Framedeck MCP vs Targetprocess MCP Server
A side-by-side look at the Framedeck MCP and Targetprocess MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
Targetprocess MCP ServerProduct Management · Local subprocess (stdio)MCP server for Tartget Process52GoodAuth: not declaredVerdict: choose Framedeck MCP for product management work as a local process; choose Targetprocess MCP Server 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.
TChoose Targetprocess MCP Server when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_current_releases, get_release_bugs, get_release_features.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Targetprocess MCP Server | |
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 56/100 · Good | 52/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 8 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 32 | 79 |
| Full listing | View Framedeck MCP | View Targetprocess MCP Server |
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
Targetprocess MCP Server tools 79
get_current_releasesget_release_bugsget_release_featuresget_release_user_storiesget_release_user_stories_with_descriptionget_release_open_bugsget_release_open_user_storiesget_feature_contentget_feature_commentsget_feature_user_storiesget_not_covered_user_stories_in_featurecovered- +67 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"
}
}
}
}
Targetprocess MCP Server
{
"mcpServers": {
"targetprocess-mcp-server": {
"command": "npx",
"args": [
"-y",
"targetprocess-mcp-server"
]
}
}
}
Frequently asked questions
Framedeck MCP is categorized under Product Management and uses a local stdio subprocess. Targetprocess MCP Server belongs to Product Management and uses a local stdio subprocess. Pick Framedeck MCP for product management work and Targetprocess MCP Server 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. Targetprocess MCP Server 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 targetprocess-mcp-server 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 2 views, 0 installs and 1 GitHub stars. Targetprocess MCP Server has 52/100 (Good) with 0 views, 0 installs and 8 GitHub stars.