Levirge Brain · install

Connect any MCP client

The endpoint, the auth, and the read-only call that proves the connection works — for any client that speaks MCP over Streamable HTTP.

No plugin needed. Any client that speaks MCP over Streamable HTTP can connect.

Endpoint

https://brain.levirge.com/mcp

The machine-readable definition is at /brain/mcp.json.

Configuration

{ "mcpServers": { "brain": {
    "type": "streamable-http",
    "url": "https://brain.levirge.com/mcp" } } }

Clients name these keys differently (for example VS Code uses servers and "type": "http", Cline uses "streamableHttp"). Use your client's own field names; the URL and transport are what matter. If the client offers stdio only, it cannot connect yet.

Auth

OAuth is negotiated on connect — add nothing to the config and your client will prompt. Where a browser round-trip isn't possible, use a token instead:

  1. Open Profile → MCP Tokens and click + New token.
  2. Label it (for example "CI"). Optionally limit it to some Vaults and to Read-only, then click Create.
  3. Copy it now: it is shown once. Lost it? Revoke it and make a new one.

Then send it on every request, usually as a headers entry in the server's config:

Authorization: Bearer <your-token>

A token acts as you, limited to the Vaults and access you picked. A token cannot create another token.

Verify

kb_overview

Read-only, and it returns your workspace's knowledge summary — a clean answer proves the endpoint, the auth and the vault access at once.

Then what

Start with search_knowledge("<your question>"), and capture what you learn with add_knowledge — identical content deduplicates, so retries are safe. The full tool list is in the tool reference.

Clients with a guide

Claude Code, Claude Desktop, Codex, ChatGPT, Cursor, VS Code, Gemini CLI, Antigravity, Windsurf, Cline, OpenCode, pi, oh-my-pi, Obsidian. No workspace yet? Request access.

← Levirge Brain Request access →