gonnagetapower/kelvia-mcp

Kelvia is a shared task manager for
people and coding agents. One concrete use: hand off an unfinished task from
Claude Code to Codex.
The guide includes a copyable repo-file handoff that works without Kelvia,
then shows when a shared task helps. Through the
Model Context Protocol, an agent can create
and update tasks, move work across a Kanban board, comment, log time, run stages,
and plan the day. Its changes stay visible and attributed in the same UI the
human uses.
The server exposes **58 tools** and works with Claude Code, Codex, Cursor, and
other MCP clients. The hosted endpoint uses OAuth, so there is no API token to
paste into the recommended setup. A local stdio mode is
available for CI and clients without remote MCP support.
**Try for free** ·
MCP documentation ·
Hosted endpoint
Connect in one command
| Client | Command |
|---|---|
| Claude Code | claude mcp add --transport http --scope user kelvia https://mcp.kelvia.app/mcp |
| Codex | codex mcp add kelvia --url https://mcp.kelvia.app/mcp |
| Cursor | Add https://mcp.kelvia.app/mcp in **Settings → Tools & MCP** |
The first connection opens Kelvia in the browser for OAuth approval. After it
connects, ask the client: List my Kelvia boards.
Why Kelvia MCP
- **Complete workflow coverage** — create and triage tasks, move work across a
board, log time, run stages, and plan a day. Not a read-only bridge.
- **Controlled write access** — agent keys have read/create/edit/delete scopes
intersected with the agent's role on each board.
- **Visible agent activity** — changes, comments, and worklogs appear in Kelvia;
supported task changes can be reverted by a human in the app.
- **Load only what you need** — toolsets let a client publish one
part of the product instead of all 58 tools.
- **Modern remote auth** — Streamable HTTP with OAuth 2.1 + PKCE, or a Bearer
token when an explicit agent identity is required.
- **A local option when you need one** — stdio for clients
without remote MCP support, for CI, and for keeping the key on one machine.
See it work
From the client side — one prompt, and the agent reads the board, decides what
matters, files a follow-up task and comments on the blocker:
A real session against mcp.kelvia.app, typeset from its transcript.
create_task really did create #17, and add_task_comment really did comment
on #9 — which is what the rest of this section shows.
And from the product side. Everything below was created by an agent over this
server — the board, the tasks, the discussion, and the logged time.
*Watch the same run as video*
Every change an agent makes is attributed to it and filterable, so a human can
review exactly what happened rather than trusting a summary:
The personal day planner is part of the surface too, so an agent can block out
the work it just triaged:
Hosted quick start (recommended)
The production endpoint is:
OAuth is the default. The client opens Kelvia in a browser, you approve access,
and the client stores and refreshes its OAuth credentials. No API token needs to
be pasted into a configuration file.
Claude Code
Start Claude Code, enter /mcp, choose kelvia, and complete **Authenticate** in
the browser. After authentication, verify the connection with:
Codex app, CLI, and IDE extension
The Codex app, CLI, and IDE extension share the same MCP configuration on a
Codex host. In an interactive Codex session, use /mcp to inspect the server.
Equivalent ~/.codex/config.toml:
Cursor
Add the server globally in ~/.cursor/mcp.json, or per project in
.cursor/mcp.json:
Open **Cursor Settings → Tools & MCP**, enable kelvia, and select **Connect** to
complete OAuth in the browser. Ask Cursor to list your Kelvia boards after it
reports the server as connected.
Agent-key authentication
OAuth acts as the approving Kelvia user. Use an agent key instead when the
connection needs its own identity, board membership, role, expiry, and granular