Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
ChatGPTClaudeClaudeClaude CodeClaude CodeCodexCodexConductorConductorCursorCursorGitHubGitHubGitLabGitLabBitbucketBitbucketGoogle CalendarGoogle CalendarGoogle MeetGoogle MeetJetBrainsJetBrains IDEsJiraJiraLinearLinearSlackCustom appn8nn8nSmitherySmitheryWindsurfWindsurf
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium


Claude Code

Put the brief in One Horizon first. The initiative, bug, or todo should give Claude Code the goal, context, links, comments, and acceptance notes before it starts.

After that, choose how you want to work. Stay in Claude Code with the MCP connector, or let a local Claude Code agent run the task on your machine from Desktop, the CLI, or Workflows. The work item carries the prompt detail.

Local agent setup is separate from the MCP connector. It uses your authenticated claude CLI and does not require you to add the One Horizon MCP server manually.

Claude Code MCP

Choose how to use Claude Code

PathBest forWhat happens
MCP connectorWorking inside Claude Code chat.Claude Code can find assigned work, read work details, and capture completed work while you stay in the terminal.
Local Claude Code agentLetting Claude Code work from a One Horizon task.One Horizon starts Claude Code on your machine, sends the work item as the brief, and records progress on the run.
Open in Claude CodeReviewing a stopped local run.Completed or failed local agent runs can reopen the recorded Claude Code session from the run menu.

Start with the work item

Claude Code works best when the initiative, bug, or todo already explains the change. Add the outcome, important files or links, constraints, and what counts as done. That work item becomes the prompt source for both MCP chat and local agent runs.

For larger implementation work, keep the brief close to spec-driven development: specific enough for Claude Code to act, short enough for a person to review.

Connect Claude Code through MCP

MCP is the interactive path. Configure it when you want to ask Claude Code about One Horizon work while you are already coding.

The Claude Code integration uses the One Horizon remote MCP server over HTTP with OAuth.

Import from Claude Desktop

If you already configured the MCP server in Claude Desktop, import it.

claude mcp add-from-claude-desktop --scope user
Copied!

Configure manually

claude mcp add --transport http onehorizon https://mcp.onehorizon.ai/mcp
Copied!

Manage servers

List, inspect, remove, or check status.

claude mcp listclaude mcp get onehorizonclaude mcp remove onehorizon/mcp
Copied!

Authenticate

When you run /mcp in Claude Code, a browser window opens so you can sign in and authorize the connection. After granting access, return to Claude Code.

/mcp
Copied!

Use Clear authentication in the /mcp menu to revoke.

Project level

Share a team configuration by committing a .mcp.json at the repository root. Our MCP server uses OAuth so there is no need for environment variables.

.mcp.json
{  "mcpServers": {    "onehorizon": {      "type": "http",      "url": "https://mcp.onehorizon.ai/mcp"    }  }}
Copied!

Run a Claude Code local agent

A local Claude Code agent is for tasks you want Claude Code to work through without a live chat. After setup, open an initiative, bug, or todo in One Horizon, choose Send to, and pick your Claude Code agent. The run stays tied to that work item.

When a local Claude Code agent run reaches complete or error status, the session stores a Claude session ID. Open in Claude Code appears in the run menu and resumes that session in the task workspace folder. The action is available only when the session status is complete or error so it does not start a separate interactive session while work is still active.

Setup, agent commands, and the execution model are described in Local Agents and Agent Sessions.

Local agents are experimental. Use them for small, well-bounded tasks and review code, tests, and pull requests before you merge.

Ask Claude Code through MCP

Short prompts are enough when the work item already has the detail:

Try these prompts:

"show my assigned issues and todos for today"

Claude Code pulls your in-flight issues from tools like Linear or Jira and summarizes them inline.

"use my assigned work details for the gateway API"

Claude Code brings those details into context so the AI names things correctly and scopes changes.

"capture this as completed work"

Claude Code summarizes what it generated and adds a completed task.

Security and permissions

The connector acts on your behalf. Data access follows your roles, workspace, team membership, and scopes.

Troubleshooting


PreviousClaudeNextCodex
Cursor

Cursor

Let Cursor use One Horizon work as the brief through MCP or a local agent.

Claude

Claude

Connect Claude to One Horizon to report, summarize, and plan work.

Codex

Codex

Send One Horizon work to Codex, or let a local Codex agent run it from your machine.

Local Agents

Create and run a local agent from Desktop or the CLI.

  • Choose how to use Claude Code
  • Start with the work item
  • Connect Claude Code through MCP
  • Run a Claude Code local agent
  • Ask Claude Code through MCP
  • Security and permissions
  • Troubleshooting
  • Back to top