Cursor MCP vs SkeletIQ
A side-by-side look at the Cursor MCP and SkeletIQ MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Cursor MCPCoding Agents · Local subprocess (stdio)Cursor's agent (cursor-agent CLI) through MCP: any model your plan offers, resumable sessions.56GoodAuth: not declaredVerdict: choose Cursor MCP for coding agents work as a local process; choose SkeletIQ for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Cursor MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CURSOR_MAX_CONCURRENCY, CURSOR_ALLOW_YOLO, CURSOR_SANDBOX, CURSOR_KILL_GRACE_MS. - You want tools like
cursor_agent, cursor_reply, cursor_models.
Choose SkeletIQ when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SKELETIQ_API_KEY, SKELETIQ_API_URL. - You want tools like
list_projects, get_design, generate_architecture.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Cursor MCP | |
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 56/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CURSOR_MAX_CONCURRENCYCURSOR_ALLOW_YOLOCURSOR_SANDBOXCURSOR_KILL_GRACE_MS | SKELETIQ_API_KEYSKELETIQ_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 6 |
| Full listing | View Cursor MCP | View SkeletIQ |
Tools & capabilities
Cursor MCP tools 5
cursor_agentExecute a prompt using Cursor's AI agentcursor_replyContinue an existing agent sessioncursor_modelsList the model ids the installed CLI offerscursor_sessionsList agent sessions (this server instance)cursor_healthCheck installation, auth, and config
SkeletIQ tools 6
list_projectsFind a project by name. Returns the candidates rather than guessing between them.get_designRead a design, in one of six modes: `overview`, `component`, `brief`, `readiness`, `build_order`, `gaps`. Where a version records its requirements, `overview` and `component` resolve the design's `R`-ids to the requirements they name, and say what became of each.generate_architectureDesign a system from a prompt. Spends credits and takes minutes. A prompt that states no load comes back with a question instead, and nothing is charged: ask your human, and answer "Not sure yet" when they do not know rather than guessing.get_generation_statusPoll a generation started with `wait: false`.critique_architectureCheck a design against SkeletIQ's rules. Deterministic, free, stores nothing. Tell it the `domain` and the `exposure`.check_driftReport what you built; hear what is missing, half done, or not in the design.
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.
Cursor MCP
{
"mcpServers": {
"cursor-mcp": {
"command": "npx",
"args": [
"-y",
"@qmediat.io/cursor-mcp"
],
"env": {
"CURSOR_MAX_CONCURRENCY": "YOUR_CURSOR_MAX_CONCURRENCY_HERE",
"CURSOR_ALLOW_YOLO": "YOUR_CURSOR_ALLOW_YOLO_HERE",
"CURSOR_SANDBOX": "YOUR_CURSOR_SANDBOX_HERE",
"CURSOR_KILL_GRACE_MS": "YOUR_CURSOR_KILL_GRACE_MS_HERE"
}
}
}
}
SkeletIQ
{
"mcpServers": {
"skeletiq-2": {
"command": "npx",
"args": [
"-y",
"@skeletiq/mcp"
],
"env": {
"SKELETIQ_API_KEY": "YOUR_SKELETIQ_API_KEY_HERE",
"SKELETIQ_API_URL": "YOUR_SKELETIQ_API_URL_HERE"
}
}
}
}
Frequently asked questions
Cursor MCP is categorized under Coding Agents and uses a local stdio subprocess. SkeletIQ belongs to Coding Agents and uses a local stdio subprocess. Pick Cursor MCP for coding agents work and SkeletIQ for coding agents.
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.
Cursor MCP has no declared pricing — check the project's own site. SkeletIQ 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 cursor-mcp and skeletiq-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cursor MCP has a quality signal of 56/100 (Good) with 2 views, 0 installs and 1 GitHub stars. SkeletIQ has 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars.