plaky115-mcp
MCP server for the Plaky project management API. Provides 32 generated and 7 curated tools for spaces, boards, items, comments, and more, with safe defaults and dry-run mutations.
README
plaky115 · Python SDK + MCP server for Plaky
A clean, typed Python SDK and a Model Context Protocol server for the
Plaky public API — every documented operation, one
wheel, no surprises. Ported from the pinned TypeScript source
apet97/plaky115 (33ae2926, v1.0.11)
with behavior-level parity tests.
Plaky115 is unofficial and independent. It is not affiliated with, endorsed by, or sponsored by Plaky or CAKE.com. “Plaky” and “CAKE.com” are trademarks of their respective owners.
Install
pip install plaky115 # SDK only
pip install "plaky115[mcp]" # SDK + MCP server
Python 3.11+. One dependency stack: httpx2 + pydantic v2 (+ the
official mcp v2 SDK behind the extra).
Highlights
- All 32 public operations across nine resources — spaces, boards, items, comments, reactions, users, teams, item groups, item files — each pinned by contract descriptors and cross-surface parity tests.
- Async-first with a real sync client.
AsyncPlakyClientandPlakyClientshare pure logic only; the sync client never touches an event loop. - Safe under failure. Only GET requests retry (equal-jitter backoff,
bounded
Retry-After); writes make exactly one network attempt — even with an idempotency key. Mutation receipts recordattempted/mayHaveCommittedconservatively. - Strict wire contracts. Paged roots must be
{"data": [...], "hasMore": bool}; unsafe int64 JSON integers survive as exact decimal strings; bodies are bounded (16 MiB default / 64 MiB max); redirects are never followed;plk_keys are redacted everywhere. - Batteries for real workflows. Resolvers (exact-ID fast path, one
bounded list for text refs), field builders, bounded chunk readers with
exact
{page, index}continuation, deterministic spreadsheet-safe CSV/JSONL export, bulk updates with durable receipts. - Deterministic generation. OpenAPI contract → models and raw MCP
tools are committed, drift-checked artifacts;
scripts/generate.py --checkfails CI on a single changed byte.
SDK quick start
from plaky115 import AsyncPlakyClient
async with AsyncPlakyClient(api_key="...") as plaky:
page = await plaky.spaces.list(page_size=50)
for space in page.data:
print(space.id, space.title)
from plaky115 import PlakyClient
with PlakyClient(api_key="...") as plaky:
for space in plaky.spaces.iterate(page_size=100):
print(space.id, space.title)
The API key is sent only in the X-API-Key header, only to the configured
HTTPS origin. Python surfaces are snake_case; wire names stay Plaky
camelCase via model aliases.
MCP server
export PLAKY115_API_KEY=... # environment only; never an argument
plaky115-mcp --transport stdio # local hosts
plaky115-mcp --transport streamable-http --port 8000 # deployment
- Safe by default:
curatedmode +readscope. Write and destructive tools mount only with explicit flags; mutation workflows default to dry-run. - Two tool surfaces: 32 generated raw tools (one per operation) and 7
curated tools with 11 workflow IDs (
workspace.map,items.search,comments.thread,export.items,items.create,items.updateFields,comments.add,itemGroups.create,itemGroups.update,itemFiles.upload,itemFiles.update). - Structured everything: every tool publishes success and error output schemas; known failures return a typed envelope with attempt state; results are capped at 128 KiB with exact continuations.
- Hardened HTTP: stateless Streamable HTTP with request-scoped SSE,
36 MiB body cap, DNS-rebinding protection, loopback-default binding,
secret-free
/healthz. Uploads accept canonical base64 + metadata — never local paths.
Host config example: examples/mcp_stdio.json.
Deployment notes: docs/mcp.md and
docs/deploy-cloudflare.md.
Documentation
| Guide | Contents |
|---|---|
| docs/sdk.md | Clients, options, resources, errors, pagination |
| docs/mcp.md | Modes, scopes, result contracts, deployment |
| docs/compatibility-inventory.md | All 32 operations mapped to SDK + MCP names |
| docs/api-behavior.md | Wire-level behavior notes |
| docs/security.md · SECURITY.md | Credential and transport policy |
| docs/contract-evolution.md | fetch → diff → accept → regenerate |
| docs/live-certification.md | Read/write live gates |
Development
uv sync --all-extras --group dev
uv run pytest # 309 tests
uv run python scripts/verify.py --offline # full release-grade gate
The offline verifier checks: parity inventories, contract + generation
determinism, format/lint, strict pyright, tests with branch coverage,
example syntax, docs gates, wheel/sdist build, twine, fresh-environment
package smoke (base install without mcp, installed-wheel typing proof),
four-scope secret scan, and lock integrity. The read-only live
certification exercises all 17 read operations across four independent
surfaces.
License
MIT — see LICENSE. Retains the upstream copyright notice from the pinned source.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.