fabric-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is fabric-mcp-server?

The fabric-mcp-server is a Model Context Protocol (MCP) server designed to expose Fabric patterns as tools for integration with Cline, enhancing its capabilities through AI-driven pattern execution.

How to use fabric-mcp-server?

To use the fabric-mcp-server, clone the repository, install dependencies, build the project, and configure it within your Cline settings. Then, create a new task in Cline and select a Fabric pattern to utilize.

Key features of fabric-mcp-server?

  • Exposes Fabric patterns as individual tools within Cline.
  • Allows users to execute Fabric patterns directly in Cline tasks.
  • Integrates AI-driven execution to enhance functionality.

Use cases of fabric-mcp-server?

  1. Executing data analysis tasks using predefined Fabric patterns.
  2. Automating workflows in Cline with AI-driven tools.
  3. Enhancing productivity by integrating various Fabric capabilities into Cline.

FAQ from fabric-mcp-server?

  • What is the Model Context Protocol (MCP)?

MCP is a specification that standardizes communication between AI systems and external tools, allowing for enhanced interaction and functionality.

  • How do I install fabric-mcp-server?

Clone the repository, install dependencies with npm, and build the project to get started.

  • Can I contribute to fabric-mcp-server?

Yes! Contributions are welcome, and guidelines can be found in the CONTRIBUTING.md file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago