MCP Integrations — Connect Your Agent to External Applications

MCP Integrations allow your raia agent to connect to external applications and services that support the Model Context Protocol (MCP). When you add an integration, your agent gains the ability to call tools provided by that application during conversations — such as looking up customer data in a CRM, creating tickets in a project management tool, or retrieving payment information from a billing platform.

Your agent is no longer limited to its own knowledge base. It can reach into the systems your team already uses and take real actions on behalf of users, all within a natural conversation.

1. 01

   The agent receives the user's message and evaluates whether any connected tools are relevant.

2. 02

   If a tool is needed, the agent calls the external MCP server using the configured URL and credentials.

3. 03

   The MCP server executes the tool (e.g. looks up a record, creates an item, runs a query) and returns the result.

4. 04

   The agent incorporates the result into its response and replies to the user naturally.

This happens automatically. The user does not need to know which tools are being called — they simply ask a question and receive an answer that draws on live data from your connected systems.

Prerequisites: an active raia agent with the MCP Skill enabled, the MCP server URL for the application you want to connect, and any required authentication credentials (API key, bearer token, or authorization header value).

Step 1 — Open the Integrations tab

Open your agent in the raia Dashboard, go to the agent's settings, select the MCP Skill page, and switch to the Integrations tab.

Step 2 — Create a new integration

Click New Integration. Fill in the form:

Step 3 — Fetch available tools

After filling in the URL and authentication details, click Get Available Tools. raia connects to the MCP server and retrieves the list of tools it offers. For example, a Stripe MCP server might expose:

• get_invoice — retrieve details about a specific invoice
• list_customers — search for customers by email or name
• create_refund — issue a refund for a charge

Step 4 — Select tools

Check the boxes next to the tools you want your agent to access. You do not need to enable all tools — only select those relevant to your agent's purpose. Limiting tools helps the agent make better decisions about when to use them.

Step 5 — Save the integration

Click Add Integration. The integration is now active and your agent can immediately begin using the selected tools in conversations.

All integrations for an agent are listed in the Integrations tab. Click any integration to open its detail view where you can update its name, description, URL, or credentials, change which tools are enabled, or toggle it between Active and Inactive. To temporarily disable an integration without deleting it, set its status to Inactive. To remove it permanently, click Delete from the detail view — this cannot be undone.

The Name and Description fields are critical because they directly influence when the AI model decides to use the integration. Write them as clear instructions.

The more specific your description, the more accurately the agent will know when to invoke the tools.

When you provide an Authorization token, raia stores it securely and includes it in every request to the MCP server. The token is never exposed to end-users or included in conversation responses.

The MCP server must be reachable from raia's cloud infrastructure over the public internet. Servers behind private networks, VPNs, or firewalls will not be accessible unless you expose them through a tunnel or proxy. raia also applies these safety filters:

• Localhost URLs are blocked — you cannot connect to 127.0.0.1 or localhost.
• Self-referencing URLs are blocked — you cannot point an integration back at raia's own API domain.

The MCP ecosystem is growing rapidly. Applications like these already ship MCP servers you can connect to your raia agent — check each application's documentation for their specific MCP server URL and authentication requirements.

A typical Stripe integration configuration looks like this:

{
  "name": "Stripe Payments",
  "description": "Use to look up invoices, customers, and subscriptions, and to process refunds when users ask about billing.",
  "url": "https://mcp.stripe.com/v1/mcp",
  "transport": "streamableHttp",
  "authorization": "Bearer sk_live_************",
  "tools": ["get_invoice", "list_customers", "create_refund"]
}