Skip to content

Support remote MCP servers #335

Description

@cometkim

Problem Statement

OCR landed MCP support and describe in the documentation as

When to use it

Reach for an MCP server when the reviewer would benefit from context that lives outside the diff:

  • Issue / ticket lookup — let the agent fetch the linked Jira / GitHub issue to check whether the change matches the stated requirement.

However, most issue trackers, including GitHub, provide this as a remote MCP and do not use local commands.

Proposed Solution

It would be nice if OCR directly supported a built-in auth flow with "type": "remote" MCP.

It would be like:

# Some remote MCPs are public and don't require auth
ocr config set mcp_servers.cloudflare_docs.type remote
ocr config set mcp_servers.cloudflare_docs.url "https://docs.mcp.cloudflare.com/mcp"

ocr config set mcp_servers.github.type remote
ocr config set mcp_servers.github.url "https://api.githubcopilot.com/mcp/"

# Optionally, when using PAT
ocr config set mcp_servers.github.headers "Authorization=$GITHUB_PAT"

# Or it returns 401, OCR should trigger auth flow or at least prompt

Alternatives Considered

Bridge commands like mcp-remote can be used, this increases the user's unnecessary configuration surface and attack vectors.

Affected Area

Configuration

Additional Context

No response

Metadata

Metadata

Labels

enhancementNew feature or request

Fields

No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions