Developers

Built to be scripted.

Everything in Radial is reachable from the terminal — by you, by CI, or by your agents. The web app is just one client.

$ brew install radial && radial auth

The CLI

Nine commands cover the whole product. Every one of them takes--jsonfor scripting.

radial create <title>Create an issue. Flags: -p priority, -l label, -a assignee, -t team

radial listList issues. Filter with --assignee, --status, --label, --team

radial show RAD-219Full issue detail, comments included, as text or --json

radial close RAD-219Close with an optional -m message; links PRs automatically

radial triageStep through unassigned issues with single-key actions

radial search <query>Same 4ms index the app uses, in your terminal

radial importBring everything from Linear or Jira: --from linear | jira

radial exportFull workspace export as JSON or CSV. Always available

radial mcpRun the MCP server over stdio for any MCP-capable agent

The MCP server

One line in your agent's config — the URL. Your client opens a browser, you approve, done. No keys to paste. Works with Claude Code, Codex, and anything else that speaks MCP. Prefer to run it locally? radial mcp serves the same tools over stdio.

.mcp.json

{
  "mcpServers": {
    "radial": {
      "url": "https://mcp.radial.build"
    }
  }
}

Exposed tools

create_issueupdate_issuesearch_issueslist_issuescommentclose_issuelist_projectstriage_queue

Every connection is scoped: read-only, triage-only, or full access. Authorize with OAuth, revoke any connection in one click without touching the others. Agents are free and don't count as seats.

The API

Plain REST. JSON in, JSON out. No GraphQL schema to spelunk, no SDK required, no deprecation roulette.

curl

$ curl -H "Authorization: Bearer $RADIAL_KEY" https://api.radial.build/v1/issues?status=open

{ "issues": [ { "id": "RAD-241", "title": "Search results flash empty state", ... } ] }

Get an API key