timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Find, read and manage cards on your Planka v2 boards: search, move, comment, edit, checklists.
Skills that teach the AI this kind of work; they work alongside this one
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect MCP server for Planka (unofficial) yet
MCP server for Planka (unofficial) runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect MCP server for Planka (unofficial)
Claude Code cannot connect MCP server for Planka (unofficial) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect MCP server for Planka (unofficial)
Cursor cannot connect MCP server for Planka (unofficial) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect MCP server for Planka (unofficial)
VS Code cannot connect MCP server for Planka (unofficial) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect MCP server for Planka (unofficial)
mcpb: …/planka-mcp-macos-arm64.mcpbmcpb: …/planka-mcp-macos-amd64.mcpbmcpb: …/planka-mcp-linux-amd64.mcpbBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026
The registry name was verified with the GitHub account sierikov, which owns the repo
Code last changed 4 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/sierikov-planka-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 4 days ago, and the latest version (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB, Docker on your computer.
In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
Search and read Empryo's documentation. Read-only, no auth, no local access.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| This one MCP server for Planka (unofficial) | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | Yes | Yes | No | No |
| Basic checks | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol server for Planka kanban boards. It lets Claude (or any MCP client) find, read, edit, comment on and move your cards without you opening Planka.
Unofficial. planka-mcp is a community project, not affiliated with or endorsed by PLANKA Software GmbH. PLANKA is their trademark.
Requires Planka v2.0 or later. Planka v1 has no per-user API keys and is not supported. The end-to-end tests run against Planka 2.2.1.
MCP Registry name: io.github.sierikov/planka-mcp
You talk about a ticket in plain words and the assistant does the rest: it finds the card, reads all of it, does the work, writes back and moves the card along. Every request runs as your own Planka user (through your API key, or your username and password in stdio mode), so Planka's own permissions apply and comments appear under your name.
Two flows it is built for:
What makes this server different from the other Planka MCP servers:
.mcpb bundles for Claude Desktop and a multi-arch Docker image.15 tools, all enabled by default. Reads are annotated read-only; creates and adds (create_card, add_comment, add_tasks) are marked non-destructive; updates are marked idempotent; deletes are marked destructive. Clients may still prompt for updates.
| Tool | What it does | Kind |
|---|---|---|
list_boards | List the projects you can see with their boards, optionally filtered by name | read |
get_board | Show a board as a kanban: lists in order, compact card lines, labels and members (no descriptions); the first 10 cards of each list (3 of a closed one), up to 100 with list | read |
search_cards | Find cards across boards by words and filters (board, project, list, label, assignee, archived) | read |
get_card | Everything about one card: description (verbatim markdown), labels, assignees, due date, stopwatch, task lists, attachments, custom fields, latest comments | read |
list_comments | Page through a card's older comments, newest first | read |
create_card | Create a card with labels, assignees, a due date and a position; a missing label is created only with create_labels | write |
move_card | Move a card to another list or board, or to the archive with list=archive | write (idempotent) |
update_card | Edit title, description, due date, labels, assignees or stopwatch; fields left out stay as they are | write (idempotent) |
add_comment | Comment on a card | write |
update_comment | Edit the text of a comment | write (idempotent) |
add_tasks | Append tasks, or links to other cards, to a checklist (created if missing); many per call | write |
update_tasks | Tick, untick or rename tasks, several in one call | write (idempotent) |
delete_card | Delete a card. Permanent: it does not go to Planka's trash; use move_card with list=archive to keep it | destructive |
delete_comment | Delete a comment | destructive |
delete_task | Delete a checklist task | destructive |
Your MCP client decides how to confirm writes. The split lets you auto-allow move_card and add_comment and still be asked before edits and deletes.
Dates are YYYY-MM-DD, or YYYY-MM-DD HH:MM when the time of day matters, in the server's time zone (set TZ to change it; the Docker image embeds the time zone database).
Every call runs as one Planka user, chosen in one of two ways:
Each person needs their own key for their own Planka user. In Planka 2.1 and 2.2, creating an API key is admin-only: the server rejects the request from a non-admin user. So:
Where the admin finds it (checked against Planka's source):
Copy the key right away: Planka shows it only once. Generating a new key later replaces the old one, which stops working. Treat the key like a password. It can do whatever its user can do in Planka.
Set PLANKA_USERNAME (your username or email) and PLANKA_PASSWORD instead of PLANKA_API_KEY. If all three are set, the username and password win, and the server logs that the key is ignored.
Pick the setup that fits. Stdio runs on your own machine with your own key or login; HTTP is a server you (or your team) host, where each client sends its own key.
Claude Code (stdio)
Download the binary for your platform from the latest release (planka-mcp-macos-arm64, planka-mcp-macos-amd64, planka-mcp-linux-amd64, planka-mcp-linux-arm64, planka-mcp-windows-amd64.exe, planka-mcp-windows-arm64.exe), make it executable, then (on macOS a downloaded, unsigned binary may be quarantined: run xattr -d com.apple.quarantine ./planka-mcp if it will not start):
claude mcp add planka \
-e PLANKA_URL=https://planka.example.com \ -e PLANKA_API_KEY=your-api-key \ -- /path/to/planka-mcp
Without a key, use your username and password instead:
claude mcp add planka \
-e PLANKA_URL=https://planka.example.com \ -e PLANKA_USERNAME=your-username \ -e PLANKA_PASSWORD='your-password' \ -- /path/to/planka-mcp
Use the https:// address. Over http:// the password travels unencrypted with the first request, before any redirect could help, so the server warns at startup when it would send a password to an http:// address on another machine. If http:// redirects, the server reports the address to use instead of following it.
Or build it yourself with Go 1.26: go install github.com/sierikov/planka-mcp/cmd/planka-mcp@latest (or @v0.1.0 for a specific release; the binary reports that module version).
Claude Code (HTTP)
Run the server somewhere your client can reach (see the Docker setup below), then add it with your own key in the Authorization header:
claude mcp add --transport http planka https://host/mcp \
--header "Authorization: Bearer "
The MCP endpoint is /mcp. Each person adds the server with their own key. Put TLS in front of it (see Security).
Claude Desktop (.mcpb)
Download the bundle for your platform from the latest release, open it (on macOS, if Gatekeeper blocks the bundled binary, it is quarantined as an unsigned download: see the xattr note in the Claude Code (stdio) setup), and Claude Desktop asks for your Planka URL and either your API key or your username and password (the key and password fields are marked sensitive).
| Platform | File |
|---|---|
| macOS (Apple Silicon) | planka-mcp-macos-arm64.mcpb |
| macOS (Intel) | planka-mcp-macos-amd64.mcpb |
| Windows (x64) | planka-mcp-windows-amd64.mcpb |
| Windows (arm64) | planka-mcp-windows-arm64.mcpb |
| Linux (x64) | planka-mcp-linux-amd64.mcpb |
| Linux (arm64) | planka-mcp-linux-arm64.mcpb |
The .mcpb format is for Claude Desktop. Other clients use the stdio or HTTP setups above.
Other clients (mcpServers JSON)
Most MCP clients (Cursor, Windsurf, VS Code, Claude Desktop without the bundle and others) take an mcpServers JSON block. For stdio, point it at the binary and pass your URL and key in env:
{
"mcpServers": { "planka": { "command": "/path/to/planka-mcp", "env": { "PLANKA_URL": "https://planka.example.com", "PLANKA_API_KEY": "your-api-key" } } } }
For a self-hosted HTTP server, give the /mcp URL and your own key in the Authorization header:
{
"mcpServers": { "planka": { "type": "http", "url": "https://host/mcp", "headers": { "Authorization": "Bearer " } } } }
Key names differ a little between clients (some want "type": "streamable-http", or serverUrl instead of url): check your client's MCP documentation.
Docker Compose, next to Planka (HTTP)
Add the server as another service in the compose file that runs Planka:
services:
planka: image: ghcr.io/plankanban/planka:2.2.1
planka-mcp: image: ghcr.io/sierikov/planka-mcp:latest restart: unless-stopped depends_on:
ports:
The image runs the HTTP transport by default and serves /mcp and GET /healthz on port 8080. It is a distroless, non-root image for li