Command · Agent Bridges (MCP)
MCP Server
Pull resources from any remote Model Context Protocol server into a project folder.
How it works
The generic MCP Server connector points Command at any remote Model Context Protocol server. Resources can be pulled into a project folder, or the server can be exposed to an agent as live tools.
Before you start
- A reachable MCP server URL (streamable HTTP or SSE)
- Whatever credential that server requires
What you need to make the connection
| Field | Where to get it |
|---|---|
| Server URL | The remote MCP endpoint, e.g. https://example.com/mcp. |
| Authentication | Either an OAuth flow the server advertises, or a bearer token / API key header you paste in. |
Credentials are stored encrypted in raia Command and are never shown again after saving. Rotate them at the provider if they are exposed.
Setup steps
- 01
In raia Command, open Settings → Connectors, find the connector, and click Connect.
- 02
Enter the MCP server URL.
- 03
Complete OAuth, or paste the bearer token / header the server expects.
- 04
Command lists the server's tools and resources — select what to import or expose.
- 05
Choose the destination project folder, run the first import, then set a sync schedule. Every run is recorded in Sync History.
Good to know
- Servers must implement the streamable HTTP transport and accept both application/json and text/event-stream.