Framedeck MCP vs Ithura MCP
A side-by-side look at the Framedeck MCP and Ithura MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Framedeck MCP for product management work as a local process; choose Ithura MCP for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Framedeck MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FRAMEDECK_API_KEY. - You want tools like
list_boards, create_board, set_active_board.
Choose Ithura MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ITHURA_API_KEY, ITHURA_WORKSPACE_SLUG, ITHURA_API_URL. - You want tools like
list_projects, get_project, create_project.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 56/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | FRAMEDECK_API_KEY | ITHURA_API_KEYITHURA_WORKSPACE_SLUGITHURA_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 32 | 23 |
| Full listing | View Framedeck MCP | View Ithura MCP |
Tools & capabilities
Framedeck MCP tools 32
list_boardsList all projects/productions in Framedeckcreate_boardCreate a new project/board in Framedeckset_active_boardSet the active board/production context. Once set, other tools will use this board by default when no board is specified.get_active_boardShow which board/production is currently set as the active context.list_columnsList stages in a board. Uses active board if set and no board specified.list_labelsList all labels/tagscreate_labelCreate a new label/taglist_cardsList cards/frames with optional filters. Uses active board if set and no board specified.create_cardCreate a new card/frame. Uses active board if set, or Idea Pool as fallback for quick idea capture.update_cardUpdate an existing card/framemove_cardMove a card/frame to a different stagedelete_cardPermanently delete a card/frame- +20 more on the listing page
Ithura MCP tools 23
list_projectsList all projects in the workspaceget_projectGet a project by IDcreate_projectCreate a new project in the workspaceupdate_projectUpdate a projectlist_issuesList issues in a project. Supports filtering by state, label, priority, assignee, cycle, module.create_issueCreate a new issue in a projectget_issueGet a single issue by IDupdate_issueUpdate fields on an existing issuedelete_issueDelete an issue from a projectlist_statesList workflow states for a projectlist_labelsList labels for a projectcreate_labelCreate a new label in a project- +11 more on 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.
Framedeck MCP
{
"mcpServers": {
"lukaris-framedeck-mcp": {
"command": "npx",
"args": [
"-y",
"framedeck-mcp"
],
"env": {
"FRAMEDECK_API_KEY": "YOUR_FRAMEDECK_API_KEY_HERE"
}
}
}
}
Ithura MCP
{
"mcpServers": {
"mcp-102": {
"command": "npx",
"args": [
"-y",
"ithura-mcp"
],
"env": {
"ITHURA_API_KEY": "YOUR_ITHURA_API_KEY_HERE",
"ITHURA_WORKSPACE_SLUG": "YOUR_ITHURA_WORKSPACE_SLUG_HERE",
"ITHURA_API_URL": "YOUR_ITHURA_API_URL_HERE"
}
}
}
}
Frequently asked questions
Framedeck MCP is categorized under Product Management and uses a local stdio subprocess. Ithura MCP belongs to Product Management and uses a local stdio subprocess. Pick Framedeck MCP for product management work and Ithura MCP for product management.
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.
Framedeck MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Ithura MCP 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 lukaris-framedeck-mcp and mcp-102 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Framedeck MCP has a quality signal of 56/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Ithura MCP has 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars.
