Integration App MCP Server

Name: Integration App MCP Server
Author: integration-app

@integration-app

リポジトリ

Integration App MCP Server について

MCP Server for Membrane

基本情報

カテゴリ

その他

ライセンス

ISC

ランタイム

node

トランスポート

stdio

公開者

integration-app

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp-server-integration-app": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "membrane-mcp-server",
        "."
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Membrane MCP Server?

The Membrane MCP Server is a Model Context Protocol (MCP) server that provides actions for connected integrations on Membrane as tools. It is intended for developers building AI agents that need to interact with third-party services through Membrane.

How to use Membrane MCP Server?

Install Node.js v18+, clone the repository, run npm install and npm run build. For local development, run npm run dev. Connect using SSE (deprecated) or Streamable HTTP (recommended) transports, authenticating with a Membrane access token via query parameter or Authorization header.

Key features of Membrane MCP Server

Provides actions from connected Membrane integrations as MCP tools.
Supports both SSE (deprecated) and Streamable HTTP (recommended) transports.
Offers static mode (all tools) and dynamic mode (selective tool enabling).
Allows filtering tools by specific integrations via apps query parameter.
Includes experimental chat session management for persistent conversations.
Can be deployed via Docker or any cloud hosting service.

Use cases of Membrane MCP Server

Build AI agents that can read and send emails via Gmail integration.
Create chatbots that manage calendar events using Google Calendar tools.
Enable AI assistants to search and retrieve documents from Google Docs.
Develop applications that orchestrate multiple integrations based on user queries.

FAQ from Membrane MCP Server

How do I authenticate?

Provide a Membrane access token either as a query parameter ?token=ACCESS_TOKEN or via Authorization: Bearer ACCESS_TOKEN header.

What is the difference between static and dynamic mode?

In static mode, the server returns all available tools for all connected integrations. In dynamic mode, only the enable-tools tool is returned, allowing selective enablement of specific tools per session.