Skip to navigation

MCP server

Every Living Brain API operation as a tool for Claude, Cursor, and other MCP clients.
Generated by Fern

Living Brain hosts a Model Context Protocol server, so AI agents can capture knowledge, search pages, and manage brains without any code on your side.

https://livingbrain.fernmcp.dev/livingbrain

It uses the Streamable HTTP transport and calls the production API at https://api.livingbrain.com.

Connect a client

Pick your client
Browse all 60 tools ↗
Terminal
claude mcp add --transport http livingbrain \
  https://livingbrain.fernmcp.dev/livingbrain \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'x-subject-id: YOUR_SUBJECT_ID'

Run it in a terminal. Claude Code picks the server up on its next start.

Replace YOUR_API_KEY and YOUR_SUBJECT_ID with your own values (see Authenticate). Any other MCP client that supports remote HTTP servers with custom headers works the same way.

Authenticate

The server forwards the same two headers as the SDKs and CLI. Configure your client to send both on every request:

HeaderValue
x-api-keyYour Living Brain API key
x-subject-idThe end user whose brains the agent works with

See Authentication for how the key and subject relate. Treat the config file like any other place you store the key.

Tools

Each API operation is one tool, named <namespace>_<method> after the SDK methods and grouped into toolsets by namespace:

ToolsetExamples
Brainsbrains_list, brains_create, brains_run_brief
Capturescaptures_capture, captures_capture_chat_turn, captures_list_sources
Workspaceworkspace_search_pages, workspace_get_page, workspace_archive, workspace_restore
Slackslack_status, slack_start_oauth, slack_bind, slack_disconnect_installation
Telegramtelegram_status, telegram_connect, telegram_disconnect
Webhookswebhooks_list, webhooks_create, webhooks_update, webhooks_remove

Tool arguments follow the API Reference: path, query, and body parameters become tool inputs, and calls return the same JSON responses.