MCP server

What this is

The Model Context Protocol is an open standard for connecting AI assistants to the systems where work actually lives. Instead of pasting project updates into a chat window, you point the assistant at Orangescrum once and it can read and act for itself.

Concretely, that means the assistant can:

• Answer questions from live data: what is overdue, who is loaded, what shipped last sprint.
• Create and update projects, tasks, subtasks, epics, features, and stories.
• Run sprints: create one, start it, assign work to it, close it.
• Log time, and read time logs back for reporting.
• Comment on tasks, and manage their dependencies, links, and labels.
• Drive Test Lab: test cases, suites, plans, runs, scenarios, baselines, and defects.
• Manage versions and releases, including readiness, approvals, and release notes.
• Run Scaled Agile: release trains, program increments, the program board, PI objectives, and WSJF.
• Manage checklists on any work item.

Connect a client

The server speaks HTTP and authenticates with OAuth. Your client opens a browser window, you sign in to Orangescrum, and the connection is bound to your account. No API key to paste, no secret in a config file. The server URL is https://mcp.orangescrum.com/mcp/partner.

// claude_desktop_config.json
// macOS  ~/Library/Application Support/Claude/claude_desktop_config.json
// Windows  %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "orangescrum": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.orangescrum.com/mcp/partner"
      ]
    }
  }
}

Once connected, ask the client to list its tools. You should see the Orangescrum tools listed below. If nothing appears, the sign in probably did not complete: disconnect and add the server again.

Try it

Nothing special is needed to invoke a tool. Ask in plain language and the assistant picks the right one.

What is overdue across all my projects, and who owns each one?

Which tasks did I close yesterday? Draft my standup.

Show me the open defects on the Website Redesign project, worst first.

Authentication

The primary endpoint is /mcp/partner, protected by OAuth bearer tokens. Clients discover how to authenticate automatically from these documents, so in most cases you only ever paste the server URL:

• /.well-known/oauth-authorization-server
• /.well-known/oauth-protected-resource
• /oauth/register

Dynamic client registration is supported, which is why clients you have never configured before can connect with only a URL.

Requests are rate limited to 120 per minute and 5,000 per day, counted per IP address. Going over returns a JSON-RPC error; back off and retry.

A legacy API key endpoint exists at /mcp/partner-legacy for integrations built before OAuth. It is disabled by default and kept only for migration. Use the OAuth endpoint for anything new.

Tool reference

342 tools in 49 groups. You do not call these yourself, the assistant does, but knowing what exists tells you what you can reasonably ask for.