Overview
The Integration App MCP Server is a Model Context Protocol (MCP) server that exposes actions (tools) for all connected integrations on the Integration.app membrane. It supports two transports: Server-Sent Events (SSE) and streamable HTTP, with SSE deprecated in the MCP spec and HTTP recommended for bidirectional streaming. By default the server runs in static mode, returning all available tools for every connected integration; in dynamic mode (?mode=dynamic) it returns only the enable-tools tool, enabling you to selectively enable the tools you need for a session. Authentication is performed via an Integration.app access token supplied as a query parameter or in the Authorization header. The server includes guidance for local development (Node.js v18+, npm), building, and running, along with a Dockerfile for containerized deployment. Tools for a specific integration can be fetched using the apps query parameter (e.g., /mcp?apps=google-calendar,google-docs). An experimental chat-session feature lets you attach x-chat-id headers to preserve a session. The README also demonstrates configuring MCP clients (Cursor, Claude Desktop) and provides an AI Agent Example to illustrate usage.
Features
Static mode (default)
Returns all available tools for all connected integrations by default.
Dynamic mode
Use ?mode=dynamic to return only the enable-tools tool, enabling selective exposure for a session.
Two transports
Supports SSE (deprecated) and Streamable HTTP (recommended) for MCP communications.
Token-based authentication
Authenticate using an Integration.app access token via query parameter or Authorization header.
App-scoped tool retrieval
In static mode, fetch tools for all connections or constrain to specific apps with the apps parameter.
Chat session management (experimental)
Persistent chat sessions via x-chat-id header to preserve conversations.
Docker deployment
Dockerfile included for containerized deployment and easy hosting.
Client configuration support
Guides for connecting with MCP clients like Cursor and Claude Desktop.
Who Is This For?
- Developers:Build integrations and MCP clients that consume tools exposed by the server.
- AI agents:Power AI agents to discover, enable, and call tools via MCP transports.
- Integrations teams:Deploy and manage integrations across customer environments using static or dynamic tool exposure.
