Skip to content

Add MCP registry cheat sheet project link#600

Merged
domdomegg merged 1 commit intomodelcontextprotocol:mainfrom
subbyte:cheat-sheet-link
Oct 2, 2025
Merged

Add MCP registry cheat sheet project link#600
domdomegg merged 1 commit intomodelcontextprotocol:mainfrom
subbyte:cheat-sheet-link

Conversation

@subbyte
Copy link
Contributor

@subbyte subbyte commented Oct 1, 2025

Add the MCP registry cheat sheet project link in /docs/community-projects.md

Motivation and Context

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?

No test needed.

Types of changes

  • 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)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

@domdomegg domdomegg merged commit b04b013 into modelcontextprotocol:main Oct 2, 2025
3 checks passed
slimslenderslacks pushed a commit to slimslenderslacks/registry that referenced this pull request Dec 18, 2025
<!-- 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 modelcontextprotocol#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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants