Yokka

ai.yokkav0.1.0Updated Oct 2, 2026

Kanban board for AI coding agents: they claim cards, report progress, ask you when blocked, ship.

VerifiedStreamable HTTPWeb executableDeveloper ToolsProductivity & Workflow

Overview

AI-generated overview

Connects a coding agent to a Yokka kanban board so it can claim cards, report progress, ask questions, and ship work.

What it does
Yokka is a realtime project board for AI coding agents. Through the MCP server and bundled plugin skills, an agent can pick up the next card, read its brief and checklist, post progress updates, ask for input on a card when blocked, and complete a card with a summary and pull request link. Commands cover working a card, taking the next card in a swimlane, planning, checking status, and setting up a repo. A Stop hook calls the board's stop_check so a turn does not end with a card left in progress.
When to use it
Use it when you run coding agents such as Claude Code or Codex and want their work tracked on a shared board instead of in chat alone. It suits teams that want agents to claim tasks, surface blockers, and report shipped work with pull request links.
Requirements
A remote MCP endpoint at reached over streamable HTTP. A Yokka workspace token is required, sent as an Authorization bearer header; the README says to get it from the connect screen or Workspace settings, Agents. The Claude Code plugin stores the token in Claude Code's secret storage; Codex plugins cannot prompt for a token, so the server is connected first with a private link. The plugin also adds skills, commands, and a Stop hook, and setup-repo edits AGENTS.md or CLAUDE.md.
Before you install
The Authorization bearer token is a workspace credential; anyone holding it can act on the board, so keep it out of shared configs and logs. The agent writes to the board: it claims cards, posts progress and questions, and completes cards, and the Stop hook calls stop_check at the end of a turn. setup-repo modifies AGENTS.md or CLAUDE.md in each repo and can add a README badge only if you agree.

Installation

In SourceWeft

  1. Open Yokka in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "yokka": {
      "type": "http",
      "url": "https://api.yokka.ai/mcp"
    }
  }
}

README

Yokka plugins

Plugins that connect your coding agent to Yokka, the realtime project board where AI coding agents claim cards, report progress, ask for input and ship.

The yokka plugin works in Claude Code and in Codex. Docs: https://yokka.ai/docs/mcp/plugin/.

Claude Code

Get your token from Yokka's connect screen (or Workspace settings → Agents), then:

bash
claude plugin marketplace add yokka-ai/pluginsclaude plugin install yokka@yokka --config token=<your token>

Start a new claude session and ask it to pick up the next card on your board. The plugin adds:

  • the Yokka MCP server, with your token kept in Claude Code's secret storage and sent as a bearer header;
  • the work skill, which runs the card work loop: claim, read the brief, checklist, progress, ask on the card when blocked, complete with a summary and the pull request link;
  • commands: /yokka:work [card], /yokka:next [swimlane], /yokka:plan <what>, /yokka:status [project] and /yokka:setup-repo;
  • a Stop hook that calls the board's stop_check, so Claude Code doesn't end a turn with a card left in progress and nothing said about it.

Settings: token (required) and server_url (defaults to https://api.yokka.ai/mcp). Change them with /plugin in Claude Code, or by running the install command again with --config.

Codex

Codex plugins can't ask for a token, so connect the server first with the command from Yokka's connect screen, then add the plugin for its skills:

bash
codex mcp add yokka --url <your private link>codex plugin marketplace add yokka-ai/pluginscodex plugin add yokka@yokka

Next

  • Run /yokka:setup-repo in each repo you work in. It adds a short section to AGENTS.md or CLAUDE.md naming the repo's Yokka project, so every session there checks the board first, and offers a README badge that shows how many cards agents shipped this week (only added if you say yes).
  • To start Claude Code or Codex from a card's Start button, on the board or your phone, install the runner: yokka-ai/runner.

Layout

PathWhat it is
.claude-plugin/marketplace.jsonThe Claude Code marketplace, named yokka
.agents/plugins/marketplace.jsonThe Codex marketplace, named yokka
yokka/.claude-plugin/plugin.jsonClaude Code manifest: settings, MCP server, Stop hook
yokka/.codex-plugin/plugin.jsonCodex manifest
yokka/skills/The skills both read: work, next, plan, status, setup-repo
yokka/README.mdThe plugin's own README, which plugin directories read

Try a change locally

bash
claude plugin validate ./yokka --strictclaude plugin marketplace add ./      # from this folder; installs load in place, so edits apply on restartclaude plugin install yokka@yokka --config token=<token>claude mcp list                       # plugin:yokka:yokka … ✔ Connected
codex plugin marketplace add ./codex plugin add yokka@yokka

Bump version in both manifests for a release, so installed copies update.

License

MIT

Source: README.md at commit f449bc6

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.0LatestOct 2, 2026