mcp-server

Provides an MCP (Model Context Protocol) server for Membrane that exposes Membrane integration actions as MCP tools. Supports connecting over HTTP streamable transport and (deprecated) SSE, with token-based authentication and optional static vs dynamic tool exposure.

Evaluated Mar 30, 2026 (21d ago)

Repo ↗ DevTools mcp membrane agents typescript integration streamable-http sse

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Uses bearer token authentication and is intended to be accessed over HTTPS endpoints. Provided docs show token passing in Authorization header (preferred) or query parameter. Scope granularity and security/error details are not documented in the provided material.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want to expose Membrane-connected actions to an MCP-capable agent using the recommended streamable HTTP transport (/mcp).

Avoid When

If you need long-term support exclusively via SSE, or you cannot use Authorization header / query token for auth.

Use Cases

• Let an LLM/agent call Membrane integration actions (tools) via MCP
• Build agent workflows that enable only a subset of tools per session (dynamic mode via enable-tools)
• Use persistent chat sessions with a custom x-chat-id header (streamable HTTP only)
• Integrate with MCP-compatible clients such as Cursor and Claude Desktop

Not For

• Use cases requiring standard public REST/GraphQL APIs rather than MCP tool interfaces
• Environments where token credentials cannot be securely handled
• Clients that only support SSE (since SSE transport is marked deprecated)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Yes

Webhooks

Authentication

Methods: Membrane access token via query parameter (?token=...) Membrane access token via Authorization: Bearer ...

OAuth: No Scopes: No

Auth is documented as a single Membrane access token presented via query or Authorization header. No explicit scope model is described in the provided README.

Pricing

Free tier: No

Requires CC: No

Pricing for the MCP server itself is not specified in the provided content; Membrane account pricing may apply.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ SSE transport is explicitly deprecated; prefer /mcp streamable HTTP
⚠ In dynamic mode, the server returns only the enable-tools tool; the agent must call enable-tools before attempting other tools
⚠ Experimental persistent sessions require using the x-chat-id header (streamable HTTP only)

Alternatives

Call Membrane APIs directly (if available) from your agent instead of via MCP Use other MCP servers/integration adapters that expose equivalent toolsets to agents

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.