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.
These are the tools for your connected systems and what they support: connections, integrations, lookups, custom fields and email templates. Connect with https://mcp.ipaas.com/mcp/systems to get just these (see Choosing Your Tools). You don't normally type tool names. Ask in plain language and the assistant picks the tool.
The tools
Connected systems and integrations
Tool | What it does | Changes data? |
list_subscriptions | Lists the external systems connected to your company. | No |
get_subscription | One connection, with its settings. The result can include secrets, such as a webhook key. | No |
resolve_subscription | Finds a subscription by its name, or by the name of its integration. | No |
list_integrations and get_integration | The catalog of integrations, and one integration's details, including what it supports. | No |
list_integration_versions | The versions of an integration. | No |
get_integration_custom_field | A custom field defined by an integration version. | No |
get_oauth | An OAuth connection record. | No |
What an integration can do
Tool | What it does | Changes data? |
get_subscription_features | Shows which data types and directions an integration can actually sync. | No |
check_feature_support | Gives a yes or no for one data type and direction. It guards against the case where the platform accepts a request but silently does nothing because the integration doesn't support it. | No |
check_integration_pair | Tells you whether system A and system B can exchange data, for which data types and in which directions, and whether the mapping collections for it already exist. | No |
plan_integration_onboarding | Plans the whole setup of an A-to-B integration as an ordered checklist, with the real IDs filled in, the outstanding placeholders and any blockers. It plans only. | No |
get_inbound_delivery | For each data type, tells you whether a system feeds iPaaS.com by webhook, by polling or both, and shows the poll events actually configured. | No |
Lookups
Tool | What it does | Changes data? |
get_lookup | A reference table by name, such as Country Code or Currency. | No |
list_lookup_tables | The catalog of reference tables. You can filter by data type or integration. | No |
list_lookup_fields | The fields that can be mapped for one system and one data type. Ask for a single combination, since the unfiltered list covers the whole platform. | No |
list_lookup_presets | The preset values available to mappings. | No |
list_lookup_custom_fields | The custom fields available for mapping. | No |
list_lookup_mapping_collections | Mapping collections in lookup form. | No |
list_available_permissions | The permission types iPaaS.com defines. | No |
Custom fields
Tool | What it does | Changes data? |
list_custom_field_definitions and get_custom_field_definition | The custom fields defined in your company. | No |
list_custom_fields_for_type | Custom fields for one type of record. | No |
get_custom_field_value | The value of a custom field, by ID. | No |
resolve_custom_field_target | Works out where a custom field would be created, from a system name and a data type, and shows what already exists there so you can reuse a field. | No |
create_custom_field | Creates a custom field definition, either internal to iPaaS.com or on a connected system. It blocks a duplicate name. | Yes (preview first) |
update_custom_field | Changes a definition's description, type, required flag or allowed values. Renaming a field is flagged. | Yes (preview first) |
delete_custom_field and reactivate_custom_field | Remove or restore a definition. The values it held on records do not come back. | Yes (preview first) |
Writing and email templates
Tool | What it does | Changes data? |
describe_write_schema | Shows what a write needs before you try it: the required fields, the allowed values, and fields the platform accepts but ignores. | No |
list_email_templates and get_email_template | Your email templates. | No |
Good to know
Some results can contain credentials. The connection and OAuth tools can return secrets. What a tool returns becomes part of your conversation with your AI provider, so only ask for them when you need to.
This tool set can't set up a connected system. That needs the system's own credentials. Ask the assistant to explain the setup instead.
Changes are previewed first. A tool that changes data shows exactly what it would send and changes nothing until you confirm. See Safety, Permissions and Limits.
A field has to be defined in the integration before it can be mapped. Custom fields are the exception, because you can create them.
Permissions
Give your key View on Subscription, Lookup, Custom Field and Email to read. Add Create, Edit or Delete on Custom Field only if you create or change custom fields. Without Subscription, the assistant can't turn a system's name into its ID. See Getting Started. Ask the assistant to check your permissions if a tool returns a 401.
Questions or bugs: mcp@ipaas.com.