| Filename | Latest commit message | Latest commit date |
|---|---|---|
b04b013246<!-- Provide a brief summary of your changes --> Add the MCP registry cheat sheet project link in `/docs/community-projects.md` ## Motivation and Context <!-- Why is this change needed? What problem does it solve? --> It will be beneficial to have a cheat sheet that describes what are the spaces of docs, organizes the spaces, and provides references to detailed docs/guides/references. With such cheat sheet, new users would quickly navigate in different spaces and find what commands and docs they need. More discussion at #540 ## How Has This Been Tested? <!-- Have you tested this in a real application? Which scenarios were tested? --> No test needed. ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [x] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [x] My code follows the repository's style guidelines - [x] New and existing tests pass locally - [ ] I have added appropriate error handling - [x] I have added or updated documentation as needed |
||
| .. | ||
| explanations | ||
| guides | ||
| reference | ||
| community-projects.md | ||
| README.md | ||
| terms.md | ||
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...
- 📤 Publish my MCP server → Publishing Guide
- 📥 Consume registry data → API Usage Guide
- 🔌 Understand the registry's purpose → Ecosystem vision
- 📋 Look up specific information → server.json spec | API spec | CLI reference
- 🤝 Add reference to my community project → Community Projects