# AI Agents - Kanera

> Kanera does not run your AI agents; it is where they report. Connect Claude, ChatGPT, Codex, Copilot, or Cursor through a native MCP server, a CLI, or a TypeScript SDK, and every change they make is attributed and visible on the board.

Canonical page: https://www.kanera.app/en-US/ai-agents

Copy AI agent setup

# All AI agents welcome. They can do anything you can do.

Kanera does not run your agents. Claude, Codex, and Cursor keep working wherever you already use them, and report here: they pick up cards, show live progress on the board, and flag when they need a person. Every change carries the agent's name, and there is no AI surcharge.

[Start free](https://board.kanera.app/signup)[Connect an agent](https://www.kanera.app/docs/en-US/ai-mcp)

Setup guides [Claude](https://www.kanera.app/docs/en-US/ai-mcp-claude)[ChatGPT](https://www.kanera.app/docs/en-US/ai-mcp-chatgpt)[Codex](https://www.kanera.app/docs/en-US/ai-mcp-codex)[GitHub Copilot](https://www.kanera.app/docs/en-US/ai-mcp-github-copilot)[Cursor](https://www.kanera.app/docs/en-US/ai-mcp-cursor)[OpenCode](https://www.kanera.app/docs/en-US/ai-mcp-opencode)[Gemini CLI](https://www.kanera.app/docs/en-US/ai-mcp-gemini-cli)

Where agents report

## You can always tell what the agent did.

Agents already run in your terminal, your editor, and your chat app. Kanera gives them a shared place to report back: it writes down which agent acted and who it acted for, shows the work while it is still happening, and tells you about it afterwards.

View A live run on the tile: who is working, on what, and whether they are stuck.

View Open the card to see the live run; when it ends, the outcome joins the activity trail.

Labelled by the agent that did it Every comment, card change, and activity row an agent writes is recorded as the agent's, alongside the person it acted for. Feeds and comment headers carry a "via Claude" badge, so nothing an assistant did ever reads as somebody's own handiwork later.

The board shows who is working now Before it starts, an agent opens a run on the card. The tile carries a live chip naming the agent and the job, turns amber when the agent is waiting on a person, and clears when the run ends. A run that stops reporting is marked stalled rather than spinning forever.

You hear what your own agent did Kanera does not notify you about your own actions — it makes an exception for your agent. What it changed while you were elsewhere lands in your inbox grouped as "you via Claude", so delegating work never means losing track of it.

[How agent attribution and runs work](https://www.kanera.app/docs/en-US/ai-mcp)

What people ask it for

## The work you keep meaning to do and never quite get to.

An agent connected to Kanera works from live boards across every workspace your identity can reach, not from a stale export or a summary someone pasted in.

What changed on the Delivery boards this week?

Weekly status without asking anyone The agent reads activity across every board you can see and writes the summary you would have chased six people for.

What is overdue and who is blocked?

Triage what slipped Read whole blocking chains in one call, find upstream prerequisites and downstream work, and follow ready-to-start handoffs across accessible boards.

Prepare my standup from my Up next queue.

Standup, prepared Your ranked queue and assigned work, read the same way the app reads it, turned into three sentences.

Turn this thread into cards on the Support board.

Capture without retyping The agent already has the conversation. It writes the cards, the checklists, and the labels in one pass.

Which cards reference the auth migration?

Find things you half-remember Search across cards, comments, notes, and attachments, then follow the links rather than reporting a list.

Audit the release board before we cut 2.0.

Check the work before it ships Unchecked checklist items, unassigned cards, stale columns. The pass nobody has time to do by hand.

Remind me to renew the venue insurance next week.

An inbox that needs no board Name no board and the task lands in your private Scratchpad inbox instead of a question about where it goes. Dates read the way you said them, in your time zone.

Attach the failing test log and a screenshot to DEV-938.

Evidence on the card, not in the chat An agent on your machine uploads files straight to the card through a one-time link, so long logs and screenshots never squeeze through a message.

What does the error in the attached screenshot say?

Reads what the team attached Images come back as images and logs as text, so the agent answers from the files already on the card.

[More prompts and workflows](https://www.kanera.app/docs/en-US/ai-mcp-examples)

Three ways in

## Whichever agent you have, there is a way in for it.

All three reach the same work, and all three stay inside your permissions. Most people need only the middle one, and it takes about a minute.

When your agent lives in a terminal

### The Kanera CLI

Your coding agent is already in a terminal, working on the thing a card describes. One install later it can read that card, comment on it, and close it when the work lands — so the board keeps up with the branch without anyone stopping to update it. Useful for you too: see what is on your plate without leaving the editor.

kanera setup claude also teaches your agent how to use Kanera properly.

[CLI documentation](https://www.kanera.app/docs/en-US/cli)

bash

# install once npm install --global @kanera/cli kanera auth login   # then work kanera work kanera card done MKT-42 kanera comment MKT-42 "Shipped."

The one most people want

### The MCP server

Approve Kanera inside Claude, ChatGPT, Codex, Copilot, Cursor, OpenCode, or Gemini CLI once, in a browser — no key to create, nothing to paste — and from then on you just ask. It sees exactly what you see and nothing you cannot, and you can disconnect it from your profile at any point.

Headless client with no browser? Device authorization is supported too.

[Connect an agent](https://www.kanera.app/docs/en-US/ai-mcp)

text

# the hosted endpoint https://mcp.kanera.app/mcp   # or your own deployment https://mcp.your-kanera.example/mcp

When you want to build it yourself

### The TypeScript SDK

For the agent that runs every Monday morning, the bot inside your own product, or the script that does the reporting nobody wants to do. Typed, dependency-free, and MIT licensed, so it runs anywhere you deploy and raises no questions from a legal review.

Signature checks, retries, and paging through long lists are already handled.

[SDK documentation](https://www.kanera.app/docs/en-US/sdk)

ts

const kanera = new Kanera({ apiKey });   // every list endpoint iterates for await (const card of kanera.work.iterateCards()) { console.log(card.key, card.title); }

Built for a moving target

## The best AI keeps changing. Yours should be free to.

Almost every project tool bolted a chatbot into the corner, picked one model, and asked you to live with it. Twelve months later that choice looks dated and you are stuck with it. Kanera built the doors instead, so the AI on the other side is always the one you rate today — not the one we happened to sign with.

Use the one you already know You have a favorite. Your designer has a different one, and your engineers have opinions about both. Nobody has to learn a second-rate assistant bolted into a project tool just to get their work updated — everyone brings what they are already fluent in.

Swap it whenever something better lands Kanera speaks MCP, REST, and a plain command line — the standards agents already use. When the thing everyone is talking about next quarter arrives, you point it at the same address and carry on. No migration, and no waiting for us to add an integration.

It gets better without us shipping a thing Every time your agent gets smarter, faster, or picks up a new skill, your Kanera workflow gets it too — the same afternoon, at no cost to you. A bundled chatbot only improves when the company that bundled it decides to improve it.

What it costs

## Bring your agent on every plan, Free included.

Connect Claude, ChatGPT, Cursor, or the CLI on the Free plan and let it read and update your boards. No AI add-on, no per-agent fee, no token bill, just fair-use limits on how fast agents can work.

Pro, at $5 per user per month, gives agents higher limits and adds unattended service agents and workspace API keys that run without anyone signed in. Host Kanera yourself and it is all switched on, with no plan checks anywhere in it.

[See pricing](https://www.kanera.app/en-US/pricing)[Run it yourself](https://www.kanera.app/en-US/self-hosted-trello-alternative)

Hosted Connect an agent in a browser and you are done. We run the address it talks to, keep it up, and keep it current. Interactive agents work on Free; unattended agents need Pro.

Self-hosted Run Kanera on your own hardware and everything here comes with it — your own agent address, the same tools, no plan checks, and nothing leaving your network that you did not send.

Common questions

## Questions about Kanera and AI

Which AI agents work with Kanera? Install the Kanera plugin in ChatGPT or supported Codex surfaces, then connect through OAuth. Other MCP-compatible clients can use the hosted server directly. Kanera publishes setup guides for Claude, ChatGPT, Codex, GitHub Copilot, Cursor, OpenCode, and Gemini CLI, and the hosted MCP endpoint works with anything else that speaks the protocol.

Agents that can only run shell commands do not need MCP at all. They can use the Kanera CLI, which exposes every MCP tool as a command.

Is there a Kanera CLI? Yes. The official kanera command-line interface is published on npm as @kanera/cli and needs Node 22 or newer. Install it with npm install --global @kanera/cli, or run npx @kanera/cli commands without installing.

It exposes the same tool layer as the MCP server, prints a machine-readable command catalog, and uses exit codes that tell an agent whether a write was refused or failed. Running kanera setup claude installs the Kanera Agent Skill for Claude Code.

Do I need to be a developer? No. In ChatGPT, install the Kanera plugin and connect your account through a browser consent screen. Claude and Copilot also connect through OAuth.

The CLI and SDK are there for the cases where you do want to build something, and the API reference documents every endpoint if you would rather work directly against HTTP.

Does Kanera have its own chatbot? No, and that is the point. The best AI changes every few months, and a chatbot bolted into a project tool is frozen at whatever its vendor picked. Kanera is built to be reachable instead: a native MCP server, a CLI, a TypeScript SDK, a complete REST API, and a published Agent Skill.

So you use the assistant you are already fluent in, your colleague uses theirs, and when something better lands next quarter you point it at the same address and carry on.

How does an agent connect? Use browser-based OAuth for a personal assistant when the client supports it. Use device authorization for a CLI or SSH session that cannot open a browser redirect. Use an unattended service connection for CI, cron, or server-side automation, and an API key for local clients or those that only accept a static credential.

What can an agent see? Exactly what the credential can see, and nothing more. A personal connection follows your current board access across workspaces, standalone boards, and guest boards, including your private personal notes.

An unattended service connection stays scoped to the single workspace or standalone board where it was created.

Can I stop an agent from changing my work? Yes. Create the personal API key as Read-only. That credential can list, read, search, and report, and Kanera refuses every write with a 403 at the API.

This matters because the refusal does not depend on the AI client honouring its own tool permissions. A confused or prompt-injected agent still cannot change a card, because the server will not let it.

Will an agent make a mess of my boards? Changes made through the API, MCP, or the CLI are recorded in card history like any other change, so you can see what happened and when.

For anything broad or sensitive, ask the agent to show a plan first, and give it a read-only credential until you trust it.

Is agent access included in my plan? Yes. Connecting your own AI agent over MCP or the CLI, and personal API keys, work on every plan. Free boards have fair-use limits on how fast agents can work; Pro boards allow more.

Unattended service agents and workspace API keys need Pro, the 30-day Pro trial, or self-hosted Kanera, which has no plan checks at all. If a hosted organization moves to Free, Kanera revokes its workspace API keys rather than deleting them; personal keys and interactive agent connections keep working. Upgrading again restores what was switched off.

Is my data used to train a model? Not by Kanera. Kanera never sends your work to a model provider, because Kanera does not call one.

When you connect an agent, your data goes wherever that agent sends it, under that vendor's terms. That is your choice to make and your relationship to manage, which is the point of keeping AI out of the product.

Can I run all of this on my own hardware? Yes. Self-hosted Kanera exposes its own MCP address, its own API, and works with the same CLI and SDK. Point them at your deployment and no request leaves your network except the ones your agent makes to its own model provider.

Get started

## Bring the agent. We built the door.

Connect in a browser with OAuth, or hand a read-only key to something that runs unattended. Either way, your work stays in Kanera and your choice of model stays yours.

[Start free](https://board.kanera.app/signup)[Connect an agent](https://www.kanera.app/docs/en-US/ai-mcp)

## Machine-readable resources

- [Kanera AI index](https://www.kanera.app/llms.txt)
- [Kanera documentation index](https://www.kanera.app/docs/llms.txt)
- [Agent discovery guidance](https://www.kanera.app/agents.md)