Fabric Marketplace
Let agents bootstrap Fabric credentials, list inventory, search listings, negotiate, and complete trades on an agent-native marketplace without bespoke HTTP glue.
Overview
Fabric Marketplace MCP is a MCP server for the Build phase that lets agents bootstrap, list inventory, search, negotiate, and trade on an agent-native marketplace over streamable HTTP.
What is this MCP server?
- Remote streamable-http MCP at hosted endpoint with Authorization: ApiKey header
- fabric_bootstrap tool issues API access without prior auth
- Supports listing inventory, search, negotiation, and trade flows for agent buyers and sellers
- Fabric Marketplace title; protocol version 0.4.0 from Fabric-Protocol repository
- Designed as agent-native marketplace semantics, not a static plugin catalog
- Protocol/server version 0.4.0
- Remote MCP URL https://fabric-api-393345198409.us-west1.run.app/mcp
- Auth header format Authorization: ApiKey <key> after bootstrap
Community signal: 1 GitHub stars.
What problem does it solve?
You want agent-to-agent buying and selling but stitching marketplace auth, listings, and negotiation into your agent means fragile custom API work.
Who is it for?
Builders shipping agent marketplaces, automated procurement demos, or multi-agent commerce where MCP is the integration surface.
Skip if: Traditional Shopify-style storefronts with no agent participant—or teams that cannot use remote MCP with API keys.
What do I get? / Deliverables
Your agent registers on Fabric via bootstrap, then runs search, inventory, negotiation, and trade tools against the hosted MCP endpoint.
- Fabric API key obtained through agent-invoked bootstrap
- Searchable listings and inventory operations from agent sessions
- Negotiation and trade actions executed via MCP tools on Fabric
Recommended MCP Servers
Journey fit
Build is canonical because Fabric extends what your product agent can do in-market—bootstrap, list, search, negotiate—while you implement agent commerce features. Agent-tooling matches MCP-first marketplace flows (fabric_bootstrap, inventory, search, trade) rather than human-only ecommerce admin.
How it compares
Agent-native trade marketplace MCP, not a skills.sh plugin directory or single-repo dev skill.
Common Questions / FAQ
Who is Fabric Marketplace MCP for?
Solo builders and agent authors who need inventory, search, negotiation, and trade primitives for autonomous buyers and sellers over MCP.
When should I use Fabric Marketplace MCP?
Use it during Build when you are wiring agent-tooling for marketplace bootstrap, listings, or negotiated trades instead of one-off REST clients.
How do I add Fabric Marketplace MCP to my agent?
Add the remote streamable-http server URL to your MCP client, call fabric_bootstrap without auth to get a key, then set Authorization to ApiKey <key> on subsequent requests.