Rapidi MCP Server: Bring Your AI Tool Into Your Integration Platform
Last week we looked at Albert, the AI assistant that lives inside MyRapidi. This week we walked through the next layer: the Rapidi MCP Server. It is the bridge that lets external AI tools like Claude reach the same context Albert has, so you can troubleshoot, configure, and run your integrations from whichever AI tool you already use.
Below is a walkthrough of the Model Context Protocol, how to connect Claude to Rapidi MCP in under a minute, and what you can actually do once it is wired up.
A Quick Summary
- MCP (Model Context Protocol) is the emerging standard for connecting AI tools to external systems. Think of it as a universal plug.
- The Rapidi MCP Server exposes MyRapidi to MCP-compatible AI tools. Today the walkthrough focuses on Claude.
- Setup is a paste-the-URL flow at claude.ai/customize/connectors. No installation, no API keys to copy.
- The MCP exposes six skill areas: connections, transfers, schedules, error troubleshooting, error report emails, and AI memory and skill management.
- You stay in control. The AI can only do what the MCP server exposes, and access is granted explicitly per tool.
Watch the Full Session
What Is MCP?
MCP, short for Model Context Protocol, is a standardized protocol for connecting AI models to tools, APIs, and data sources. The point of standardizing it is to remove the custom glue code that used to be needed for every AI, plus every system. One protocol, many tools.
Three properties matter in practice:
- Standardized. One interface that any MCP-compatible AI tool can use. No bespoke integration per AI model.
- Bidirectional. The AI can read context from your systems and take actions inside them. That is what makes "run that transfer now" or "check today's logs" possible.
- Secure and controlled. You grant access explicitly. The AI only does what the MCP server exposes, nothing more.
How to Connect Claude to Rapidi MCP
The setup is short. The Rapidi MCP URL is https://myrapidi.com/mcp.
- Make sure you are logged into MyRapidi in the same browser first. The MCP connector relies on your existing session, so there is no separate login prompt.
- Go to claude.ai/customize/connectors.
- Click "Add connector".
- Paste the Rapidi MCP URL.
- Click Add. The Rapidi tools are now available inside your Claude chat.
From there, you can pick which tools Claude is allowed to use. The connector splits them into read-only tools and write-or-delete tools, so you can keep things conservative while you get used to it.
What You Can Do With Rapidi MCP
The MCP server exposes the same skill areas that Albert has inside MyRapidi, so external AI tools can reach the work integration teams actually do every day:
- Error Troubleshooter. Investigate and resolve transfer errors, schedule failures, and sync issues.
- Transfer Configuration. Create, update, run, and manage data transfers, field mappings, and filters.
- Schedule Management. View, start, stop, and configure integration schedules.
- Connection Skills. For example, set up and troubleshoot Business Central, Dynamics 365 F&O, HubSpot, and Salesforce connections.
- Data Errors Report Email. Auto-generate and send formatted error digest emails.
- AI Memory and Skill Management. Store preferences, manage custom skills, and extend capabilities over time.
Three Prompts That Show The Value
The session walked through three prompts that map to typical workdays:
- Transfers: "Add a filter to only sync Contacts with status = Active." Claude reads the transfer config, adds the filter, and confirms the change.
- Connections: "Set up a new Business Central connection for company A." Claude walks through the required fields, creates the BC connection, and tests it.
- Errors: "Why did my schedules fail today?" Claude fetches recent logs, reads the error codes, explains the root cause, and suggests a fix.
The pattern is the same in each case: you describe the outcome you want in natural language, the AI uses the MCP tools to look at the real configuration, and it either does the work or explains what is in the way.
Where MCP Fits Next to Albert
Albert is the AI assistant inside MyRapidi. The Rapidi MCP Server is the same capability surface, but reachable from outside. If your team already lives in Claude, Copilot, or another MCP-compatible tool, MCP lets you stay there and still get to your integrations. If you prefer working inside MyRapidi, Albert is right there. Same context, different entry points.
Getting Started Today
Three concrete things you can do this week:
- Connect Rapidi MCP to your AI tool of choice. Start with Claude and the paste-the-URL flow above. It takes under a minute.
- Try a read-only prompt first. Something like "list the schedules that ran in the last 24 hours" or "show me failed transfers from yesterday." See the answer, compare it to MyRapidi, and build confidence.
- Move on to actions. Once read-only feels right, try a small change: a new filter on a non-critical transfer, or a test connection. Verify in MyRapidi that the result matches what you asked for. That verification habit is what keeps AI safe in production.
Frequently Asked Questions
Do I need an API key to use Rapidi MCP?
No. The connector relies on your existing MyRapidi browser session. Log in to MyRapidi in the same browser, then add the MCP URL at claude.ai/customize/connectors. There is no separate login prompt and no key to paste.
Which AI tools work with Rapidi MCP today?
The walkthrough focuses on Claude, since Claude.ai has a clean connector flow. MCP is an open protocol, so any MCP-compatible tool that lets you add a remote server can connect to https://myrapidi.com/mcp. The skill surface is the same regardless of the client.
What can the AI do, and what can it not do?
The AI can only do what the MCP server exposes. Today, those are the six skill areas covered above: connections, transfers, schedules, error troubleshooting, error report emails, and AI memory and skill management. Anything outside that surface is not reachable through MCP, even if you ask for it.
Is this the same thing as Albert?
The capability surface is similar, but the entry point is different. Albert is the AI assistant inside MyRapidi, embedded in the platform UI. The Rapidi MCP Server is the protocol that lets external AI tools, like Claude, reach the same kind of context and actions from outside MyRapidi. You can use either, or both.
Where can I learn more after this session?
The MyRapidi wiki has the technical references for connections, transfers, schedules, logs, and the related groups, RTI, tags, and services sections. See myrapidi.com/wiki. Albert is available inside MyRapidi for guided help, and you can keep up with new sessions on the Open Office Hours page.
More From Open Office Hours
Catch up on previous sessions on the Open Office Hours page, and stay tuned for our 2 Seasons.
