Awesome MCP Servers

    Join the TensorBlock Discord



    Explore Forge, our open-source middleware for AI model provider management

TensorBlock MCP Index turns this community-curated MCP server directory into a hosted, searchable registry for agents and applications. Contributors add servers in markdown; TensorBlock normalizes the entries, generates structured profiles and install-config previews, and serves the index through a free public API.

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

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

Community cleanup queue: Help verify and improve indexed MCP servers

MCP Maintainer Quick Start

If you maintain an MCP server, the index can give your project a public profile, install-config previews, API metadata, and a README badge.

1. Add your server in the best docs/*.md category, or use the Add MCP server issue form.
2. Include install, transport, auth, supported clients, docs, license, endpoint, and tool details when you have them.
3. After merge, the follow-up comment gives you the public profile URL, API profile URL, install-config links, and badge markdown.
4. Add the TensorBlock MCP Index badge to your project README so users can jump back to the indexed profile.
5. Claim your profile or send metadata fixes through the claim profile and metadata improvement forms. Valid profile claims and structured metadata updates generate draft metadata PRs; once reviewed, merged, and deployed, the public profile shows maintainer claim status plus install, auth, docs, license, tool, and verification metadata when available. Claim status is separate from TensorBlock verification.

Coverage

This repo currently indexes 7,747 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.

Community Cleanup Queue

Want to contribute without adding a new server? Start with the MCP Index Community Cleanup Queue. It links to live GitHub issue queues for good first metadata fixes, broken entries, catalog-health reports, new server submissions, client config requests, and profile claims.

Cleanup work improves the value of the hosted index: fewer duplicates, fresher source links, better install metadata, clearer categories, and more trustworthy profiles.

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; when the profile id and structured values are clear, automation drafts a metadata sidecar PR for maintainer review.
• Claim your TensorBlock MCP profile with the claim profile issue form. Claims show community maintainer ownership metadata and do not imply TensorBlock verification.
• 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. Clear requests generate a draft client-config spec PR so maintainers can review the target before implementation.
• 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. Clear dead-link reports can generate direct cleanup PRs, while duplicate, stale, category, safety, or unclear reports generate draft investigation PRs so cleanup work can be reviewed and tracked.
• Add missing metadata that makes search and install generation more accurate.
• Pick a scoped cleanup task from the community cleanup queue.
• Propose verification signals, ranking improvements, or better category rules. The catalog health checker also runs on a schedule to flag duplicate primary links, missing GitHub repos, archived repos, and disabled repos as broken-entry reports.
• Join the [TensorBlock Discord](https://discord.com