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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago