Membranehq Mcp Server

Membrane 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

git clone https://github.com/membranehq/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

# Run the server in test mode
npm run start:test

# 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 membrane-mcp-server .
docker run -p 3000:3000 membrane-mcp-server

🔗 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:

?token=ACCESS_TOKEN
Authorization: Bearer ACCESS_TOKEN

SSE (Deprecated)

await client.connect(
  new SSEClientTransport(
    new URL(
      `https:///sse`
    )
    {
      requestInit: {
        headers: {
          Authorization: `Bearer ${ACCESS_TOKEN}`,
        },
      },
    }
  )
);

Streamable HTTP (Recommended)

await client.connect(
  new StreamableHTTPClientTransport(
    new URL(`https:///mcp`)
    {
      requestInit: {
        headers: {
          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. 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.

import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';

const client = new Client({
  name: 'example-membrane-mcp-client',
  version: '1.0.0',
});

const transport = new StreamableHTTPClientTransport(
  new URL(`https:///mcp?mode=dynamic`),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${ACCESS_TOKEN}`,
      },
    },
  }
);

await client.connect(transport);

await client.callTool({
  name: 'enable-tools',
  arguments: {
    tools: ['gmail-send-email', 'gmail-read-email'],
  },
});

🔧 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.

Starting a new chat session:

POST /mcp
Authorization: Bearer YOUR_ACCESS_TOKEN
x-chat-id: my-awesome-chat-123

Retrieving your chat sessions:

GET /mcp/sessions
Authorization: Bearer YOUR_ACCESS_TOKEN

Response:

{
  "my-awesome-chat-123": "session-uuid-1",
  "another-chat-456": "session-uuid-2"
}

This feature lets you use same session for a conversation. Check out our AI Agent Example to see how this works in practice.

Configuring other MCP clients

📝 Cursor

To use this server with Cursor, update the ~/.cursor/mcp.json file:

{
  "mcpServers": {
    "membrane": {
      "url": "https:///sse?token={ACCESS_TOKEN}"
    }
  }
}

Restart Cursor for the changes to take effect.

🤖 Claude Desktop

To use this server with Claude, update the config file (Settings > Developer > Edit Config):

{
  "mcpServers": {
    "membrane": {
      "url": "https:///sse?token={ACCESS_TOKEN}"
    }
  }
}

🔧 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

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: membranehq
• Source: membranehq/mcp-server
• License: ISC

Install and usage instructions live in the source repository linked above.