MCP-Server-Fabric

Created By
PipeDionisioa year ago
Overview

What is MCP-Server-Fabric?

MCP-Server-Fabric is a project that integrates patterns from Fabric as tools in N8N, allowing for customization and enhancement of each pattern. It provides seamless access to various integrations, leveraging the MCP-Server to utilize tools as a USB, significantly empowering AI capabilities.

How to use MCP-Server-Fabric?

To use MCP-Server-Fabric, update the N8N API credentials, handle any errors that may arise, and customize the parameters according to your needs. You can then integrate and run tools to enhance AI output precision.

Key features of MCP-Server-Fabric?

  • MCP-Server Integration: Simplifies AI interaction with the model context protocol.
  • Prompt Filtering by Tags: Allows filtering prompts using tags for targeted tool application.
  • Customization and Enhancement: Customize and improve each pattern within N8N.
  • Supercharged AI: Enhances AI capabilities by integrating patterns as tools.

Use cases of MCP-Server-Fabric?

  1. Enhancing AI output precision through tool integration.
  2. Customizing patterns in N8N for specific requirements.
  3. Utilizing diverse tools to create intelligent output chains.

FAQ from MCP-Server-Fabric?

  • What is the purpose of MCP-Server-Fabric?

It integrates various tools to enhance AI capabilities and streamline processes in N8N.

  • How do I handle errors during setup?

Restart N8N from Docker if you encounter SSL-related errors due to API limitations.

  • Can I customize the patterns?

Yes! You can customize and enhance each pattern to fit your specific needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PipeDionisio
Star
1
Language
-
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)

2 days ago
Voyei

4 hours ago