convez.ai
MCP ServerIntegração & APIsIntermediário
TensorBlock

Awesome MCP Servers

TensorBlock/awesome-mcp-servers

Registro hospedado e pesquisável de servidores MCP com API pública gratuita

Ver no GitHub
BomPluginScore · de 0 a 100

Diretório comunitário abrangente de servidores Model Context Protocol (MCP) com índice hospedado e API pública. Cataloga mais de 7.493 servidores MCP únicos, oferecendo registro pesquisável, perfis estruturados e configurações de instalação para agentes e aplicações.

Instalação

$npx convez-ai TensorBlock/awesome-mcp-servers

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1,1 mil
Forks
2,1 mil
Acompanhando
9
Saúde
50%
Último commit
há 1 dia
Versão
—
Issues abertas
38
Contribuidores
399

Casos de uso

  • Descobrir e integrar servidores MCP em agentes Claude
  • Compartilhar e documentar servidores MCP da comunidade
  • Pesquisar e comparar funcionalidades de servidores MCP por categoria

Veredito

Projeto essencial de curação comunitária que resolve o problema real de descoberta e padronização de servidores MCP. A abordagem de índice normalizado com API pública é pragmática e reduz significativamente o atrito para adoção em produção.

README

A tradução para o português deste README ainda está na fila.

Awesome MCP Servers Awesome

Website Twitter Discord 🤗 Hugging Face Telegram

MCP Index website: https://www.tensorblock.co/mcp

Hosted API: https://mcp-index.tensorblock.co

Coverage

