Thrinacia Fabric now includes a built-in Model Context Protocol server for every managed Fabric instance.
Customers can connect MCP-compatible tools such as Codex, Claude Code, and other AI development or automation clients directly to their Fabric platform. There is no separate MCP server to install, host,
update, or maintain. Self hosted package version 0.5.0 is also now publicly available through npm.
A Dedicated MCP Endpoint for Each Fabric Instance
Each Fabric platform now provides its own MCP endpoint:
https://your-fabric-domain.example/mcpThe endpoint is connected exclusively to that Fabric instance. Campaigns, products, orders, contributions, users, analytics, and other records remain isolated within the customer’s platform.
Customers using a custom domain can access MCP through that domain’s /mcp path.
No Separate MCP Installation Required
Managed Fabric customers do not need to install the npm package, operate another server, configure a separate hostname, or synchronize MCP releases.
The MCP service is deployed alongside the Fabric backend and is updated as part of the standard Fabric deployment process.
To connect an MCP-compatible client, customers only need:
- Their Fabric MCP endpoint
- A scoped Fabric API key
- An MCP-compatible client
Secure, Scoped Authentication
The built-in MCP server uses Fabric’s existing API-key and permission system. Clients authenticate using a bearer credential:
Authorization: Bearer YOUR_API_KEYThe credential is validated against the associated Fabric instance for every request. It is not accepted through a query string and is not stored by the MCP server.
Fabric supports both platform API keys and user-scoped API keys:
- Platform API keys support approved administrative and platform-level integrations.
- User API keys allow MCP operations to follow the permissions and identity of a specific administrator, campaign creator, vendor, or other user.
Organizations can limit each key to only the capabilities required by the integration.
Fundraising Capabilities
Depending on the assigned permissions, Fabric MCP can support fundraising workflows such as:
- Searching and retrieving campaigns
- Creating campaign drafts
- Updating campaign information
- Reviewing campaign performance
- Working with rewards and campaign updates
- Reviewing contributions and recurring contributions
- Creating secure campaign checkout sessions
- Checking payment status and receipts
- Managing authorized refunds and subscriptions
- Accessing fundraising analytics and reports
Commerce Capabilities
The built-in server also exposes authorized Fabric commerce capabilities, including:
- Searching products and variants
- Creating and updating products
- Reviewing and adjusting inventory
- Creating store orders
- Generating secure checkout sessions
- Checking order and payment status
- Managing fulfillment and returns
- Accessing commerce reports
Payment Security
Fabric MCP does not collect raw card numbers or card security codes. Checkout continues through the configured payment provider’s secure SDK, tokenization, hosted approval, or other supported payment
process.
MCP can create secure checkout sessions and initialize payment workflows, but sensitive payment details remain within the appropriate payment-provider flow.
Selected financial and administrative operations also require explicit confirmation in addition to the appropriate API-key permissions.
Connecting an MCP Client
A typical remote MCP configuration looks similar to the following:
{
"mcpServers": {
"thrinacia-fabric": {
"url": "https://your-fabric-domain.example/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}The exact configuration format differs between MCP clients. API keys should always be stored using the client’s secure credential or environment-variable support rather than committed to source code.
Optional npm Package
Organizations that prefer to run MCP locally or operate a self-hosted Fabric deployment can still use the platform-neutral npm package:
Install it globally with:
npm install -g @thrinacia/fabric-mcpOr run it directly:
npx @thrinacia/fabric-mcpThe npm package supports local MCP client integration and a self-hosted single-instance Streamable HTTP server. It can run on Linux, macOS, Windows, containers, virtual machines, and other environments
supported by Node.js.
Designed for Custom Frontends and Automation
The integrated MCP server complements Fabric’s REST API, scoped API keys, and webhooks. Organizations can continue using Fabric’s reference frontend, build a completely custom frontend, connect an existing
application, or introduce AI-assisted workflows without replacing the underlying Fabric permission and operational model.
Potential workflows include campaign preparation, product administration, reporting, customer support, data analysis, operational automation, and controlled integration with AI agents.
Available Now
The built-in /mcp endpoint is now available on managed Thrinacia Fabric instances. Customers can create an appropriately scoped API key in Fabric and connect a compatible MCP client directly to
their platform.
For assistance selecting API-key scopes or configuring an MCP client, contact the Thrinacia team.