The Integration App MCP Server is a Model Context Protocol (MCP) server that provides actions for connected integrations on Integration.app membrane as tools. It enables your applications to interact with various integrations through a standardized protocol, making it easier to build AI-powered applications with access to external tools and services.
To get started with the Integration App MCP Server, follow these steps:
git clone https://github.com/integration-app/mcp-server.git
cd mcp-server
npm install
npm run build
After installation, you can run the development server locally with:
npm run dev
The server will be available at http://localhost:3000.
For containerized deployment, you can use the included Dockerfile:
docker build -t integration-app-mcp-server .
docker run -p 3000:3000 integration-app-mcp-server
The MCP server supports two transport protocols:
The Streamable HTTP transport is the recommended approach:
import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';
const client = new Client({
name: 'example-integration-app-mcp-client',
version: '1.0.0',
});
const transport = new StreamableHTTPClientTransport(
new URL(`https://<HOSTED_MCP_SERVER_URL>/mcp`),
{
requestInit: {
headers: {
Authorization: `Bearer ${ACCESS_TOKEN}`,
},
},
}
);
await client.connect(transport);
The Server-Sent Events (SSE) transport is deprecated but still supported:
await client.connect(
new SSEClientTransport(
new URL(`https://<HOSTED_MCP_SERVER_URL>/sse`),
{
requestInit: {
headers: {
Authorization: `Bearer ${ACCESS_TOKEN}`,
},
},
}
)
);
You must provide an Integration.app access token via a query parameter or the Authorization header:
?token=ACCESS_TOKEN
Authorization: Bearer ACCESS_TOKEN
By default, the MCP server runs in static mode, returning all available tools (actions) for all connected integrations.
In dynamic mode, the server only returns one tool: enable-tools. This allows you to selectively enable specific tools as needed.
To use dynamic mode, append ?mode=dynamic to your connection URL:
const transport = new StreamableHTTPClientTransport(
new URL(`https://<HOSTED_MCP_SERVER_URL>/mcp?mode=dynamic`),
{
requestInit: {
headers: {
Authorization: `Bearer ${ACCESS_TOKEN}`,
},
},
}
);
await client.connect(transport);
// Enable specific tools
await client.callTool({
name: 'enable-tools',
arguments: {
tools: ['gmail-send-email', 'gmail-read-email'],
},
});
You can choose to only fetch tools for specific integrations by using the apps query parameter:
/mcp?apps=google-calendar,google-docs
The MCP server supports persistent chat sessions through the streamable-HTTP transport. Include an x-chat-id header in your requests to track sessions for a specific chat:
POST /mcp
Authorization: Bearer YOUR_ACCESS_TOKEN
x-chat-id: my-awesome-chat-123
To retrieve your active chat sessions:
GET /mcp/sessions
Authorization: Bearer YOUR_ACCESS_TOKEN
This will return a response like:
{
"my-awesome-chat-123": "session-uuid-1",
"another-chat-456": "session-uuid-2"
}
To use this server with Cursor, update the ~/.cursor/mcp.json file:
{
"mcpServers": {
"integration-app": {
"url": "https://<HOSTED_MCP_SERVER_URL>/sse?token={ACCESS_TOKEN}"
}
}
}
Restart Cursor for the changes to take effect.
To use this server with Claude, update the config file (Settings > Developer > Edit Config):
{
"mcpServers": {
"integration-app": {
"url": "https://<HOSTED_MCP_SERVER_URL>/sse?token={ACCESS_TOKEN}"
}
}
}
If you encounter issues with the MCP server:
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "integration-app" '{"url":"https://<HOSTED_MCP_SERVER_URL>/sse?token={ACCESS_TOKEN}"}'See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"integration-app": {
"url": "https://<HOSTED_MCP_SERVER_URL>/sse?token={ACCESS_TOKEN}"
}
}
}To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"integration-app": {
"url": "https://<HOSTED_MCP_SERVER_URL>/sse?token={ACCESS_TOKEN}"
}
}
}3. Restart Claude Desktop for the changes to take effect