Fabric MCP Server 9fc5b8c5

MCPAI代理

提供方 brneto

AI代理 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude DesktopClaude
查看接入方式

一个将Daniel Miessler的Fabric模式和策略暴露给符合MCP协议的客户端的服务器,支持动态同步、模式提示、策略支持和资源管理。

一句话选型结论

按资料字段整理

Fabric MCP Server 9fc5b8c5 属于AI代理类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude Desktop、Claude,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式支持远程部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 5 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量5暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

AI工作流Python本地部署提示工程模型上下文协议Docker服务研究资源管理

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
docker run -i fabric-mcp-server

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 5 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 5 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Fabric MCP Server 9fc5b8c5当前 5 stdio · 本地进程 支持远程部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方brneto上游标注的维护方 brneto
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Docker本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

13.8 KB
来自项目仓库与上游目录的原文,未做删改

Fabric MCP Server (Docker)

A Model Context Protocol (MCP) server that exposes Daniel Miessler's Fabric patterns and strategies to MCP-compliant clients. It automatically syncs with the upstream Fabric repository, allowing you to use its powerful prompts directly within your AI workflow.

Features

  • Dynamic Sync: Clones or updates the Fabric repository every time the server starts.
  • Pattern Prompts: Automatically creates an MCP prompt for every folder in patterns/.
  • Smart Descriptions: Extracts meaningful descriptions from each pattern's system.md file to help LLMs understand when to use each pattern.
  • Strategy Support: Every prompt includes an optional strategy argument to prepend context from strategies/. Natural language phrases like "with strategy cot" or "using cot strategy" are recognized.
  • User Input: Every prompt requires an input argument for user-provided content (text, URL, etc.).
  • Execute Pattern Tool: Exposes an execute_pattern tool so AI agents can execute any Fabric pattern programmatically with optional strategy.
  • List Patterns Tool: Exposes a list_patterns tool so AI agents can discover available Fabric patterns programmatically.
  • List Strategies Tool: Exposes a list_strategies tool to discover available strategies and their descriptions.
  • Research Resources: Exposes research documents as MCP resources in both markdown and PDF formats, accessible via custom URIs (e.g., markdown://researches/the-prompt-report, pdf://researches/the-prompt-report).
  • Resource Subscriptions: Supports subscribing to markdown resource changes, notifying clients when files are modified.

Project Structure```

fabric-mcp-server/
├── server.py # Main entry point, MCP server registration
├── Dockerfile
├── pyproject.toml
│
├── helpers/ # Helper utilities package
│ ├── init.py # Re-exports all functions
│ ├── _types.py # TypedDict definitions
│ ├── config.py # Configuration constants
│ ├── repo.py # Repository management (sync, clone)
│ ├── paths.py # Directory/path utilities
│ ├── text.py # Text processing utilities
│ ├── patterns.py # Pattern operations
│ ├── strategies.py # Strategy operations
│ └── prompt_builder.py # Prompt construction utilities
│
├── mcp_handlers/ # MCP protocol handlers package
│ ├── init.py # Re-exports all handlers
│ ├── tools.py # Tool handlers (list_patterns, execute_pattern, etc.)
│ ├── resources.py # Resource handlers (research documents)
│ └── prompts.py # Prompt handlers (Fabric patterns as prompts)
│
└── resources/
├── markdown/
│ └── researches/ # Markdown research documents exposed as MCP resources
└── pdf/
└── researches/ # PDF research documents exposed as MCP resources


## Prerequisites

- Docker installed and running.

## Build

Build the Docker image locally:```bash
docker build -t fabric-mcp-server .

Running the Server

1. Manual Test (Stdio)

To test if the server starts and syncs the repository correctly:```bash
docker run -i fabric-mcp-server

*Note: The server communicates via JSON-RPC over stdin/stdout. You will see logs on stderr and can interact via the MCP Inspector.*

### 2. Access via MCP Gateway (Claude Desktop, etc.)

To use this server with a gateway like **Claude Desktop**, add the following to your `claude_desktop_config.json` (usually located at `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):```json
{
  "mcpServers": {
    "fabric": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "fabric-mcp-server"
      ]
    }
  }
}

3. Access via Gemini CLI

To use this server with the Gemini CLI, add the following to your ~/.gemini/settings.json:```json
{
"mcpServers": {
"fabric": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"fabric-mcp-server"
]
}
}
}


### 4. Usage with MCP Gateway "Run" Command

