Before you start to use our MCP, please review the following items:
Ensure you have completed the iPaaS.com platform training before using this to best understand what is going on. If you need to gain access to it reach out to partnerships@ipaas.com.
With great power comes great responsibility - the MCP can do things like trigger a sync for your entire catalog and modify (or remove) data from your account. Ensure you understand what you want it to do before you work with it. iPaaS.com is not responsible for restoring any data or configuration changes made using the MCP.
Measure twice, cut once: When working with this, planning ahead of time (or asking the MCP to plan for you) will greatly benefit your work.
Remember that this is in beta so some features may be added, removed or altered as we continue our development. The latest change log notes can be found here.
If you have any issues or need to report a bug please reach out to us at mcp@ipaas.com.
What is the iPaaS.com MCP server?
The Model Context Protocol (MCP) is an open standard that lets an AI assistant, such as Claude, use external tools. The iPaaS.com MCP server gives your assistant more than 240 tools for working with your iPaaS.com company. Instead of clicking through the portal, you describe what you want in plain language. The assistant chooses the right tools, shows you what it found, and, for anything that changes data, asks you to confirm before it acts.
What you can ask it to do
Look up records. Products, Customers, Transactions, Gift Cards, Employees and Messages, including the external IDs that link them to your connected systems.
Answer business questions. Sales performance, inventory health, orders stuck in a sync, and gift card liability.
Investigate failed syncs. Read the error queue, explain the likely cause, point to the relevant help articles, and plan a fix.
Review your sync configuration. Connected systems, mapping collections, translations and webhooks.
Make changes, with your confirmation. Edit mappings and translations, create or update records, enable or disable webhooks, and resync individual records or small batches (up to 25 at a time) to a connected system.
Example requests
"Which iPaaS.com company am I connected to?"
"Which orders are stuck, and why?"
"This customer failed to sync. Walk me through the error."
"Which products have no external ID for my e-commerce system?"
"How much gift card liability do we have right now?"
"I want to change how Product prices map. Plan it with me before changing anything."
How it works
Your API key is your account. The server stores no credentials of its own. Every request carries your API key, and that key decides which company you see and what you are allowed to do.
One company per connection. A connection can't switch companies. To work in another company, connect with that company's API key.
Permissions are per tool area. If your key lacks a permission, only the tools in that area fail. Everything else keeps working.
Changes start as a preview. Tools that change data show you exactly what they would change, and nothing happens until you confirm.
What it is not
It shows the current state of your data. It doesn't keep record history, and reports that can't cover a date range say so.
It can't set up a connection to an external system for you, because that setup needs that system's own credentials. It points you to the connector's installation guide instead.
It can only use fields that are already defined in your integration. If a field you need doesn't exist yet, contact support@ipaas.com. Custom fields are the exception, and you can create them.
Before you begin
An iPaaS.com company and permission to create an API key.
An AI assistant that supports MCP, such as Claude, Claude Code, Cursor, VS Code with GitHub Copilot or Gemini CLI.
Node.js, but only if you connect Claude Desktop through its configuration file. The Getting Started article explains when you need it.
The iPaaS.com platform training, as noted at the top of this article.
Where to go next
Getting Started: create an API key, choose its permissions, and connect.
Choosing Your Tools: narrow the tool set to the area you are working in.
Safety, Permissions and Limits: how changes are confirmed and what to check before you confirm one.
Guides: investigating a failed sync, business reports, and reviewing mappings.
Tool Reference: every tool, by area.
Release Notes: what has changed, newest first.
Questions or bugs: mcp@ipaas.com.