MCP Server für Integration Package Management
MCP Integration Suite MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Integration Suite directly instead of describing what you should do. MCP Server für Integration Package Management.
DISCLAIMER: This server is still experimental. Use at your own risk! # MCP Integration Suite Server
Once MCP Integration Suite is connected, these are the calls the assistant has available:
packages — Get all integration packagespackage — Get content of an integration package by namecreate-package — Create a new integration packageget-iflow — Get the data of an IFlow and contained resourcescreate-empty-iflow — Create an empty IFlowupdate-iflow — Update or create files/content of an IFlowget-iflow-endpoints — Get endpoints of IFlow and its URLs/Protocolsiflow-image — Get the IFlow logic shown as a diagramdeploy-iflow — Deploy an IFlowget-iflow-configurations — Get all configurations of an IFlowget-all-iflows — Get a list of all available IFlows in a Packageget-messagemapping — Get data of a Message MappingNodeJs and NPM (Node Version > 20 because of native NodeJS fetch)
Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Integration Suite's toolset — packages, package, create-package and 11 more — is a fair guide to whether it matches your workflow. It is maintained by 1nbuc; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| packages | Get all integration packages |
| package | Get content of an integration package by name |
| create-package | Create a new integration package |
| get-iflow | Get the data of an IFlow and contained resources |
| create-empty-iflow | Create an empty IFlow |
| update-iflow | Update or create files/content of an IFlow |
| get-iflow-endpoints | Get endpoints of IFlow and its URLs/Protocols |
| iflow-image | Get the IFlow logic shown as a diagram |
| deploy-iflow | Deploy an IFlow |
| get-iflow-configurations | Get all configurations of an IFlow |
| get-all-iflows | Get a list of all available IFlows in a Package |
| get-messagemapping | Get data of a Message Mapping |
| update-message-mapping | Update Message Mapping files/content |
| deploy-message-mapping | Deploy a message-mapping |
{
"mcpServers": {
"integration-suite": {
"command": "npx",
"args": ["-y", "npm"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
NodeJs and NPM (Node Version > 20 because of native NodeJS fetch)
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.