MCP Server

Connect Claude Code, Cursor, or Codex to your Lucius financial data with OAuth — read-only tools for burn, runway, invoices, and ledger.

Server URL

https://api.lucius.finance/mcp

Transport: Streamable HTTP · Auth: OAuth 2.1 (PKCE)

Revoke access anytime in the Lucius dashboard → Settings → Connected Agents.

Fastest: Add to Cursor — click the link, confirm install, then complete OAuth when prompted.

Or add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

{
  "mcpServers": {
    "lucius": {
      "url": "https://api.lucius.finance/mcp"
    }
  }
}

Or use the UI: Cursor MCP docs → Settings → Tools & MCP → Add server → paste the URL above.

After adding, restart Cursor if tools don't appear. First tool call triggers the OAuth browser flow.

Run in your terminal (Claude Code MCP docs):

claude mcp add --transport http lucius https://api.lucius.finance/mcp

Start a Claude Code session and ask a financial question — your browser opens for Lucius login and consent.

Useful commands:

claude mcp list          # verify lucius is registered
claude mcp remove lucius # disconnect

codex mcp add lucius --url https://api.lucius.finance/mcp

Authenticate (OAuth browser flow):

codex mcp login lucius

Start Codex (codex) and run /mcp to confirm lucius is connected.

Or edit ~/.codex/config.toml:

[mcp_servers.lucius]
url = "https://api.lucius.finance/mcp"

For Claude on the web (Claude connectors):

Requires a Claude plan that supports custom connectors.

Once connected, try:

Agents can chain tools automatically — e.g. burn spike → costs breakdown → transactions for a specific account.

Scope	Access
`read:analytics`	Burn, runway, revenue trends, forecasts
`read:reports`	P&L, balance sheet, cash flow, deferred revenue
`read:transactions`	Bank balances and transactions
`read:invoices`	Receivables, payables, customers, vendors, contracts
`read:ledger`	Journal entries, chart of accounts, account activity

Scopes granted at consent are capped by your org role in Lucius.