Connect Claude Code

Install the plugin

The fastest path. The plugin connects the server and installs Orcha's usage guides as skills in one step, with no token to manage:

/plugin marketplace add westonhancock/orcha-mcp
/plugin install orcha@orcha

Claude Code walks you through OAuth on first use, where you pick the workspace and choose which of read, write, and delete the connection gets. The skills arrive as /orcha:retrieval, /orcha:citations, /orcha:authoring, and /orcha:troubleshooting, and Claude loads whichever one a task calls for.

The rest of this page covers connecting the server by hand, which you want if you need a bearer token, a pinned project configuration, or no plugin.

Prerequisites

An API token from the Tokens page with the permissions you want Claude Code to have. read is enough for retrieval; add write if the agent should create or update context. See Tokens and scoping.

Add the server

claude mcp add --transport http orcha https://app.tryorcha.com/mcp \
  --header "Authorization: Bearer orca_your_token_here"

Add --scope project to share the configuration with your team via .mcp.json, or --scope user to use it across all your projects. If you commit a project-scoped config, put the token in an environment variable instead of the file:

{
  "mcpServers": {
    "orcha": {
      "type": "http",
      "url": "https://app.tryorcha.com/mcp",
      "headers": {
        "Authorization": "Bearer ${ORCHA_TOKEN}"
      }
    }
  }
}

Verify

Run /mcp inside Claude Code to confirm the orcha server is connected and its tools are listed.

Usage

Claude Code is told to start with get_workspace_overview when it is unfamiliar with a workspace, then use search_context for questions and memories for curated workflows. Try:

• "Search my Orcha workspace for our deployment requirements"
• "Check which Orcha memories apply to this task and use the best match"
• "Create a file in Orcha summarizing the decisions we just made"