Skip to main content
Glama

fabric-mcp-server

Table of Contents

  1. Introduction

  2. What is Model Context Protocol (MCP)?

  3. Features

  4. Tools

  5. Installation

  6. Usage

  7. Configuration for Claude Desktop

  8. Configuration for VS Code with Cline

  9. Tips for Using with Different AI Agents

  10. Troubleshooting

  11. Contributing

  12. License

Related MCP server: wrapmcp

Introduction

The fabric-mcp-server is a Model Context Protocol (MCP) server designed to expose Daniel Miessler's Fabric patterns as tools for integration with AI coding agents and assistants. This integration enhances AI capabilities by leveraging AI-driven pattern execution from the Fabric repository. The server works with various AI platforms including Claude Desktop, Cline, and other MCP-compatible AI agents.

What is Model Context Protocol (MCP)?

The Model Context Protocol (MCP) is a specification that facilitates communication between AI systems and external tools or resources. It standardizes the way AI models interact with various capabilities such as databases, APIs, and file systems. MCP servers, like fabric-mcp-server, implement this protocol to make tools and resources accessible to AI models, thereby expanding their functional scope.

Features

  • Exposes Fabric Patterns as Tools: The server makes all Fabric patterns available as individual tools within MCP-compatible AI agents.

  • Pattern Execution: Users can select and execute Fabric patterns directly within AI assistant tasks.

  • Enhanced Capabilities: Integrates AI-driven pattern execution to augment AI assistant functionality.

  • Cross-Platform Compatibility: Works with Claude Desktop, Cline, and other MCP-compatible AI agents.

Tools

The fabric-mcp-server exposes a wide range of Fabric patterns as tools. Some examples include:

  • analyze_claims

  • summarize

  • extract_wisdom

  • create_mermaid_visualization

  • And many more...

To see the full list of available patterns, you can list the directories in the [fabric/patterns](https://github.com/danielmiessler/Fabric/tree/main/data/patterns) directory.

Installation

  1. Clone the Repository: Clone the fabric-mcp-server repository to your local system.

  2. Install Dependencies: Navigate into the fabric-mcp-server directory and run npm install.

  3. Build the Project: Run npm run build to compile the TypeScript code.

Usage

To use the fabric-mcp-server with AI agents:

  1. Ensure the server is installed and running.

  2. Configure the MCP server in your AI agent's settings file.

  3. Create a new task or conversation and select a Fabric pattern to use.

The specific configuration steps vary depending on which AI agent you're using. See the sections below for detailed instructions.

Configuration for Claude Desktop

To use fabric-mcp-server with Claude Desktop:

  1. Complete Installation: Follow the installation steps above to build the project.

  2. Configure Claude Desktop: Add the MCP server configuration to your Claude Desktop settings. The configuration file is typically located at:

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Linux: ~/.config/Claude/claude_desktop_config.json

  3. Add Server Configuration: Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "fabric-mcp-server": {
      "command": "node",
      "args": [
        "<path-to-fabric-mcp-server>/build/index.js"
      ],
      "env": {}
    }
  }
}

Replace <path-to-fabric-mcp-server> with the actual path to the fabric-mcp-server directory on your system.

  1. Restart Claude Desktop: Restart Claude Desktop to apply the changes.

Configuration for VS Code with Cline

To use fabric-mcp-server with Cline in VS Code:

  1. Complete Installation: Follow the installation steps above to build the project.

  2. Configure Cline Settings: Add the MCP server configuration to your Cline settings file. The file path varies by operating system:

    • Windows: C:\Users\<username>\AppData\Roaming\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

    • macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

    • Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

  3. Add Server Configuration: Use the following configuration:

{
  "fabric-mcp-server": {
    "command": "node",
    "args": [
      "<path-to-fabric-mcp-server>/build/index.js"
    ],
    "env": {},
    "disabled": false,
    "autoApprove": [],
    "transportType": "stdio",
    "timeout": 60
  }
}

