Log inSubmit server

Testkube MCP vs MCP Ts Core

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

Testkube MCP logoTestkube MCPDeveloper ToolsMCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants41FairAuth: not declaredMCP Ts Core logoMCP Ts CoreDeveloper Tools · Local subprocess (stdio)TypeScript framework for building MCP servers with declarative definitions and observability.51GoodAuth: not declared

Verdict: choose Testkube MCP for developer tools work; choose MCP Ts Core 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?

Testkube MCP logoChoose Testkube MCP when

  • You need dedicated capabilities in the Developer Tools domain.
Explore Testkube MCP

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTestkube MCP logoTestkube MCPMCP Ts Core logoMCP Ts Core
CategoryDeveloper ToolsDeveloper Tools
Quality signal41/100 · Fair51/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,674152
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Testkube MCP View MCP Ts Core

Tools & capabilities

Testkube MCP tools

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

MCP Ts Core 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.

Testkube MCP

No confirmed install command for Testkube MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

MCP Ts Core

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

Frequently asked questions

Testkube MCP is categorized under Developer Tools and uses an install path we have not confirmed yet. MCP Ts Core belongs to Developer Tools and uses a local stdio subprocess. Pick Testkube MCP for developer tools work and MCP Ts Core 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. Testkube MCP has no confirmed install command yet — follow its own setup instructions.

Testkube MCP has no declared pricing — check the project's own site. MCP Ts Core 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 testkube-mcp and mcp-ts-core as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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

Popular comparisons with Testkube MCP

Popular comparisons with MCP Ts Core