If you are using a gateway that supports running servers via a direct command string, use:```bash
docker run -i --rm fabric-mcp-server

5. Usage via Docker MCP Gateway

If you are using the Docker MCP Gateway CLI, you can run this server directly using:```bash
docker mcp gateway run fabric-mcp-server


### 6. Global Registration (Docker MCP Catalog)

To make this server visible to all Docker MCP clients (like the `docker mcp` CLI) using the configuration files in `~/.docker/mcp/`:

1.  **Build the Image**:```bash
    docker build -t fabric-mcp-server .
    ```

2.  **Create a Local Catalog**:
    Create a file named `local.yaml` in your catalogs directory (usually `~/.docker/mcp/catalogs/local.yaml`):```yaml
    version: 3
    name: local-catalog
    displayName: Local Catalog
    registry:
      fabric:
        title: Fabric
        description: Fabric patterns and strategies
        type: server
        image: fabric-mcp-server:latest
        tools:
          - execute_pattern
          - list_patterns
          - list_strategies
          - list_research_resources
          - read_research_resource
        prompts: []  # One prompt per pattern in the Fabric repository
        resources: {}
        metadata:
          category: productivity
          tags:
            - fabric
            - ai
            - prompts
          owner: local
    ```

3.  **Enable the Server**:
    Edit your registry file (usually `~/.docker/mcp/registry.yaml`) and add the `fabric` entry under `registry:`:```yaml
    registry:
      # ... other servers ...
      fabric:
        ref: ""
    ```

4.  **Verify**:
    Run `docker mcp list` (if available) or simply try running it:```bash
    docker mcp gateway run fabric
    ```

## Debugging with MCP Inspector

The MCP Inspector is an interactive developer tool for testing and debugging MCP servers. It allows you to inspect resources, test prompts, execute tools, and monitor server notifications.

### Running the Inspector

