Mcp Ts Core
Ship custom MCP servers in TypeScript with declarative tool definitions instead of hand-rolling protocol plumbing for every integration.
Overview
io.github.cyanheads/mcp-ts-core is a Build-phase MCP framework that helps you author TypeScript MCP servers with declarative definitions and stdio or HTTP transport.
What is this MCP server?
- Agent-native TypeScript framework @cyanheads/mcp-ts-core v0.9.9
- Declarative MCP server and tool definitions
- Stdio and streamable-http (localhost:3010/mcp) transport options via npm scripts
- MCP_LOG_LEVEL for structured server logging
- Bun runtime hint for published package workflows
- Framework package version 0.9.9
- Transports: stdio and streamable-http at http://localhost:3010/mcp
- npm @cyanheads/mcp-ts-core with start:stdio and start:http scripts
Community signal: 145 GitHub stars.
What problem does it solve?
Every new MCP integration becomes bespoke protocol and boilerplate code, slowing solo builders who need repeatable server structure.
Who is it for?
Indie developers and agent-tooling authors shipping one or more custom MCP servers in TypeScript.
Skip if: Non-developers who only need to install finished MCP servers, or teams committed to Python-only MCP stacks without TS investment.
What do I get? / Deliverables
You scaffold MCP servers on a shared TypeScript core with declarative definitions and choosable stdio or streamable-http startup scripts ready for your client config.
- Reusable TypeScript MCP server foundation with declarative definitions
- Stdio or streamable-http transport wiring via published npm scripts
- Configurable MCP_LOG_LEVEL logging for local and staged servers
Recommended MCP Servers
Journey fit
Framework code for MCP belongs under Build agent-tooling when solo builders extend what their agents can call; it is infrastructure for integrations, not a Grow or Operate runtime monitor. mcp-ts-core is agent-native server authoring—declarative definitions, stdio and streamable-http transports—so your product’s MCP surface matches how Claude Code and peers consume tools.
How it compares
MCP server framework library, not a ready-made third-party API connector.
Common Questions / FAQ
Who is mcp-ts-core for?
Solo builders and small teams writing TypeScript MCP servers who want declarative definitions and shared transport patterns instead of one-off protocol code.
When should I use mcp-ts-core?
Use it during Build when you are creating agent-tooling or product MCP endpoints and need a consistent TS foundation before publishing npm packages or private servers.
How do I add mcp-ts-core to my agent?
Add @cyanheads/mcp-ts-core as a dependency in your server project, implement tools with its declarative APIs, run start:stdio or start:http, then point your MCP client at your built server—not at the core package alone.