MCP Documentation Search Server

Created By
PicardRaphaela year ago
🔍 FastMCP-powered documentation search engine that provides unified access to multiple framework docs (Next.js, Tailwind, Framer Motion, etc.) with intelligent name resolution and async processing.
Overview

What is MCP Documentation Search Server?

MCP Documentation Search Server is a powerful documentation search engine built with FastMCP, enabling AI systems to intelligently search across multiple popular framework and library documentations.

How to use MCP Documentation Search Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, and run the server. You can then use the provided API to search documentation for various libraries.

Key features of MCP Documentation Search Server?

  • Multi-library support for frameworks like Next.js, Tailwind CSS, and Framer Motion.
  • Intelligent search with smart name resolution and DuckDuckGo-powered results.
  • Asynchronous processing for efficient web request handling.
  • Robust error handling for network timeouts and invalid inputs.

Use cases of MCP Documentation Search Server?

  1. Quickly finding documentation for specific libraries.
  2. Assisting developers in retrieving relevant information from multiple sources.
  3. Enhancing AI systems with unified access to documentation.

FAQ from MCP Documentation Search Server?

  • What libraries are supported?

The server supports multiple libraries including LangChain, Next.js, Tailwind CSS, and more.

  • Is it easy to set up?

Yes! Follow the quick start guide in the documentation to set it up easily.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and you can find guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PicardRaphael
Star
0
Language
Python
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.

8 hours ago