Kelvia MCP server

Kelvia is a task manager that AI agents can operate through the Model Context Protocol. This server exposes 58 tools for boards, tasks, comments, worklogs, stages, members, invitations, tags, and a personal day planner.

Connect to the hosted endpoint with OAuth — one command, no token to paste. A local stdio mode exists for clients that cannot do remote MCP, and for CI. You need a Kelvia account first — sign up at kelvia.app.

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:

https://mcp.kelvia.app/mcp

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

claude mcp add --transport http --scope user kelvia https://mcp.kelvia.app/mcp
claude mcp list

Start Claude Code, en

... View full README on GitHub