← Back to directory
M

MCP TypeScript Core Server

Community
Agent-native TypeScript framework for building MCP servers
GitHub source repository ↗
★ 148 Stars Category · Dev Tools Popular Source revision 8b14ca68d8c0
33FMRS · D
Reliability
2/20
Security and permissions
8/20
Maintenance
10/20
Documentation
10/20
Setup experience
3/20

This server is a scaffold powered by the mcp-ts-core framework and currently includes no predefined tools. It is suitable for developers as a starting point but not for non-technical users directly.

Read the FMRS scoring method →

This is a scaffold server generated by the @cyanheads/mcp-ts-core framework, which is designed for building MCP servers. The framework provides declarative definitions (tools, resources, prompts), authentication (JWT/OAuth), multi-backend storage (in-memory, filesystem, Supabase, Cloudflare D1/KV/R2), OpenTelemetry observability, and first-class support for Bun, Node.js, and Cloudflare Workers. This server acts as a demonstration of the framework's capabilities; actual tools are defined by the developer in the generated project.

Tools

The tool list has not been reviewed yet.

Setup

  1. Ensure Node.js and npm are installed.
  2. Start the server using npx -y @cyanheads/mcp-ts-core run start:stdio.
  3. Set environment variables as needed (e.g., MCP_LOG_LEVEL).
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-ts-core-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/mcp-ts-core",
        "run",
        "start:stdio"
      ],
      "env": {
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Fit and risk

Best for

  • TypeScript developers looking to quickly scaffold an MCP server
  • Teams needing extensible MCP server infrastructure
  • Experimental projects or proof-of-concepts

Not for

  • End-users requiring out-of-the-box production tools
  • Scenarios needing ready-made domain-specific functionality
  • Those who do not wish to implement their own tool definitions

Required permissions

  • Network access (if tools call external APIs)
  • Filesystem access (depending on storage backend)
  • Environment variable configuration

Risks and side effects

  • The framework is likely under active development, APIs may change
  • Default security configuration may be insufficient; adjust for production
  • Dependencies may introduce vulnerabilities; keep updated

Troubleshooting

  1. Ensure Node.js version compatibility (TypeScript ^7.0.2 recommended)
  2. Check that environment variables are set correctly
  3. Check logs (MCP_LOG_LEVEL) for error messages

Use cases

As a starting point for building MCP servers in TypeScript
To test interactions between MCP clients and a framework-based server
As a scaffold for developing custom MCP servers

Supported clients

Claude DesktopFull support

More servers from this repository