MCP Ts Core vs MCP Server
A side-by-side look at the MCP Ts Core and MCP Server 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 MCP Server 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?
Choose MCP Ts Core when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, search_model.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 152 | 117 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View MCP Ts Core | View MCP Server |
Tools & capabilities
MCP Ts Core tools
No tool names declared yet. Check the project README from the listing page.
MCP Server tools 2
search_docsThis tool uses vector embeddings to locally search through preprocessed CAP documentation, stored as embeddings. The process works as follows:search_modelThis tool performs fuzzy searches against names of definitions from the compiled CDS model (Core Schema Notation).
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"
]
}
}
}
MCP Server
{
"mcpServers": {
"mcp-server-107": {
"command": "npx",
"args": [
"-y",
"@cap-js/mcp-server"
]
}
}
}
Frequently asked questions
MCP Ts Core is categorized under Developer Tools and uses a local stdio subprocess. MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Ts Core for developer tools work and MCP Server 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. MCP Server has no declared pricing — check the project's own site. Auth: no auth required. 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 mcp-server-107 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. MCP Server has 64/100 (Good) with 4 views, 0 installs and 117 GitHub stars.