orca-mcp
Officialby BuildContext
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP only. Listen port (default 8787). | |
| HINDSIGHT_URL | No | HTTP only. Optional Hindsight proxy target (default http://127.0.0.1:8888). | |
| ORCA_BRIDGE_FROM | No | Pin a live terminal as orchestration sender (alternative to ORCA_BRIDGE_SENDER_TERMINAL). | |
| ORCA_CLI_COMMAND | No | Override the 'orca' binary (Linux often 'orca-ide'). | |
| ORCA_BRIDGE_DEBUG | No | Set to '0' to mute access log (stderr in --stdio, stdout in HTTP). | |
| ORCA_BRIDGE_TOKEN | Yes | Required (both transports). Master token (≥16 chars) — stdio env auth; HTTP path-token + OAuth 'password'. | |
| ORCA_BRIDGE_TOOLSETS | No | Comma list of enabled tiers: status, dispatch, admin (default = all three). | |
| ORCA_BRIDGE_AUDIT_DIR | No | Directory for the append-only audit log (default ~/.orca-bridge). | |
| ORCA_BRIDGE_CLI_ADMIN | No | Set to '1' to union admin into enabled toolsets (compat with CLI allowlist admin; ignored under --read-only). | |
| ORCA_BRIDGE_DEFAULT_REPO | No | Default --repo (path:… / name:…). | |
| ORCA_BRIDGE_SENDER_TITLE | No | Title for auto-created coordinator tabs. | |
| ORCA_BRIDGE_CLI_HARDENING | No | Set to '1' to enforce deny-by-default allowlist on action=cli. | |
| ORCA_BRIDGE_DEFAULT_AGENT | No | Default agent for dispatch (default 'omp'). | |
| ORCA_BRIDGE_PUBLIC_ORIGIN | No | HTTP only. Public origin for OAuth URLs (Funnel / proxy host). | |
| ORCA_BRIDGE_SENDER_SHARED | No | Set to '1' to force all clients onto the env pin (disables multi-coordinator isolation). | |
| ORCA_BRIDGE_REDIRECT_ALLOW | No | HTTP only. Comma-separated allowed redirect_uri prefixes. | |
| ORCA_BRIDGE_SENDER_TERMINAL | No | Pin a live terminal as orchestration sender (alternative to ORCA_BRIDGE_FROM). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BuildContext/orca-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server