MCP servers
Extend Morbium with Model Context Protocol servers to give the AI new tools, added from config or the in-app marketplace.
Model Context Protocol, or MCP, is an open standard for giving an AI new tools. Connect an MCP server and its tools become available to Morbium's agents, so the AI can do things it could not before, like drive a browser or query your own services.
Add a server in config
MCP servers go under the mcp key in morbium.json, keyed by a unique name you choose. You can then refer to a server by that name when you prompt the AI. There are two kinds.
A local server is a command Morbium runs on your machine:
{
"$schema": "https://morbium.co/config.json",
"mcp": {
"playwright": {
"type": "local",
"command": ["npx", "-y", "@playwright/mcp"],
"environment": { "BROWSER": "chromium" },
"enabled": true
}
}
}
A remote server is a URL:
{
"$schema": "https://morbium.co/config.json",
"mcp": {
"github": {
"type": "remote",
"url": "https://api.example.com/mcp",
"headers": { "Authorization": "Bearer {env:GITHUB_TOKEN}" },
"enabled": true
}
}
}
Fields:
type:localorremote.command: for local servers, the command and its arguments.environment: environment variables for a local server.urlandheaders: for remote servers.enabled: setfalseto turn off a server (including one inherited from your global config).
Header and token strings support interpolation: {env:VAR} reads an environment variable and {file:path} reads a file, so secrets never sit in the config.
The marketplace
You do not have to write config by hand. Open the MCP marketplace in the app to browse servers from the official registry, search, and install one with a click. It is the quickest way to add a server.
Using MCP tools
Once a server is connected, its tools show up to agents automatically, and the MCPs control next to the composer shows what is active. Like any tool, MCP tools are subject to permissions.