Studio Module
Give your AI coding tools direct access to your Planner work
Studio connects the AI coding tools your team already uses to your workspace's Planner data. Instead of copying a ticket into a chat window, the tool reads the issue itself — description, comments and all — and can update it when the work is done.
How a Connection Works
Connecting a tool issues it a scoped Planner API token and shows you exactly what to paste into the tool. Planner never asks for or stores your credentials for the tool — the tool calls Planner, not the other way round. The same token works two ways:
- ✓ As an MCP server — any tool that speaks MCP over HTTP gets Planner's work as tools it can call directly: list projects and issues, read an issue and its comments, get an implementation brief, create and update issues, and comment
- ✓ As the REST API — for anything that can't speak MCP, the same token calls the plain HTTP API
Capabilities
- ✓ Guided setup for 13 popular AI coding tools
- ✓ Read-only or read-and-write access, chosen per connection
- ✓ See when each tool last called Planner
- ✓ Reopen setup details at any time, without reconnecting
- ✓ Disconnect instantly — revoking the token cuts the tool off
- ✓ A tool never has more access than the person who connected it
Typical Use Case
Step-by-Step:
- Open Studio from the workspace sidebar
- Choose your tool, e.g. Claude Code, and click Connect
- Pick read-only or read-and-write access
- Copy the MCP URL and token (or the environment variables) into the tool
- Ask the tool to pick up the next issue in the current cycle
- It reads the ticket and its comments, makes the change, and updates the issue
Supported Tools
Command line
Claude Code, Aider
Editors
Cursor, Windsurf, Zed
Editor extensions
GitHub Copilot, Cline, Continue
Hosted builders
Devin, Replit Agent, v0, Bolt, Lovable
Any other tool that supports MCP over HTTP, or can make HTTP requests, works too.
Plans: Studio connections use the public API, which is included in Business and Enterprise. Want Planner to write the code itself instead? See Automation.