How it works
The Model Context Protocol (MCP) skill bridges your raia agent and external systems in both directions. In Server Mode (RAIA MCP tab), external clients like Claude Desktop, Cursor, or Windsurf can query your agent's knowledge and capabilities through a single standardized tool. In Client Mode (Integrations tab), your agent connects to other MCP servers, discovers their tools automatically, and calls them at runtime to fetch live data or perform actions — no custom Functions required.
Key features
Server Mode (RAIA MCP)
Exposes a get-any-info-about-[Agent] tool so external MCP clients can query your agent's full context (instructions, vector store, linked packs).
Client Mode (Integrations)
Connect the agent to any external MCP server by URL. Tools are discovered automatically and injected into the agent's toolkit.
Flexible Authentication
Server Mode supports header-based Bearer tokens (with regeneratable secret keys) and full OAuth flows for external clients.
Transport Options
Client integrations support both Streamable HTTP (standard) and SSE (Server-Sent Events) for streaming servers.
Granular Tool Selection
When adding an integration, pick exactly which discovered tools the agent is allowed to use — leave destructive tools off by default.
AI-Optimized Descriptions
Use the Optimize with AI button to auto-generate Server and Tool Descriptions from your agent's core instructions so external clients know when to call you.
Runtime Tool Routing
Selected external tools are passed to the LLM as type: 'mcp' alongside custom functions; raia routes execution to the external server and feeds the response back into context.
Archive & Manage
Temporarily archive an integration to disable its tools without losing configuration, or delete it entirely.
How to configure it
- 01
Open the MCP skill and choose the RAIA MCP tab (Server Mode) or the Integrations tab (Client Mode).
- 02
Server Mode: fill in a Server Description and Tool Description (or click Optimize with AI), then share the MCP Endpoint URL + Secret Key, or the OAuth Registration URL, with the external client.
- 03
Client Mode: click Add Integration, give it a clear Name (used as the server_label sent to the LLM) and Description, and enter the external MCP server URL.
- 04
Select the Transport (Streamable HTTP or SSE) and, if required, add a Bearer Authorization token and any custom headers like X-API-Key.
- 05
Click Get Available Tools, tick the specific tools the agent is allowed to use, and save. The agent can call them on the next message.
Frequently asked questions
What is the difference between Server Mode and Client Mode?
Server Mode makes your raia agent callable by external MCP clients (Claude Desktop, Cursor, Windsurf, etc.). Client Mode lets your raia agent call tools hosted on someone else's MCP server. Both can be enabled at the same time.
How do external clients authenticate to my agent in Server Mode?
Either header-based auth (the client sends Authorization: Bearer [Secret Key], which you can regenerate at any time if compromised) or a standard OAuth flow using the OAuth Registration URL.
When should I use MCP instead of Functions?
Use Functions for a single REST endpoint. Use MCP for complex systems with many actions (GitHub, Jira, Salesforce), for secure internal data sources, or when the provider already ships an MCP server so you skip writing custom API wrappers.
Can I connect to a local MCP server on localhost?
No. raia CX runs in the cloud, so external MCP servers you integrate with must be publicly reachable on the internet. localhost and 127.0.0.1 will not connect.
How do I keep the agent safe when connecting external tools?
Only tick the specific tools you trust when adding an integration. Avoid granting destructive tools (like drop_database) unless strictly necessary, and prefer read-only tools whenever possible.