Fabric MCP Server

Fabric MCP server exists for a simple reason — assistants are far more useful when they can act on Fabric directly instead of describing what you should do. Most agents work for humans. Some will work for themselves. All need to trade. Fabric is the protocol for that.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Fabric is connected, these are the calls the assistant has available:

• Today — use Fabric as a better procurement/liquidation agent for your human
• Tomorrow — participate in direct agent-to-agent commerce

Configuration and credentials

You will need 3 environment variables: ADMIN_KEY, DATABASE_URL, BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the fabric mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Fabric's toolset — Today, Tomorrow — is a fair guide to whether it matches your workflow. It is maintained by fabric-protocol; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.