MCP Ts Core vs Val Town

A side-by-side look at the MCP Ts Core and Val Town MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP Ts Core logoMCP Ts CoreDeveloper Tools · Local subprocess (stdio)TypeScript framework for building MCP servers with declarative definitions and observability.51GoodAuth: not declaredVal Town logoVal TownDeveloper Tools · Local subprocess (stdio)Deploy serverless TypeScript on Val Town: HTTP vals, cron, SQLite, email, OAuth.47FairAuth: not declared

Verdict: choose MCP Ts Core for developer tools work as a local process; choose Val Town for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

MCP Ts Core logoChoose MCP Ts Core when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore MCP Ts Core

Val Town logoChoose Val Town when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Val Town

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Ts Core logoMCP Ts CoreVal Town logoVal Town
CategoryDeveloper ToolsDeveloper Tools
Quality signal51/100 · Good47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars15210
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

MCP Ts Core tools

No tool names declared yet. Check the project README from the listing page.

Val Town tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

MCP Ts Core

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-ts-core": {
      "command": "bunx",
      "args": [
        "@cyanheads/mcp-ts-core"
      ]
    }
  }
}

Val Town

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "val-town": {
      "command": "npx",
      "args": [
        "-y",
        "@changesets/cli"
      ]
    }
  }
}

Frequently asked questions

MCP Ts Core is categorized under Developer Tools and uses a local stdio subprocess. Val Town belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Ts Core for developer tools work and Val Town for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

MCP Ts Core has no declared pricing — check the project's own site. Val Town has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mcp-ts-core and val-town as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Ts Core has a quality signal of 51/100 (Good) with 2 views, 0 installs and 152 GitHub stars. Val Town has 47/100 (Fair) with 1 views, 0 installs and 10 GitHub stars.