Replace <path-to-fabric-mcp-server> with the actual path to the fabric-mcp-server directory on your system. For example:

  • Windows: "C:\\path\\to\\fabric-mcp-server\\build\\index.js"

  • macOS/Linux: "/path/to/fabric-mcp-server/build/index.js"

  1. Restart VS Code: Restart VS Code or reload the Cline extension to apply the changes.

Tips for Using with Different AI Agents

For Claude Desktop Users

  • Simply mention that you'd like to use a Fabric pattern in your conversation

  • Ask Claude to list available patterns if you're unsure which one to use

  • The patterns will be automatically available as tools once configured

For Cline Users

To maximize the benefits of fabric-mcp-server with Cline, add use fabric-mcp-server at the end of your prompts or consider adding the following rule to your .clinerules file:

# Fabric MCP Server Rule
1. **List Fabric Patterns**: When a new task is created, list all pattern names from the Fabric repository.
2. **Prompt for Pattern Selection**: Ask the user to select one of the following options:
   a) Enter a pattern name from the list to use the `fabric-mcp-server` tool with the specified pattern.
   b) Choose not to use `fabric-mcp-server` for the task.

This rule streamlines the tool selection process for new tasks in Cline.

For Other MCP-Compatible Agents

  • Consult your specific AI agent's documentation for MCP server configuration

  • The basic server configuration should be similar to the examples above

  • Ensure your agent supports the MCP protocol and tool execution

Troubleshooting

  • Ensure the fabric-mcp-server is correctly configured in your AI agent's settings.

  • Verify that the server is running and reachable.

  • Check the console output for any error messages.

  • Make sure the path to the build/index.js file is correct and accessible.

  • Verify that Node.js is installed and available in your system PATH.

Contributing

Contributions to fabric-mcp-server are welcome. Please refer to the CONTRIBUTING.md file for guidelines on how to contribute.

License

fabric-mcp-server is released under the MIT License.

Available Tools

1 tool
recommend_toolC

Recommends the best Fabric pattern tool for a given task

ParametersJSON Schema
NameRequiredDescriptionDefault
inputYesThe user's task description

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'recommends' but does not clarify how recommendations are generated (e.g., based on criteria, algorithms, or data sources), whether it requires specific permissions, or what the output format entails. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficiently conveys the essential information, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a recommendation function with no annotations or output schema), the description is incomplete. It lacks details on how recommendations are made, what criteria are used, the format of the output, or any behavioral traits. This makes it inadequate for an agent to fully understand and use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the parameter 'input' documented as 'The user's task description.' The description adds no additional meaning beyond this, such as examples or constraints. According to the rules, when schema coverage is high (>80%), the baseline score is 3, which applies here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Recommends the best Fabric pattern tool for a given task.' It specifies the verb ('recommends') and resource ('Fabric pattern tool'), making the function understandable. However, with no sibling tools provided, it cannot demonstrate differentiation from alternatives, preventing a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or specific contexts. It merely restates the tool's function without indicating appropriate scenarios or exclusions, which is insufficient for effective agent decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool name 'recommend_tool' follows a consistent verb_noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.

Tool Count2/5

A single tool is too few for most server purposes, as it severely limits functionality and scope. This feels thin and incomplete for a server named 'Fabric MCP Server', which might imply broader capabilities.

Completeness1/5

The server is severely incomplete; with only a recommendation tool, there are obvious gaps in the surface. It lacks any tools to actually execute or manage Fabric patterns, making it impossible for agents to perform core tasks beyond getting advice.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that publishes CLI tools on your machine for discoverability by LLMs
    14
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Universal MCP server that wraps any CLI tool, enabling AI assistants to run commands via natural language.
    MIT
  • F
    license
    C
    quality
    C
    maintenance
    An MCP server that exposes Discord bot actions as tools for LLM clients.
    29
    1

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/augmentedivan/fabric-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server