Akilat Spec Leave Manager MCP vs Kordoc
A side-by-side look at the Akilat Spec Leave Manager MCP and Kordoc MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Akilat Spec Leave Manager MCP for workplace & productivity work; choose Kordoc for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Akilat Spec Leave Manager MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
Choose Kordoc when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 29/100 · Emerging | 55/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 | 0 | 2,763 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Akilat Spec Leave Manager MCP | View Kordoc |
Tools & capabilities
Akilat Spec Leave Manager MCP tools
No tool names declared yet. Check the project README from the listing page.
Kordoc 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.
Akilat Spec Leave Manager MCP
No confirmed install command for Akilat Spec Leave Manager MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Kordoc
{
"mcpServers": {
"kordoc": {
"command": "npx",
"args": [
"-y",
"kordoc"
]
}
}
}