MCP Integration

Shellarium provides a unified MCP layer shared by all supported agent providers. You configure MCP once, then reuse the same servers and credentials everywhere.

Why This Matters

One-time setup — add MCP servers once in Shellarium
Provider-agnostic — the same MCP configuration works with Claude Code and ACP-compatible agents
Unified authorization — complete OAuth once and reuse credentials across providers and sessions
Consistent behavior — same auth checks, status signals, and policy handling in chat and automations

Unified Server Configuration

MCP server definitions are managed centrally on the Integrations page. Each MCP server appears as its own entry with a dedicated detail page showing connection status, description, and controls. You can add servers manually or import them from your Claude configuration.

Select those servers per workspace or per automation without duplicating setup for each provider. Shellarium applies one internal configuration model and bridges it to the active provider.

Unified OAuth Authorization

For protected MCP servers, Shellarium supports in-app OAuth authorization flow:

Start authorization directly from chat or from the integration detail page
Persist credentials in Shellarium-managed storage
Reflect successful auth state immediately in the chat guard
Auto-refresh expired access tokens before agent start when refresh_token is available
View token expiry time and auto-refresh status on the MCP server detail page

Unattended Runs (Automations)

Automations can run without manual supervision. For MCP authorization gaps, you can choose policy:

ignore — continue run without the unauthorized MCP server
fail — stop the run when selected MCP access is unavailable

This keeps background behavior predictable and explicit.

Health & Safety Signals

Shellarium continuously validates MCP availability and authorization state:

MCP tab warning indicator when selected server is unavailable or unauthorized
Pre-send auth prompts inline in chat stream
Persistent “send anyway” behavior per chat with automatic re-check when auth state changes