One clear view. Keep work moving.
See what is assigned, what changed, what is blocked, and what has been completed across every project, client, and team.
Start free · Explore features · Read the docs · Explore dependencies · ·
Loading
Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.kanera.app/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http app.kanera-mcp https://mcp.kanera.app/mcpRun in a terminal.
{ "mcpServers": { "app.kanera-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.kanera.app/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
One clear view. Keep work moving.
See what is assigned, what changed, what is blocked, and what has been completed across every project, client, and team.
Start free · Explore features · Read the docs · Explore dependencies · ·
Manage Kanera workspaces, boards, cards, checklists, comments, notes, automations, and reports.
Kanera coordinates assigned, active, blocked, and completed work across projects, clients, and teams from one fast, polished workspace. It brings boards, structured tasks, dependency maps and timelines, notes, assignments, progress history, automation, and integrations into one focused system—more visibility than a basic Kanban board without the overhead of a heavyweight work suite.
Use the hosted service and get started in minutes, or self-host Kanera on your own infrastructure.
? to see what is available.Connect cards with Blocks, Blocked by, or Relates to relationships, including across boards. Kanera makes blocked work visible and shows when the last active prerequisite clears, helping the next person pick up the handoff.
Open Dependencies on a board, in My Cards, or in Team Cards. Follow the chain in Map, compare due weeks in Timeline, or read a numbered Steps list that adapts to your phone. On a workspace board, switch between the board's chains and the wider workspace while keeping each card's source and permissions intact.
Find Blocked, At risk, Start here, and Ready work without losing the chain around it. The biggest bottleneck points to the card holding up the most open work; Critical path highlights the longest routes by number of open cards. Timeline aligns every chain to shared due-week columns and marks prerequisites due after their dependents in amber.
In Map or Timeline, drag from a card's + handle to add a blocking link, or select a connector to remove it. Tap-to-link and keyboard controls work too, with Undo and Redo for your map edits. Changes update live, and agents can inspect the same chains through MCP, the CLI, SDK, or REST API.
Read the Dependencies view, timeline, and editing guide or learn about card relationships and blocking.
Organisation
├─ Workspace
│ └─ Board
│ └─ Card
└─ Standalone board
└─ Card
Use a workspace when several boards should follow the same operating model. Lists, labels, custom fields, checklist templates, and automations are configured once and used across its boards, keeping workflows and reporting consistent as projects grow.
That means a status like In Review or a field like Client has the same meaning everywhere—no rebuilding each board or reconciling mismatched setups later.
For work that does not need to share that setup, create a standalone board. It keeps its own lists, labels, custom fields, checklist templates, automations, members, access, and integrations independently of your workspaces.
Use Claude, ChatGPT, Codex, Cursor, or another agent you already work with to pick up cards, read their context, carry out tasks, and report back in Kanera. Agent work stays on the same boards as your team's work, with live progress, visible blockers, and a record of who did what for whom.
Start with the Agent Workflow template: Backlog → Agent Working → Waiting on Me → Review → Done. Describe the task on a card, then ask your agent to pick it up. Following Kanera's agent instructions, it moves the card as work starts, needs your input, or finishes. You review the result and decide when it belongs in Done.
The workflow combines ordinary cards with agent runs. Runs track a working session; card moves remain explicit actions by the agent or a person, so starting or finishing a run does not silently move the card.
An agent opens a run before multi-step work and updates it with a short progress note. Everyone viewing the board sees a live chip on the card; it turns amber when the agent is waiting on a person. Open the card to see the agent, its current work, and when it last reported. A pull request or session link can take you straight to the result.
When the run ends, its outcome and closing summary stay in the card's activity. Runs that stop reporting are marked stalled after fifteen minutes, so an interrupted agent does not leave work looking active. A blocked run makes the wait visible; the agent should also comment with its question so watchers and assignees are notified.
With an OAuth connection, comments and changes show the person the agent acted for plus a via Claude, via Codex, or other agent badge. That includes browser sign-in through the CLI: name the agent with kanera auth login --agent "Claude Code". Personal API keys attribute actions to their owner without a via badge; workspace and board keys use the key's name.
Your agent's changes can notify you even though it acts on your behalf. The Agent tab brings those updates together, and Work Done distinguishes agent output from your own actions. Agents still operate within the connected person's current board permissions, and read-only credentials prevent writes at the server.
Read more about agent runs, attribution, and the Agent Workflow template.
The CLI and the MCP server expose the same tool layer, so anything an agent can do over MCP it can also do with kanera from a shell. Try the CLI without installing it:
npx -y @kanera/cli commands
Read-only credentials are enforced by the server, and self-hosted Kanera exposes its own MCP address and API for the same CLI and SDK. See Work with coding agents from the terminal for picking up cards and reporting progress from Claude Code or Codex.
Start with overdue work, items due today, the next seven days, and recent progress in one focused view. Jump back into active boards and scan the week without opening each project separately.
Move cards through lists while keeping labels, assignees, due dates, checklist progress, and visual covers in view. Boards in a workspace share the same ordered lists, so stages such as Intake, In progress, Review, and Done remain consistent across related projects.
Press ? to open a shortcut sheet that reflects the current screen. Use two-key sequences to jump to Home, My Cards, Team Cards, Portfolio, or Settings; single keys to open Scratchpad, Up next, notifications, and board tools; and contextual card shortcuts for assignment, labels, due dates, lists, completion, watching, and copying links. Letter shortcuts automatically stand down while you type.
Build one ranked queue from cards assigned to you across every accessible board. Reorder it as priorities change, keep source boards and due dates visible, and see the same order on Home, My Cards, board cards, and Table.
Group and sort cards by list, assignee, due date, label, status, or custom field, then choose the columns that matter and edit any of them in place. Numeric custom fields support sum and average aggregates per group, with a second breakdown dimension for questions such as hours by client and work type.
Export the filtered result to Excel as a multi-sheet workbook containing card rows, spreadsheet-friendly summaries, and a readable report when aggregates are enabled.
Review mentions, assignments, comments, due-date changes, and other updates without losing the board context behind them. Group the feed by day, board, or person, narrow it to one board or one colleague, and search it by card, board, or list.
Then decide where each notification type reaches you: email, browser push, ntfy, Gotify, or a signed webhook of your own. Per-workspace rules pause or narrow a single noisy workspace without weakening your account defaults, and the in-app drawer always keeps the complete history regardless of what is switched off elsewhere.
Descriptions, custom fields, checklists, due dates, comments, attachments, and activity all live in one focused card view.
See the whole visible team or focus on one teammate without losing each card's board, list, fields, or permissions. Switch between Board, Team overview, Table, Calendar, Dependencies, and Work Done views to review ownership, workload, and execution order across projects.
One panel per teammate answers "what is each person working on, and what is next?" without opening each board in turn: their In progress cards longest-running first with time in progress, what they recently moved or created themselves, the head of their Up next queue, their other assigned cards by due date, and what they finished this week. Open, In progress, Overdue, and Done counts expand into the full list, in-progress work with no assignee gets its own panel, and folding a section folds it for everyone.
Pick one teammate to see just their panel with their Up next queue docked beside it. Reorder their queue, and queue what they should do next from the open cards they have not queued yet, listed soonest due first.
Build automations from a When trigger and ordered Do actions. Triggers can respond when cards enter or leave lists, a custom field changes to a selected value, a due date approaches or arrives, assignments and labels change, checklists or cards complete, or a card reaches the configured inactivity period. Kanera can then add labels, assign people, apply checklist templates, set due dates and custom fields, move cards, or mark work complete. Automations can belong to one standalone board or run across every board in a workspace.
Review a daily history of cards created, moved, and completed, plus finished checklist items. Use it on a board, My Cards, or Team Cards for standups, async updates, progress reviews, and client check-ins.
Review active, overdue, upcoming, unassigned, and completed work across organisations, workspaces, and boards from one reporting view.
Kanera's responsive, touch-friendly interface keeps boards, cards, Table, Calendar, My Cards, Team Cards, notifications, settings, and the rest of the product available on phones and tablets. Use it in the browser or install the PWA on iOS, Android, or desktop. Installed devices support push notifications, and recently opened boards remain available for browsing when the connection drops.
Explore the full product tour at kanera.app/features.
Kanera includes guided importers for Trello JSON, Kanera board JSON exports, and CSV files. Upload an export, map its columns or workspace data, review the result, then confirm a controlled one-time import. Kanera can preserve attachment links and copy supported uploaded files when Trello is connected for the import. Your original board or file stays unchanged, and later source changes are not synced automatically.
For Jira, ClickUp, Asana, monday.com, Notion, Linear, spreadsheets, or an internal system, export one representative project as CSV and use the CSV importer. Review its columns, users, dates, and multi-value fields before importing the full project.
Hosted Kanera is the simplest way to get started. New accounts include a 30-day Pro trial with no card required; teams can then stay on Free or upgrade to Pro. Pro adds unlimited boards and automations, board guests for clients and contractors, the REST API, webhooks, chat destinations, personal notification channels, and email support, typically within one business day. See current pricing.
Self-hosted Kanera has no plan gating and no per-seat charges. Everything above is included, including guests, the REST API, webhooks, chat destinations, and personal notification channels. You control the infrastructure, storage, maintenance, and backups.
Kanera is a pnpm monorepo built with Angular 22, Fastify 5, Socket.IO 4, PostgreSQL 18, Drizzle ORM, and Valkey.
For AI tools and automated research, see the LLM-readable documentation index.
apps/api/ Fastify API, worker, public API, and migrations
apps/web/ Angular web application
apps/admin-web/ Angular administration application
apps/mcp/ MCP server for AI clients
apps/cli/ kanera command-line interface for terminals and AI agents
packages/sdk/ @kanera/sdk TypeScript client for the public API
packages/shared/ Shared schema, DTOs, events, and workspace defaults
docker/ Local and production support files
You will need Node.js 24, pnpm 11 (usually through corepack enable), and Docker.
pnpm install
cp .env.example .env
pnpm dev:db
pnpm db:migrate
pnpm dev
Open http://localhost:4200.
The example environment uses PostgreSQL on localhost:5433 and Valkey on localhost:6379. Replace JWT_SECRET and MEDIA_SIGNING_SECRET with unique random values before exposing the application outside your machine. See .env.full.example for optional settings and defaults.
To load a realistic demo workspace:
pnpm dev:db:reset:seed
Seed account details are documented in dev-db-seed-content/README.md.
pnpm dev # API :3000 + worker :3003 + web :4200
pnpm dev:public-api # Public integration API on :3001
pnpm dev:mcp # MCP server on :3002
pnpm cli -- whoami # Run the kanera CLI from the workspace
pnpm dev:db # Start local PostgreSQL and Valkey
pnpm dev:db:down # Stop local database services
pnpm db:generate # Generate Drizzle migrations
pnpm db:migrate # Apply pending migrations
pnpm build # Build and type-check all packages
pnpm lint # Type-check and lint all packages
pnpm test # Run unit and integration test suites
pnpm test:api # Run API unit and route tests
pnpm test:cli # Run CLI tests
pnpm test:sdk # Run SDK tests
pnpm test:api:integration # Run API integration tests with isolated PostgreSQL
Flexible board model: workspaces share lists, labels, and custom fields across their boards, while standalone boards keep their configuration isolated.
Realtime collaboration: REST is the write path and Socket.IO fans out typed events to connected clients.
Durable events: board- and workspace-scoped events are recorded in an outbox for cross-process realtime delivery and webhooks.
Integrations: workspace API keys support external tools without exposing user credentials.
Delivery outside the app: chat destinations are webhook endpoints with a provider set, so Slack, Discord, Telegram, and Zulip reuse the webhook worker, retry policy, and delivery history. Personal notification channels run through the push queue, with HMAC-signed payloads for user-owned endpoints.
Agent-native MCP: OAuth-capable AI clients can connect with short-lived tokens, structured tool results, explicit safety annotations, and auditable access. An organisation admin can hand a connected agent a blank account and have it bootstrap workspaces and standalone boards from templates.
Typed API client: @kanera/sdk wraps the public API with card-key resolution, cursor iteration, idempotent retries, and webhook signature verification. See packages/sdk/README.md.
Agent-native CLI: kanera exposes the same tool layer as the MCP server to any agent that can run shell commands, with a machine-readable command catalog and exit codes that distinguish "not permitted" from "failed". Try it without a global install using npx -y @kanera/cli commands, or install it with npm install --global @kanera/cli.
Kanera also supports MCP event subscriptions for card creation, updates, moves, and new comments, delivered through verified HTTPS callbacks. See MCP events for filtering, subscription lifetimes, and deployment checks.
Hosted MCP clients connect to https://mcp.kanera.app/mcp. See the AI and MCP guide for supported clients and setup instructions. For the command line, see apps/cli/README.md.
Kanera is source available under the Elastic License 2.0. You may inspect, modify, and self-host it for your own use, but may not provide Kanera to third parties as a hosted or managed service.
The @kanera/sdk API client is the exception: it is MIT licensed so it can be embedded in any application without license-policy friction.
The Kanera name, logo, and brand assets are covered separately by TRADEMARKS.md.
© 2026 MCP Directory.
Manage Kanera workspaces, boards, cards, checklists, comments, notes, automations, and reports.
{ "mcpServers": { "app.kanera-mcp": { "url": "https://mcp.kanera.app/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Kanera is reached over HTTP.
Last checked 2026-11-13. Manage Kanera workspaces, boards, cards, checklists, comments, notes, automations, and reports.