To debug this Fabric MCP server with MCP Inspector, run:```bash
npx @modelcontextprotocol/inspector docker run -i --rm fabric-mcp-server

This will launch the Inspector UI in your browser, connecting to the Fabric MCP server running in Docker.

Inspector Features

  • Resources Tab: Browse and inspect research documents (markdown and PDF)
  • Prompts Tab: Test Fabric patterns with custom inputs and strategies
  • Tools Tab: Execute list_patterns, list_strategies, execute_pattern, and research resource tools
  • Notifications Pane: Monitor server logs and notifications

Development Workflow

  1. Build the Docker image: docker build -t fabric-mcp-server .
  2. Launch the Inspector with the command above
  3. Make changes to your server code
  4. Rebuild the image and reconnect the Inspector to test

How it Works

  1. Startup: The server clones https://github.com/danielmiessler/fabric into the container.
  2. Prompts: It scans folders like extract_wisdom, summarize, etc. in patterns/.
  3. Resources: It scans the resources/markdown/researches/ and resources/pdf/researches/ folders for research documents and exposes them as MCP resources with custom URIs.
  4. Subscriptions: Clients can subscribe to markdown resource changes. The server monitors the markdown resources folder and sends notifications when files are modified (PDF subscriptions are not supported).
  5. Execution:
    - When you select a prompt (e.g., extract_wisdom), it reads the system.md file.
    - If you provide a strategy (e.g., cot), it fetches the strategy JSON, extracts the prompt content, and prepends it to the system message.
    - The input argument content is appended to the end of the prompt.
  6. Tools:
    - Use execute_pattern to run any Fabric pattern with content and optional strategy.
    - Use list_patterns to discover all available Fabric patterns.
    - Use list_strategies to discover available strategies and their descriptions.
    - Use list_research_resources to discover all available research documents.
    - Use read_research_resource to read a specific research document by name (supports both human-readable names like "The Prompt Report" and slugs like "the-prompt-report").

MCP Prompts, Tools, and Resources

> Important Note: In the Model Context Protocol (MCP):
> - Prompts are templates exposed by servers for the client (you) to use
> - Tools are functions the AI agent can call directly
> - Resources are data sources (files, documents) that can be read by clients
>
> As an AI agent, LLMs primarily see Tools. They may not have direct visibility into user-facing Prompts (like analyze_bill_short or youtube_summary) from connected MCP servers. Those are typically accessed via your client's UI (e.g., typing / in your chat interface with Claude Desktop).
>
> This is why we expose:
> - Prompts: For clients that support the / command interface
> - execute_pattern Tool: So AI agents can run any pattern programmatically via natural language
> - list_patterns Tool: So AI agents can discover available patterns
> - list_research_resources Tool: So AI agents can discover available research documents
> - read_research_resource Tool: So AI agents can read research documents via natural language
> - Resources: Research documents accessible via markdown://researches/{title} and pdf://researches/{title} URIs

Usage Examples

Using Prompts via Client UI

MCP Prompts are accessed through your client's UI. For example, in Claude Desktop, type / followed by the pattern name:

Client Action Result
Type /create_micro_summary Invokes the pattern with prompts for input (required) and strategy (optional)
Type /summarize Invokes the summarize pattern
Type /extract_wisdom Invokes the extract wisdom pattern

Using Tools via Natural Language

AI agents can use the available tools to discover and execute patterns:

Natural Language Prompt Tool Called Arguments
"What Fabric patterns are available?" list_patterns -
"Show me the available strategies" list_strategies -
"What research documents are available?" list_research_resources -
"List all research papers" list_research_resources -
"Read the Prompt Report research paper" read_research_resource name="The Prompt Report" or name="the-prompt-report"
"Show me the content of the prompt report" read_research_resource name="the-prompt-report", format="markdown"
"Summarize the key findings from the prompt report" read_research_resource name="the-prompt-report"
"Create a micro summary of https://youtu.be/abc123" execute_pattern pattern="create_micro_summary", input="https://youtu.be/abc123"
"Summarize this article with strategy cot: https://example.com/article" execute_pattern pattern="summarize", input="https://example.com/article", strategy="cot"
"Extract wisdom using chain-of-thought from this text: [text]" execute_pattern pattern="extract_wisdom", input="[text]", strategy="cot"

Using Resources

MCP Resources are data sources exposed by the server. Research documents are available in both markdown and PDF formats via custom URIs:

Resource URI Description
markdown://researches/the-prompt-report The Prompt Report (Markdown format)
pdf://researches/the-prompt-report The Prompt Report (PDF format)

Accessing Resources via Client UI

MCP Resources are accessed differently than Prompts. In Gemini CLI, use the @ prefix to reference and embed resource content into your chat:

Feature Access Method Function
MCP Prompts / Runs a pre-defined prompt template
MCP Resources @ Fetches and attaches data (files, docs) to your message
Client Action Result
Type @fabric:markdown://researches/the-prompt-report Embeds the markdown research document into your chat context
Type @fabric:pdf://researches/the-prompt-report Embeds the PDF research document into your chat context

Tip: Type @ in Gemini CLI to see auto-completion for all available resources from connected MCP servers.

Example usage:@fabric:markdown://researches/the-prompt-report Summarize the key findings from this research paper

Adding New Resources

To add new research documents:
- Place markdown files in resources/markdown/researches/
- Place PDF files in resources/pdf/researches/

Files will be automatically discovered and exposed with a URL-friendly slug based on the filename.

Resource Subscriptions

Clients can subscribe to markdown resource changes to receive notifications when files are modified:

  • Subscribe: Call resources/subscribe with a markdown resource URI to start receiving change notifications
  • Unsubscribe: Call resources/unsubscribe to stop receiving notifications

When a subscribed markdown file is modified, the server sends a notifications/resources/updated notification to the client.

> Note: PDF resources do not support subscriptions.

Prompt Arguments

When invoking a prompt (via / command), you can provide:

Argument Required Description Example
input Yes The content to analyze (text, URL, etc.) https://youtu.be/abc123
strategy No Thinking strategy to enhance analysis cot, tot

Tip: For best results when using strategies, include phrases like:
- "with strategy cot"
- "using strategy tot"
- "apply cot strategy"

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Fabric MCP Server 9fc5b8c5 怎么安装?

在客户端按下面的安装命令接入:docker run -i fabric-mcp-server。装完在客户端配置里引用同一个包或端点。

Fabric MCP Server 9fc5b8c5 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Fabric MCP Server 9fc5b8c5 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Fabric MCP Server 9fc5b8c5 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Fabric MCP Server 9fc5b8c5 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Fabric MCP Server 9fc5b8c5 能提供哪些能力?

资料显示约 5 个工具;能力标签包括 AI工作流、Python、Claude。具体工具清单以官方文档为准。

Fabric MCP Server 9fc5b8c5 需要什么运行环境?

运行时为 Docker;属于本地进程,需要在本机装好运行环境。

Fabric MCP Server 9fc5b8c5 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。