Add mcp-core toolkit to framework list in README#4202
Open
pandaGaume wants to merge 1 commit into
Open
Conversation
Added a new modular MCP toolkit entry to the README.
pandaGaume
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
@cyanmycelium/mcp-coreto the Frameworks → For servers section.What it is
Engine-neutral, transport-agnostic Model Context Protocol primitives for TypeScript, distributed as composable ESM subpath exports:
@cyanmycelium/mcp-core- core primitives: behaviors, adapters, grammars, and shared types@cyanmycelium/mcp-core/server- server building blocks@cyanmycelium/mcp-core/client- client building blocks@cyanmycelium/mcp-core/llm- LLM bridge@cyanmycelium/mcp-core/node- Node.js runtime adapterThe grammars layer is modular: multiple grammar implementations can be registered and selected per source/target pair (different LLM providers, message dialects, or prompt formats) and per locale, enabling internationalization of generated prompts and tool descriptions without forking the core.
The package leaves transport, runtime, and LLM provider choices to the consumer, making it a low-level alternative to opinionated frameworks already listed in this section.
Why it fits this section
It complements existing entries (FastMCP, ModelFetch, MCP-Framework, etc.) by targeting a different audience: developers who want to assemble their own MCP server or client from primitives rather than start from a high-level framework. Two features that aren't commonly exposed by other frameworks in this section:
The granular subpath exports also let consumers import only what they need (smaller install footprint when only
/clientor/llmis required).Checklist
main(lint, build, vitest)