This repo currently indexes 7,493 unique MCP server links from the category docs. The README stays lightweight while the full directory lives in docs/*.md, data/catalog.json, and the registry MCP server.

How to Participate

This repo is a community directory plus a hosted index. Every useful contribution makes the MCP Index easier for people and agents to search, compare, install, and verify.

Choose the path that matches what you want to do.

If you maintain an MCP server:

  • Share your public MCP profile from https://www.tensorblock.co/mcp so users can inspect metadata, install configs, source links, and badges without reading the raw markdown.
  • Add your server to the best category under Browse by Category, or use the Add MCP server issue form.
  • Improve your existing entry with install command, transport, auth requirements, supported clients, docs URL, license, endpoint, and tool details. Use the metadata issue form if you do not want to open a PR directly.
  • Claim your TensorBlock MCP profile with the claim profile issue form.
  • Add the TensorBlock MCP Index badge to your project README so users can jump from your repo to the indexed profile.

If you build MCP clients, agents, or developer tools:

  • Use the hosted API at https://mcp-index.tensorblock.co to search servers, fetch normalized profiles, list categories, or generate install-config previews.
  • Request another install target with the client config issue form. Include the client name, expected config shape, example config, and official docs.
  • Help improve the config generator for Claude Desktop, Cursor, Codex, VS Code, and future clients.

If you want to improve the index itself:

  • Fix duplicate, stale, broken, or poorly categorized entries. Use the broken entry issue form when you want maintainers to triage it.
  • Add missing metadata that makes search and install generation more accurate.
  • Propose verification signals, health checks, ranking improvements, or better category rules.
  • Join the TensorBlock Discord to discuss roadmap work before opening a larger PR.

Issue forms are routed automatically. When you submit a server, metadata update, profile claim, client config request, or broken-entry report, the repo adds the right triage labels and posts the next steps so contributors and maintainers can keep the workflow moving. Server submissions with a clear category can also generate a draft docs PR automatically.

New server entries can be simple, but high-quality metadata makes the profile much more useful. The best entries answer:

  • What can an agent do with this server?
  • How does a user install or connect to it?
  • Does it use stdio, sse, or streamable-http?
  • Does it require an API key, OAuth, bearer token, or no auth?
  • Which MCP clients does it support?
  • Where are the setup docs, source repo, license, and public endpoint?

After a PR lands on main, the deploy workflow rebuilds the catalog and profiles. The hosted API and public profile pages refresh after the Railway deployment succeeds.

TensorBlock MCP Index

This repo is both a community directory and an agent-ready index. Humans add MCP servers in markdown category pages; the indexer turns those entries into structured data that agents can search, inspect, and use to draft install configs.

Hosted MCP Index API

TensorBlock provides the MCP Index API as free community infrastructure. We contribute the compute, hosting, data normalization, and ongoing maintenance needed to make this directory usable by agents and applications without requiring every user to clone the repo or parse markdown.

Public website:

https://www.tensorblock.co/mcp

Base URL:

https://mcp-index.tensorblock.co

Useful endpoints:

  • GET / - discover available endpoints and current catalog size.
  • GET /v1/categories - list categories with entry counts and source docs.
  • GET /v1/servers?query=postgres&limit=5 - search servers by name, description, category, or URL.
  • GET /v1/servers?category=Databases&transport=stdio - filter by category, transport, auth type, and result limit.
  • GET /v1/servers/{id} - fetch the normalized profile for one MCP server.
  • GET /v1/servers/{id}/badge.svg - render a TensorBlock MCP Index badge for project READMEs.
  • GET /v1/servers/{id}/install-config?client=claude-desktop - generate an MCP client config for Claude Desktop, Cursor, Codex, or VS Code.
  • https://tensorblock.co/mcp/servers/{id} - share a public website profile for an indexed server.

What the API supports today:

  • Search MCP servers by keyword.
  • Filter by category, transport, auth type, and result limit.
  • Browse all categories with entry counts.
  • Fetch a normalized server profile by stable server id.
  • Generate install-config previews for Claude Desktop, Cursor, Codex, and VS Code.

We want this registry to support more MCP clients and installation formats over time. If you want another client, package manager, transport, auth flow, or metadata field supported, please open an issue or PR with the expected config shape and examples.

We plan to keep investing in this hosted registry: improving metadata quality, expanding install-config coverage, adding verification signals, and keeping the service available for the MCP community. Contributors are welcome to help build the registry by adding servers, improving metadata, reporting bad entries, and proposing better search or verification workflows. When changes land on main, the deploy workflow rebuilds the catalog and profiles before publishing, so newly merged server entries become searchable after the Railway deployment succeeds.

How entries become index data:

  1. The source of truth is the category markdown under docs/*.md.
  2. Each server entry is parsed from a markdown bullet with a link and description.
  3. npm run catalog:build generates data/catalog.json with normalized server metadata.
  4. npm run profiles:build generates data/profiles/*.json for stable per-server profiles.
  5. The deploy workflow publishes the refreshed catalog to the hosted API after changes land on main.

For local development:

  • npm run registry:mcp starts a local registry MCP server with search_servers, get_server_profile, and get_install_config tools.
  • npm run registry:api:dev starts a local HTTP API for search, category browsing, profiles, and install configs. See TensorBlock MCP Index API.

Contributors still submit normal awesome-list entries, but better metadata makes each entry more useful to agents. See the MCP Index Metadata Contribution Guide for examples.

Add or Improve an Entry

To add a new MCP server:

  1. Pick the best category from Browse by Category.
  2. Open that category page under docs/.
  3. Add one markdown bullet using this format:
    - [Server Name](https://github.com/owner/repo): Brief description of what the MCP server lets an agent do. Install: `npx your-package`.
    
  4. Search the repo for your URL or project name to avoid duplicates.
  5. Open a pull request.

If you are not sure where the server belongs, use the Add MCP server issue form and we can help route it.

To improve an existing server, edit the same markdown bullet where the server is listed. Add missing install, transport, auth, docs, license, client, tool, endpoint, or maintainer information in the description when possible.

Generated files such as data/catalog.json and data/profiles/*.json are maintained by the indexer. If you only add a server entry, editing the relevant docs/*.md category page is enough for the PR.

For metadata and indexer examples, see the MCP Index Metadata Contribution Guide.

For maintainers validating a metadata/indexer change:

npm run catalog:build
npm run profiles:build
npm test
npm run typecheck
npm run build

Browse by Category

The README is now a lightweight entry point. Browse the full directory in the category pages below, or use data/catalog.json and the registry MCP server for agent-native search.

CategoryListed entriesFull list
AI & LLM Integration1,619Browse
Art, Culture & Media78Browse
Browser Automation & Web Scraping275Browse
Build & Deployment Tools88Browse
Cloud Platforms & Services371Browse
Code Analysis & Quality105Browse
Code Execution165Browse
Communication & Messaging327Browse
Content Management Systems59Browse
Data Analysis & Business Intelligence238Browse
Databases290Browse
Developer Productivity & Utilities393Browse
Filesystems56Browse
Finance & Crypto408Browse
Frameworks244Browse
Gaming106Browse
Hardware & IoT59Browse
Healthcare & Life Sciences57Browse
Infrastructure156Browse
Knowledge Management & Memory559Browse
Location & Maps89Browse
Marketing, Sales & CRM167Browse
Monitoring & Observability83Browse
Multimedia Processing204Browse
Operating System & Command Line106Browse
Project & Task Management219Browse
Science & Research106Browse
Search168Browse
Security121Browse
Social Media & Content Platforms107Browse
Sports6Browse
Travel & Transportation45Browse
Utilities & Helpers353Browse
Version Control76Browse
Ver o original no GitHub

Bom para

Relacionados