The Membrane MCP Server (formerly Integration.app), built by membranehq, provides the Membrane MCP Server is the official Model Context Protocol integration for Membrane, the agentic integration platform formerly known as Integration.app — the company rebranded to getmembrane.com in 2026, and its GitHub org moved from `integration-app` to `membranehq`, which is why the old `integration-app/mcp-server` repo URL no longer resolves. It is officially maintained and best for API & Web.
by membranehq
About
The Membrane MCP Server is the official Model Context Protocol integration for Membrane, the agentic integration platform formerly known as Integration.app — the company rebranded to getmembrane.com in 2026, and its GitHub org moved from `integration-app` to `membranehq`, which is why the old `integration-app/mcp-server` repo URL no longer resolves. Membrane connects AI agents, products, and internal tools to 100,000+ third-party SaaS applications through a single unified integration layer, so instead of writing bespoke API clients for every app your customers use, an agent calls one MCP server and Membrane routes the request to the right connected integration. The server exposes "actions for connected integrations on Membrane" as MCP tools: in static mode it returns every available action across all connected apps, while dynamic mode lets a client selectively enable only the tools it needs via an `enable-tools` call, and requests can be scoped to specific apps with an `apps` query parameter. Authentication is a Membrane access token, supplied either as a `?token=` query parameter or an `Authorization: Bearer` header — there is no anonymous/no-account mode. It ships as a self-hosted Node.js (v18+) server: clone the repo, `npm install && npm run build`, then run it locally (`npm run dev` serves on `http://localhost:3000`) or containerize it with the provided Docker setup for your own cloud hosting. It speaks MCP over streamable HTTP at `/mcp` (recommended) and a deprecated SSE endpoint at `/sse`. Typical use: an agent needs to "create a contact in whichever CRM this customer has connected" or "sync this record to their connected apps" without the developer hand-building integrations for every possible SaaS target — Membrane's pre-built connector catalog and unified data model handle the app-specific translation.
Trust verdict
How grades are computed →Grade B (81/100, solid) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.
What was measured
- Repository maintenance55/100 · weight 20
The last push or release is between six and eighteen months old. — last push 2026-03-04.
- Source verification100/100 · weight 25
The repository URL was confirmed to resolve against the live GitHub API and is not archived.
- Provenance90/100 · weight 10
Published and maintained by the vendor of the service it connects to, rather than by a third party.
- Listing ↔ repository match70/100 · weight 5
The linked repository membranehq/mcp-server was confirmed to exist, but its name does not obviously correspond to this listing. Worth opening the repo before you trust the mapping.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Live MCP handshakeunknown
No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.
- Measured uptimeunknown
No probe history recorded for this server yet.
- Tool-schema stabilityunknown
Drift is a difference between two successive checks, and this server has none recorded.
Installation
git clone https://github.com/membranehq/mcp-server.git && cd mcp-server && npm install && npm run buildCategories
Frequently Asked Questions
What is Membrane MCP Server (formerly Integration.app)?
Who built Membrane MCP Server (formerly Integration.app)?
Is Membrane MCP Server (formerly Integration.app) free?
How do I install Membrane MCP Server (formerly Integration.app)?
What does Membrane MCP Server (formerly Integration.app) integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Last commit
- 6mo ago
- Install
- npm
- Package
- git
Quick Info
- Install Type
- npm
- Author
- membranehq
- Categories
- 1
- Integrations
- 5
Related Servers
Fetch
Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.
Apify MCP Server
The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.
Browserbase MCP Server
Browserbase MCP and Stagehand MCP are the same server under two names, and this catalog lists both because people search for both — this page is the platform view, /servers/stagehand covers the natural-language automation layer that runs inside it. What Browserbase supplies is the browser itself: a headless Chrome session running in Browserbase's cloud rather than on the machine your agent is on, which is the reason to use it at all. The session is a real, addressable browser with its own residential-proxy and stealth configuration and a recorded replay you can watch afterwards, so an agent's browsing survives being run from a datacenter IP, and a failed run is debuggable after the fact instead of being a black box. Nothing renders on the developer's machine, so a long-running agent is not tied to a desktop staying awake. Browserbase's recommendation is the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they operate it and absorb the model inference that the instruction-following tools require. Clients without HTTP transport connect via npx mcp-remote https://mcp.browserbase.com/mcp. Self-hosting installs @browserbasehq/mcp-server-browserbase from npm and needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID from your dashboard. Six tools are exposed — start and end for session lifecycle, navigate, act, observe and extract — and they are documented in detail on the Stagehand entry, because the act/observe/extract trio is Stagehand's model rather than Browserbase's. One thing to know before self-hosting: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now says it is kept for historical reference and should not be read as representative of the current production service. The npm package still installs and the star count on this page belongs to that archived repo; the hosted endpoint is the path Browserbase actually maintains.
Firecrawl MCP Server
The Firecrawl MCP server gives your AI assistant the ability to crawl, scrape, and extract structured data from any website — turning raw HTML into clean, LLM-ready Markdown or JSON in seconds. Built by the Firecrawl team, it exposes tools for single-page scraping, deep site crawls (following internal links), and batch URL extraction, all with JavaScript rendering handled automatically so dynamic content is never missed. Developers use it to automate competitive research, build live knowledge bases, extract pricing tables, monitor documentation changes, or feed structured web data into RAG pipelines — all through natural-language prompts without writing a single scraper script. The Firecrawl MCP server handles rate limiting, retries, and proxy rotation behind the scenes. Authentication requires a Firecrawl API key (free tier available). Install with: npx firecrawl-mcp. Works with Claude Desktop, Cursor, VS Code, and any MCP-compatible client. With Firecrawl, any public webpage becomes a structured data source your AI can reason over, compare, and act on — making it the go-to MCP server for web data extraction workflows.
Notion MCP Server
The Notion MCP Server is the official integration from Notion that connects AI assistants directly to your Notion workspace via the Notion REST API. With 4,580+ GitHub stars, it is the canonical MCP tool for bringing Notion's knowledge management capabilities into Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. The server exposes a rich set of tools: search your entire workspace by keyword and return matching pages and databases; retrieve full page content and block trees; create new pages inside any parent page or workspace section; update, append, or delete block content on existing pages; list all databases your integration has access to; query database entries with filter and sort parameters; retrieve individual blocks or nested children by block ID; and add comments to pages. Authentication uses a Notion integration token — create an internal integration at notion.so/my-integrations, share specific pages or databases with it, and set NOTION_TOKEN in your environment (the older OPENAPI_MCP_HEADERS form still works). Install with a single npx command. The Notion MCP Server is especially powerful for AI workflows that span documentation retrieval, project planning, and knowledge capture — Claude can read product specs from Notion, draft new pages from conversation output, log structured data into databases, and search across thousands of notes without any manual copy-paste.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →