membranehq/mcp-server

The Membrane MCP Server is a Model Context Protocol (MCP) server, it provides actions for connected integrations on 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)
- A Membrane account
⚙️ Installation
🛠️ Local Development
To run the development server locally, start it with:
The server will be live at http://localhost:3000 ⚡️
🧪 Running tests
🚀 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.
🔗 Connecting to the MCP server
This MCP server support 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 a Membrane access token via query or Authorization header:
**SSE** (Deprecated)
**Streamable HTTP** (Recommended)
⚡ 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. You can use this tool to selectively enable the tools you actually need for that session.
In dynamic mode, your implementation should figure out which tools are most relevant to the user's query. Once you've identified them, prompt the LLM to call the enable-tools tool with the appropriate list.
Want to see how this works in practice? Check out our AI Agent Example.
🔧 Getting tools for a specific integrations
In static mode, the MCP server fetches tools from all active connections associated with the provided token.
You can choose to only fetch tools for a specific integration by passing the apps query parameter: /mcp?apps=google-calendar,google-docs
💬 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. This is an experimental feature that we provide in addition to standard MCP sessions.