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.
By default, the iPaaS.com MCP server gives your assistant every tool it has, which is more than 240. That works, but an assistant with that many choices is slower and more likely to pick the wrong one. If you know what you're working on, tell the server and you will get sharper, faster results.
How to choose
Add a domain to the end of the server URL. A domain is a group of related tools, such as products or transactions.
You connect to | You get |
| Every tool |
| Only the product tools, plus the always-available tools below |
| Transactions and customers together (separate domains with commas) |
Three things to know:
You choose when you connect, and it stays that way. The tool list doesn't change during a conversation. To change it, edit the server URL in your connection settings and restart the app or start a new session.
You can combine domains. Work across data types by listing several, such as
/mcp/transaction,customer,mappings.Domains don't change what your key can do. Your API key's permissions still decide what is allowed (see Getting Started). Choosing a smaller set of tools just means the assistant can't reach for the others.
The domains
Add to the URL | What it covers | Can change data? |
The product catalog: products, variants, inventory, categories, locations, kits and options | Yes | |
Customers, addresses, categories and customer companies | Yes | |
Orders and invoices, with their lines, payments, taxes and shipping | Yes | |
Gift cards and their activity history | Yes | |
Employees, their addresses and timesheets | Yes | |
Notification messages and image assets | Yes | |
Answers to business questions: sales summary, inventory health, stuck orders and gift card liability. Also the field map tools, which store which of your custom fields holds each business value. | The reports only read. Two field map tools can change settings, and both show a preview first. | |
Connected systems and integrations, what each integration supports, lookups, platform settings and custom field definitions | Yes (custom fields) | |
Mapping and translation collections, formulas and scopes, with analysis tools | Yes | |
Keeping syncs healthy: webhooks, errors, logs, diagnosing failures, resyncing records, events and polling | Yes, including resyncs |
Shortcuts for common combinations
Add to the URL | Same as |
| product, customer, transaction and giftcard |
| systems, mappings and operations |
You can mix a shortcut with plain domains, for example /mcp/retail,mappings.
Which should I pick?
If you want to | Use |
Ask plain-language questions about how the business is doing |
|
Look up products, customers, orders and gift cards |
|
Work an order problem, including the customer on the order |
|
Find out why a sync failed and fix it |
|
Review or change how data maps between systems |
|
Explore everything, or you're not sure yet |
|
Tools that are always available
A few tools are on every connection, whichever domains you choose:
get_active_tenant and check_my_permissions: which company you're connected to, and what your key can do.
match_data_type, get_data_model, list_platform_categories and get_platform_category: reference information about iPaaS.com data types and connected system categories.
find_help_articles, build_ipaas_url, parse_ipaas_url and get_api_contract: finding help articles, linking to and decoding portal screens, and reading the iPaaS.com API's own documentation.
Where to put the domain
Add it to the server URL in whichever setting your app uses. The Getting Started article shows each one.
Claude custom connector: in the server URL field, for example
https://mcp.ipaas.com/mcp/retail.Claude Code: in the
claude mcp addcommand, in place of the plain URL.Cursor, VS Code, Gemini CLI: in the
url(orhttpUrl) value in the JSON file.Claude Desktop configuration file: in the URL line inside
args.
Apps that let you add headers can send the domain in a header instead of the URL. The header name is X-Ipaas-Domain, and the value is the same list, for example transaction,customer. If you use the mcp-remote configuration, remember no space after the colon, as in X-Ipaas-Domain:transaction,customer.
How results read
Separately from which tools you get, you can choose how results read. By default, results are written for technical users. If you're a business user, ask for the business style, which keeps technical working notes out of what you see and presents the answer in plain language.
Add
?audience=businessto the end of the server URL.Or, in an app that lets you add headers, send
X-Ipaas-Audiencewith the valuebusiness.
This only changes how results read. It never changes which tools exist, what they do or what your key allows. A common choice for a non-technical user is the business domain with the business style:
https://mcp.ipaas.com/mcp/business?audience=business
You can combine the two with other domains too, for example https://mcp.ipaas.com/mcp/business,customer,product?audience=business.
If something doesn't work
A tool you expected isn't there. Check which domain you connected with. A tool outside your domains doesn't appear. Add the domain to the URL, then restart the app or start a new session.
I changed the URL but nothing changed. The tool list is fixed when the connection starts. Fully quit and reopen the app, or start a new session.
A tool is there but returns 401. The domain is fine, but your key lacks permission for that area. Ask the assistant to run check_my_permissions.
The assistant seems slow or picks odd tools. Connect with a smaller set of domains.
Anything else: mcp@ipaas.com.
