# How to submit an MCP server to TensorBlock awesome-mcp-servers By [Jonah Ease](https://manycp.com/about) Published 1 Oct 2026 Last checked 1 Oct 2026 You add a server here by writing one Markdown bullet in a category file. A build then turns that bullet into a profile page, an install-config preview for several clients, and a badge for your own README[1]. That makes the line you write the thing the index says about you, so it is worth writing the line well. ## A pull request or an issue form - **A pull request** that adds the bullet to the right category file under `docs/`. The issue form itself says a pull request is still the fastest path[2]. - **The Add MCP server issue form**, when you are unsure of the category or want help shaping the entry. It asks for a name, a project URL and a best category from a list of 13, a description of what an agent can do with it, and optionally install steps, transport, auth, clients and licence[2]. When the form has enough, automation can open a draft pull request for you[1]. ## The bullet, and where it goes One entry (example names) ``` - [Example Weather](https://github.com/example-user/weather-mcp): Gets forecasts and weather alerts for a city. Install: `npx -y weather-mcp`. ``` Search the repository for your project URL first to avoid a duplicate, then add the bullet to the category page that fits[1]. The README lists 33 categories with their counts. On 1 Oct 2026 the largest were AI & LLM Integration (1,632 entries), Knowledge Management & Memory (572), Finance & Crypto (445) and Developer Productivity & Utilities (414), and the whole index held 7,747 unique links[1]. ## The metadata that makes the profile useful A simple bullet is enough to be merged. The README says the best entries also answer: what can an agent do with this server, how is it installed or connected, whether it uses `stdio`, `sse` or `streamable-http`, whether it needs an API key, OAuth, a bearer token or nothing, which clients it supports, and where the docs, source, licence and public endpoint are[1]. Extra structured values go in sidecar files the indexer reads, or through the metadata issue form. You do not need to touch those to be listed. ## What you get after a merge After a pull request lands on `main`, a deploy rebuilds the catalog and profiles. The README says a follow-up comment then gives you the public profile address, the API profile address, install-config links and the badge to paste into your README[1]. Claiming the profile is a separate issue form, and the README is careful to say a claim is not the same as TensorBlock verification[1]. ## Edits that get bounced - **Editing generated files.** `data/catalog.json` and `data/profiles/*.json` are produced by the indexer. For a simple entry, editing the category page is enough[1]. - **A duplicate.** Submissions through the form get an intake label, and `duplicate` means your project URL is already in the catalog. The others are `needs-metadata`, `ready-for-pr` and `automation-blocked` [1]. - **Missing fields.** `needs-metadata` means a required field, a valid project URL, or category routing is still missing[1]. ## By hand, the short way Search, pick the category page, add the bullet at the end, and open a pull request. The title the form uses is "Add MCP server: " followed by the name[2], and a pull request title in that style fits. ## Current status, 1 Oct 2026 On 2 Oct 2026 the repository had [7 open pull requests](https://github.com/TensorBlock/awesome-mcp-servers/pulls?q=is%3Apr+is%3Aopen) and [2 open issues](https://github.com/TensorBlock/awesome-mcp-servers/issues?q=is%3Aissue+is%3Aopen) [3] [4], and [4 open issues labelled ready-for-pr](https://github.com/TensorBlock/awesome-mcp-servers/issues?q=is%3Aissue+is%3Aopen+label%3Aready-for-pr) on the day I read it[5]. The index serves a free public API that other tools can read, described in the README[1]. ## How long merges took In the 90 days to 2 Oct 2026, 581 outside pull requests merged here; the typical one was merged [17 h](https://github.com/TensorBlock/awesome-mcp-servers/pulls?q=is%3Apr+is%3Amerged) after it was opened. The middle half took 7 h to 1.6 days. 1 of the 581 were opened by ManyCP for its own listings. TensorBlock awesome-mcp-servers Rolling 30-day median time to merge TensorBlock awesome-mcp-servers: rolling 30-day median time to merge, by the day the window ends. Windows with fewer than 3 merges are left out. | Window ending | Rolling median | Merges in window | | --- | --- | --- | | 31 Oct 2025 | 6.3 days | 3 | | 12 Dec 2025 | 3 h | 3 | | 19 Dec 2025 | 3 h | 3 | | 26 Dec 2025 | 3 h | 3 | | 2 Jan 2026 | 3 h | 5 | | 9 Jan 2026 | under 1 h | 6 | | 16 Jan 2026 | under 1 h | 6 | | 23 Jan 2026 | under 1 h | 9 | | 30 Jan 2026 | under 1 h | 8 | | 6 Feb 2026 | 6 h | 9 | | 13 Feb 2026 | 6 h | 10 | | 20 Feb 2026 | 8 h | 14 | | 27 Feb 2026 | 6 h | 33 | | 6 Mar 2026 | 9 h | 55 | | 13 Mar 2026 | 9 h | 63 | | 20 Mar 2026 | 15 h | 81 | | 27 Mar 2026 | 1.1 days | 79 | | 3 Apr 2026 | 1.1 days | 94 | | 10 Apr 2026 | 1.8 days | 88 | | 17 Apr 2026 | 1.8 days | 96 | | 24 Apr 2026 | 1.3 days | 77 | | 1 May 2026 | 2.4 days | 66 | | 8 May 2026 | 2.8 days | 57 | | 15 May 2026 | 3.5 days | 65 | | 22 May 2026 | 4.3 days | 60 | | 29 May 2026 | 4.4 days | 69 | | 5 June 2026 | 4.7 days | 68 | | 12 June 2026 | 8.9 days | 177 | | 19 June 2026 | 6.4 days | 186 | | 26 June 2026 | 6.6 days | 182 | | 3 July 2026 | 4.1 days | 197 | | 10 July 2026 | 1.5 days | 103 | | 17 July 2026 | 1.5 days | 96 | | 24 July 2026 | 1.7 days | 109 | | 31 July 2026 | 1.7 days | 126 | | 7 Aug 2026 | 1.7 days | 128 | | 14 Aug 2026 | 2.1 days | 113 | | 21 Aug 2026 | 2.4 days | 126 | | 28 Aug 2026 | 2.3 days | 158 | | 4 Sept 2026 | 1.2 days | 166 | | 11 Sept 2026 | 15 h | 192 | | 18 Sept 2026 | 10 h | 203 | | 25 Sept 2026 | 9 h | 229 | | 2 Oct 2026 | 10 h | 300 | Measured 2 Oct 2026. Pull requests merged on each list's GitHub repo, timed from opened to merged, read from GitHub's REST pulls list. Bot accounts ([bot]), the repo's owners, members and collaborators, and pull requests from a branch inside the list's own repo are left out. A past figure, not a promise. All 10 directories side by side: [how long MCP directories take to merge](https://manycp.com/guides/mcp-server-merge-times). ## Sources 1. [TensorBlock/awesome-mcp-servers: README](https://github.com/TensorBlock/awesome-mcp-servers/blob/main/README.md) · checked 1 Oct 2026 2. [TensorBlock/awesome-mcp-servers: the Add MCP server issue form](https://github.com/TensorBlock/awesome-mcp-servers/blob/main/.github/ISSUE_TEMPLATE/add-mcp-server.yml) · checked 1 Oct 2026 3. [TensorBlock/awesome-mcp-servers: open pull requests](https://github.com/TensorBlock/awesome-mcp-servers/pulls?q=is%3Apr+is%3Aopen) · checked 1 Oct 2026 4. [TensorBlock/awesome-mcp-servers: open issues](https://github.com/TensorBlock/awesome-mcp-servers/issues?q=is%3Aissue+is%3Aopen) · checked 1 Oct 2026 5. [Open issues labelled ready-for-pr](https://github.com/TensorBlock/awesome-mcp-servers/issues?q=is%3Aissue+is%3Aopen+label%3Aready-for-pr) · checked 1 Oct 2026 ManyCP is not affiliated with, endorsed by or sponsored by any directory, Docker, OpenAI, Anthropic or GitHub named here. Names are used to say which service a fact is about. --- Source: [ManyCP](https://manycp.com/directories/tensorblock-awesome-mcp-servers)