MCP Ts Core vs Testkube MCP
A side-by-side look at the MCP Ts Core and Testkube MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Ts Core for developer tools work as a local process; choose Testkube MCP for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Ts Core when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose Testkube MCP when
- You need dedicated capabilities in the Developer Tools domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 152 | 1,674 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Ts Core | View Testkube MCP |
Tools & capabilities
MCP Ts Core tools
No tool names declared yet. Check the project README from the listing page.
Testkube MCP 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": {
"mcp-ts-core": {
"command": "bunx",
"args": [
"@cyanheads/mcp-ts-core"
]
}
}
}
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.