fastify-mcp

Created By
haroldadmina year ago
A Fastify plugin to run Model Context Protocol (MCP) servers
Overview

What is fastify-mcp?

fastify-mcp is a Fastify plugin designed to integrate Model Context Protocol (MCP) servers with Fastify applications, enabling seamless communication and data handling.

How to use fastify-mcp?

To use fastify-mcp, first define your MCP server and then create a Fastify app where you register the plugin. You can manage sessions and set up the server to handle different transport methods.

Key features of fastify-mcp?

  • Integration with Model Context Protocol servers.
  • Support for Streamable HTTP and legacy HTTP+SSE transports.
  • In-memory session management for active sessions.

Use cases of fastify-mcp?

  1. Building real-time applications that require efficient data handling.
  2. Creating APIs that utilize the Model Context Protocol for communication.
  3. Managing multiple sessions in a Fastify application.

FAQ from fastify-mcp?

  • What is the Model Context Protocol?

The Model Context Protocol is a specification for building context-aware applications that can manage and communicate data effectively.

  • Is fastify-mcp easy to install?

Yes! You can install fastify-mcp using npm or yarn with a simple command.

  • Can I manage multiple sessions?

Yes! fastify-mcp provides in-memory session management to handle multiple active sessions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
haroldadmin
Star
11
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
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.

21 minutes ago