MCP Ts Core vs Apifable
A side-by-side look at the MCP Ts Core and Apifable 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 Apifable 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 Apifable 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
get_spec_info, list_endpoints_by_tag, search_endpoints.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 152 | 10 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View MCP Ts Core | View Apifable |
Tools & capabilities
MCP Ts Core tools
No tool names declared yet. Check the project README from the listing page.
Apifable tools 7
get_spec_infoReturns the API title, version, description, servers, and all tags with their endpoint counts. Start here to understand the shape of an unfamiliar spec.list_endpoints_by_tag**Inputs:**search_endpoints**Inputs:**get_endpoint**Inputs (choose one):**search_schemas**Inputs:**get_schema**Inputs:**get_types**Inputs (choose one mode):**
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"
]
}
}
}
Apifable
{
"mcpServers": {
"ycs77-apifable": {
"command": "npx",
"args": [
"-y",
"apifable@latest"
]
}
}
}
Frequently asked questions
MCP Ts Core is categorized under Developer Tools and uses a local stdio subprocess. Apifable belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Ts Core for developer tools work and Apifable 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. Apifable is listed as free. 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 ycs77-apifable 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. Apifable has 57/100 (Good) with 3 views, 0 installs and 10 GitHub stars.