Integration App
Created 6 months ago
Integration App MCP Server provides actions for connected integrations on Integration.app membrane.
What is Integration App?
Interact with any other SaaS applications on behalf of your customers.
Documentation
Integration App MCP Server
The Integration App MCP Server is a Model Context Protocol (MCP) server, it provides actions for connected integrations on Integration.app membrane as tools. Here's our official AI Agent Example that shows you how to use this MCP server in your application.
📋 Prerequisites
- Node.js (v18 or higher)
- An Integration.app account
⚙️ Installation
git clone https://github.com/integration-app/mcp-server.git
cd mcp-server
npm install
npm run build
🛠️ Local Development
To run the development server locally, start it with:
npm run dev
The server will be live at http://localhost:3000
⚡️ Running tests
npm run start:test\n\n# then run tests
npm test
🚀 Deployment
Deploy your own instance of this MCP server to any cloud hosting service of your choice.
🐳 Docker
The project includes a Dockerfile for easy containerized deployment.
docker build -t integration-app-mcp-server .
docker run -p 3000:3000 integration-app-mcp-server
🔗 Connecting to the MCP server
This MCP server supports two transports:
| Transport | Endpoint | Status |
| -------- | ---------------------------------------------------------------------- | |
| SSE (Server‑Sent Events) | /sse | 🔴 Deprecated — deprecated as of November 5, 2024 in MCP spec |
| HTTP (Streamable HTTP) | /mcp | 🟢 Recommended — replaces SSE and supports bidirectional streaming |
🔐 Authentication
Provide an Integration.app access token via query or Authorization header:
?token=ACCESS_TOKEN
Authorization: Bearer ACCESS_TOKEN
⚡ Static vs Dynamic Mode
By default, the MCP server runs in static mode, which means it returns all available tools (actions) for all connected integrations. With dynamic mode (?mode=dynamic), the server will only return one tool: enable-tools.
💬 Chat Session Management (Experimental)
The MCP server (streamable-http transport only) supports persistent chat sessions. Include an x-chat-id header in your requests to automatically track sessions for that specific chat.
🔧 Troubleshooting
- Ensure your access token is valid and you're generating it according to these instructions
- Check the MCP server logs for any errors or issues during startup or connection attempts.
- Use the MCP Inspector for testing and debugging
Server Config
{
"mcpServers": {
"integration-app-server": {
"command": "npx",
"args": [
"integration-app"
]
}
}
}