registry/docs
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Seey 5e565ed19f
docs(community): update project link and name to ToolSDK MCP Registry (#747)
<!-- Provide a brief summary of your changes -->

Updated the project entry from **Awesome MCP Registry** to **ToolSDK MCP
Registry**, reflecting the new GitHub repository name and official
project name.

> We’re honored that our Sub Registry project has been included in the
official MCP Registry. To better reflect its purpose and maintain a more
professional naming convention, we’re updating the entry name from
**Awesome MCP Registry** to **ToolSDK MCP Registry**. This change
replaces the earlier, more generic name “Awesome” with a clearer and
more representative title for the project.
>
> *Based on GitHub’s renaming mechanism, the old link remains valid and
will automatically redirect to the new repository.*

## Motivation and Context

The project repository has been renamed and migrated from
[`toolsdk-ai/awesome-mcp-registry`](https://github.com/toolsdk-ai/awesome-mcp-registry)
→
[`toolsdk-ai/toolsdk-mcp-registry`](https://github.com/toolsdk-ai/toolsdk-mcp-registry).

This update ensures that the community registry points to the **correct
and active repository**, while maintaining the same project description
and context. The **ToolSDK MCP Registry** continues to extend the MCP
Registry with **API-based MCP execution**, **private deployment**, and
**secure sandbox isolation**.

---

## How Has This Been Tested?

Verified that the new link is accessible and points to the correct
repository. All descriptions and formatting remain consistent with other
community entries.

---

## Breaking Changes

No breaking changes — documentation update only.

---

## Types of changes

* [x] Documentation update

---

## Checklist

* [x] I have verified the new link and repository name
* [x] I have followed the repository’s documentation style
* [x] The update aligns with MCP community contribution guidelines

---

## Additional context

This change reflects a **repository rename** for clarity and branding
consistency. The project functionality and scope remain the same.
2025-11-05 10:15:21 +02:00
..
explanations Add presentation from MCP Dev Summit October 2025 (#624) 2025-10-07 12:56:40 +03:00
guides Implement --token and MCP_GITHUB_TOKEN login support (#705) 2025-10-29 17:23:41 +02:00
reference Enable Google KMS and Azure Key Vault for publisher login tool (#696) 2025-10-29 13:23:20 +00:00
community-projects.md docs(community): update project link and name to ToolSDK MCP Registry (#747) 2025-11-05 10:15:21 +02:00
README.md Add community-projects reference document (#569) 2025-09-29 21:38:46 +01:00
terms.md Add terms of service documentation (#346) 2025-09-05 00:35:24 +01:00

MCP Registry Documentation

The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.

I want to...

Documentation Index