fabric-mcp

Provides a standalone MCP server that bridges MCP tool calls to a running Fabric AI instance (via its REST API), exposing tools for listing patterns/models and running Fabric patterns/configurations.

Evaluated Mar 30, 2026 (21d ago)

Repo ↗ Ai Ml mcp fabric ai-workflows tooling python stdio http-transport

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

TLS/HTTPS requirements for the MCP server are not documented; default upstream base URL uses http://127.0.0.1. Upstream auth is via a single API key variable (no scopes/role model described). No evidence in the provided content of secret redaction practices, MCP authentication, or authorization controls on tool invocation.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You already run `fabric --serve` and want an MCP-compatible wrapper/bridge for IDEs or chat interfaces.

Avoid When

You cannot secure the upstream Fabric endpoint or you need granular authorization on the MCP server surface (not clearly documented here).

Use Cases

• Integrate Fabric prompts/patterns into MCP-capable IDE extensions
• Use chat/MCP assistants to run Fabric-based refactoring, explanation, or writing workflows
• Expose Fabric patterns and model/strategy metadata as MCP tools

Not For

• Direct use as a hosted SaaS for model inference (it is a local/standalone bridge)
• Environments requiring strong, documented end-to-end auth/authorization for the MCP server itself (only upstream Fabric API key is described)
• Use where you need published REST/OpenAPI contracts for the MCP interface

Interface

REST API

Yes

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: Upstream Fabric API key (FABRIC_API_KEY) for calls to `fabric --serve`

OAuth: No Scopes: No

Authentication is described only for the upstream Fabric REST API. No MCP-server auth mechanism (e.g., MCP host auth, client auth, or transport security requirements) is documented in the provided README.

Pricing

Free tier: No

Requires CC: No

No pricing details for the package itself are provided in the README; it appears to be open-source (MIT) and intended to run locally.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Requires a separately running Fabric REST API instance (`fabric --serve`)
⚠ MCP operations may depend on transport mode (stdio vs http-streamable) and host/port/mcp-path configuration
⚠ If FABRIC_API_KEY is required by the upstream Fabric server, misconfiguration will cause tool execution failures

Alternatives

Build a custom MCP server wrapper directly around Fabric’s REST API Use MCP tooling to call Fabric endpoints without an intermediate server (if your Fabric deployment supports it) Use Fabric CLI patterns directly within your IDE/chat integration

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for fabric-mcp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.