Mcp Directory

Created By
Go-To-Seaa year ago
discover MCP Servers and Clients for Claude Integration
Overview

What is Mcp Directory?

Mcp Directory is a project designed to help users discover MCP Servers and Clients for Claude Integration.

How to use Mcp Directory?

To use Mcp Directory, clone the repository from GitHub, install the necessary dependencies, prepare the database, set environment variables, and run the development server to preview the site.

Key features of Mcp Directory?

  • Easy discovery of MCP Servers and Clients.
  • Quick start guide for setup and installation.
  • Community support through Telegram and Discord.

Use cases of Mcp Directory?

  1. Integrating Claude with various MCP Servers.
  2. Setting up a local development environment for MCP projects.
  3. Collaborating with the community for MCP-related queries.

FAQ from Mcp Directory?

  • What is the purpose of Mcp Directory?

Mcp Directory helps users find and integrate MCP Servers and Clients for Claude.

  • Is there community support available?

Yes! You can join the MCP Server Telegram and Discord for community support.

  • What technologies are used in Mcp Directory?

The project is built using TypeScript and requires a Supabase database.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Go-To-Sea
Star
2
Language
TypeScript
License
Apache-2.0 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.

16 hours ago
Voyei

6 hours ago