Skip to main content
GET
Retrieve an MCP server

Authorizations

Authorization
string
header
required

Your Reason API key from Settings > API. New keys use reason_; legacy ara_ keys remain accepted. Keys are capability-scoped: run, mcp:read, mcp:write, secrets:read, secrets:write, sessions:read, sessions:debug, knowledge:read, memory:read, memory:write, skills:read, skills:write, repos:read, repos:write, reviews:read, reviews:write, deployment:read, analytics:read, org:read, org:write, attachments:read, attachments:write, guardrails:read, guardrails:write, automations:read, automations:write, agent_auth:read. mcp:write manages MCP server configuration only; it does not authorize remote MCP-tool execution. sessions:debug is privileged: it expands diagnostic session events only for organization owners/admins.

Path Parameters

orgId
string
required

Organization id or slug. Resolve it with GET /v3/self.

id
string
required

The MCP server id.

Response

The MCP server.

An org-level MCP server. Secret values are write-only and are never returned; only secret_names lists which secrets are set.

id
string
slug
string
name
string
icon
string | null
description
string
source
string
transport
enum<string>
Available options:
http,
stdio,
sse
url
string | null
command
string | null
args
string[]
env
object
headers
object
auth_type
enum<string>
Available options:
none,
oauth,
bearer
secret_names
string[]

The names of the secrets configured for this server. Secret values are write-only and are never returned.

access
string
enabled
boolean
created_at
string<date-time>
updated_at
string<date-time>