Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@AgilePlace MCP Server Bulk create 30 cards on my 'Sprint 12' board"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AgilePlace demo-provisioning MCP server. Creates and shapes demo environments (boards, bulk cards, hierarchy) from Claude Desktop or Cursor. stdio transport, single-user.
Module | Role |
| Env-driven config + authed HTTP client (Bearer). |
| Board-list warm on first use; lazy per-board card types; label → ID resolution. |
| Throttles off |
| Bulk card creation. |
| stdio MCP entrypoint. |
Related MCP server: apollo-mcp
Sequential, self-throttling writes.
Max ~40 cards per call; larger batches rejected (chunk and retry).
Per-card clientKey correlation, echoed on results.
Error handling: retry (429 / 5xx / network), fail-card-continue (400 / 422 / 404), abort-batch (401 / 403), circuit breaker on repeated identical failures.
Partial success returns isError: false; cards in created[] should not be resubmitted.
Set credentials in the host config env block (claude_desktop_config.json or Cursor mcp.json). Not in source.
{
"mcpServers": {
"agileplace-v3": {
"command": "node",
"args": ["/absolute/path/to/src/server.mjs"],
"env": {
"AGILEPLACE_DEFAULT_URL": "https://<your-org>.leankit.com/io",
"AGILEPLACE_DEFAULT_TOKEN": "<token>"
}
}
}
}Run standalone:
node src/server.mjscreateCards — implemented.
updateCards / findCards / createBoard — not yet implemented.
Deferred: multi-environment routing, lane name resolution, OKR tools, whole-call idempotency, tasks extension.
Bulk-creates cards on one board. Use for new cards, not updates. Returns created[] with clientKey + the real id for a later connect pass; failed[] carries clientKey + title + reason. Pass type as a label ("Epic"); the tool resolves it. header is cosmetic and is not used to connect cards. One board per call. Max 40 cards per call — chunk larger sets and concatenate created[] before connecting. Partial success is normal: isError: false with some cards in failed[]. Cards in created[] already exist — NEVER resubmit those clientKeys. To complete a partial batch, resubmit only the failed[] (and any never-sent) cards. This applies to every partial result, not just retryAfter rate-limit cases. If retryAfter is set, wait that many seconds, then resubmit only the never-sent cards (not created[]). Never invent board, type, or lane ids. Attach to an existing parent with parentCards; otherwise create all cards first, then connect using the returned ids.
Inputs: cards (required), boardId (required). Returns: failed, created, summary, retryAfter
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
Only one tool exists, so there is no possibility of overlap or misselection. Its purpose is explicit: bulk-create cards on a board.
The single tool uses a clear verb_noun camelCase name, createCards, but there is no broader naming pattern to evaluate consistency across a set.
For an AgilePlace server, one tool covering only card creation is too narrow; agents will likely need other board, lane, and card lifecycle operations. The tool itself is substantial, but the server is under-scoped.
Only creation is exposed; there are no read, update, delete, search, or connect operations for cards or boards. Bulk creation is handled robustly, but most AgilePlace workflows hit dead ends.
Create and drive KanbanThing kanban boards. No account, no API key, board link required.
Manage Klaro Cards projects, boards, cards, dimensions and KPIs.
Read and update Markboard kanban boards: cards, checklists, labels, comments and files.
Read and write Less Annoying CRM contacts, notes, tasks, events, pipelines and groups.
