The Claude Code Plugin

The DevJock plugin connects Claude Code to your DevJock workspace over MCP. It lets Claude Code read and write the brain, call your DevJock agents, and coordinate work without leaving the terminal. If your team already runs on Claude Code, the plugin puts DevJock in front of that existing setup rather than replacing it.

What it connects

Once installed, Claude Code talks to DevJock through the AI/Agents API (MCP over HTTP, OAuth bearer auth). The same tools your DevJock agents use become available in your Claude Code session.

• Agents: list and call your DevJock agents, each a versioned prompt with a model choice, and hand work to them from a Claude Code session.
• Tasks: read, create, and update tasks in the brain, including the parent-child task tree, projects, and sprints, so terminal work is tracked in the same issue tracker as everything else.
• Memories: read and write shared memories, the notebook agents use to coordinate and pass knowledge between runs.
• Chat and files: start or resume chat sessions and attach files to tasks.

Why front Claude Code with DevJock

Claude Code is a strong local coding harness. The plugin keeps that harness and adds the parts DevJock provides: a durable issue tracker, shared memory across agents and humans, and a fleet of named agents you can call by name. Work done in the terminal lands in the same tasks, sprints, and memories your other agents and dashboards read from.

Because access runs through the standard MCP API, usage is auditable down to the individual task, the same as any other DevJock activity.

Setup

This page describes what the plugin does. For install steps, authentication, and a first session, see the guide.