Kibi MCP vs Spec Driven Development
A side-by-side look at the Kibi MCP and Spec Driven Development MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kibi MCP for coding agents work as a local process; choose Spec Driven Development 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?
Choose Kibi MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Choose Spec Driven Development when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 48/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 10 | 439 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Kibi MCP | View Spec Driven Development |
Tools & capabilities
Kibi MCP tools
No tool names declared yet. Check the project README from the listing page.
Spec Driven Development 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.
Kibi MCP
{
"mcpServers": {
"kibi-mcp": {
"command": "npx",
"args": [
"-y",
"--no-install",
"kibi-mcp"
]
}
}
}
Spec Driven Development
{
"mcpServers": {
"spec-driven-development": {
"command": "npx",
"args": [
"-y",
"mcp-server-spec-driven-development@latest"
]
}
}
}
Frequently asked questions
Kibi MCP is categorized under Coding Agents and uses a local stdio subprocess. Spec Driven Development belongs to Coding Agents and uses a local stdio subprocess. Pick Kibi MCP for coding agents work and Spec Driven Development 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.
Kibi MCP has no declared pricing — check the project's own site. Spec Driven Development 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 kibi-mcp and spec-driven-development as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kibi MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 10 GitHub stars. Spec Driven Development has 44/100 (Fair) with 1 views, 0 installs and 439 GitHub stars.