MCP Servers (Per-App)
Attach external Model Context Protocol servers to a specific app so the AI building the app can call your custom tools. Sibling to /docs/mcp, which covers calling GenMB from external MCP clients.
Adding MCP servers to an app requires a Pro or Business plan.
Adding a Server
Open the MCP panel
Click Add Server
Verify the connection
Auth Headers
Custom headers are stored per-server and sent on every tool call. The most common pattern:
Authorization: Bearer YOUR_SECRET_TOKEN
X-Workspace-Id: ws_123How the Generator Uses It
During generation and chat refinement, the AI sees the union of GenMB's built-in tools and the tools exposed by attached MCP servers. When a tool call would help (e.g. fetching real data, calling a domain-specific API), the AI invokes it; the result flows back into the generation context.
For external clients (Claude Desktop, Cursor) calling GenMB's own MCP server, see the MCP Integration page.
Limits
- Cap on attached servers per app (validated server-side when adding).
- Server URL must be HTTPS and publicly reachable.
- Tool discovery + invocation must respect GenMB's per-app rate limits (200 req / min / IP applies to outbound calls too).
- Pro or Business plan required to add a server. Listing existing servers is allowed on any plan.
FAQs
How is this different from /docs/mcp?▾
What can an attached MCP server do?▾
Where does the MCP server need to run?▾
Can I gate access with a key?▾
Ready to build?
Create your first app for free, no credit card required.