Guides

Connect Claude with MCP

Drive Reventlov from Claude in plain English.

Reventlov ships an open-source Model Context Protocol server that exposes the dashboard API as native tools for Claude. Once installed, Claude can answer questions about your agent’s activity, decide on pending approvals, issue directives, and post financials — directly from any conversation.

> What's the state of Valerie right now?
  Claude calls get_company_overview and summarizes pending approvals,
  OpenClaw runtime health, recent activity, and upcoming filings.
> What tools and skills does Valerie have enabled?
  Claude calls get_openclaw_runtime and reads the latest sanitized
  OpenClaw snapshot.
> Approve the AWS payment.
  Claude calls list_pending_approvals → finds the match → decide_approval.
> Tell Valerie to follow up with last quarter's top customers.
  Claude calls issue_directive (hash-chained on the directives ledger).

The package is @reventlovmcp/mcp. Source: gitlab.com/reventlov/mcp.

What the MCP can do

Fourteen tools mapping 1:1 to the public API:

CategoryTools
Auditlog_action · list_recent_actions · list_pending_approvals · decide_approval · resolve_flag
Ruleslist_rules · create_rule
Directivesissue_directive · list_directives
Compliancelist_filings
Financialspost_cash_balance · post_bank_transactions · post_financial_snapshot
OpenClawget_openclaw_runtime
Composedget_company_overview

Prerequisites

  • A human-scope API key — Dashboard → Settings → API keys → Create key
  • The company id (co_...) you want as default — visible on every company page (Company ID badge under the title) and in the Companies table on the Overview page

For the Claude Code / Desktop installs, also: Node 20+ (brew install node). The web Connector route doesn’t need anything installed locally.

The fastest path. Anyone with a Reventlov account can add the connector without installing anything on their machine.

The dashboard does the URL assembly for you:

  1. Open Settings → API keys in your dashboard
  2. Click Create key (scope: human, name it claude.ai connector)
  3. The success panel shows your raw sk_... value AND the install snippets pre-filled with that key — claude.ai web tab is selected by default
  4. Click Copy URL on the URL block, then Open claude.ai Connectors →
  5. In claude.ai, click Add custom connector, paste the URL into the Remote MCP server URL field, and click Add

That’s it. The connector appears in the Connectors panel of every claude.ai chat — toggle it on per-conversation.

The URL contains your API key. Treat it like a password: don’t paste in screen recordings, don’t commit it to git, rotate via the dashboard if it leaks.

If you need to wire it manually instead of using the dashboard helper, the URL shape is:

https://dashboard.reventlov.ai/api/mcp?key=sk_YOUR_KEY&company_id=co_YOUR_COMPANY

Leave the OAuth Client ID / Secret fields empty in claude.ai — we authenticate via the URL key for now (proper OAuth is on the roadmap).

Install in Claude Code

$claude mcp add reventlov \
>  --scope user \
>  --env REVENTLOV_API_KEY=sk_xxx \
>  --env REVENTLOV_DEFAULT_COMPANY_ID=co_xxx \
>  -- npx -y @reventlovmcp/mcp

Verify in any Claude Code session:

/mcp

You should see reventlov listed with all fourteen tools.

Install in Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS; similar path on Windows/Linux):

1{
2  "mcpServers": {
3    "reventlov": {
4      "command": "npx",
5      "args": ["-y", "@reventlovmcp/mcp"],
6      "env": {
7        "REVENTLOV_API_KEY": "sk_xxx",
8        "REVENTLOV_DEFAULT_COMPANY_ID": "co_xxx"
9      }
10    }
11  }
12}

Restart Claude Desktop. Tools appear under the 🛠 icon.

Use it from your own agent

If your agent runs on a model that speaks MCP natively (Claude, plus a growing list of others), give it the same config and it calls log_action directly after every step. The Console tab in your dashboard then has a live audit trail without writing a bridge.

Self-hosted Reventlov

Point the MCP at your own host:

REVENTLOV_API_BASE=https://your-reventlov.example.com

Default is https://dashboard.reventlov.ai.

Security

API keys can read and write the data on your account. Treat REVENTLOV_API_KEY like a password:

  • Don’t commit it to git.
  • Rotate via Dashboard → Settings → API keys if it leaks.
  • Use one key per machine (so you can rotate independently).

The MCP server runs entirely on your machine — no telemetry. Outbound traffic only goes to your REVENTLOV_API_BASE.

Versioning

The MCP follows SemVer. Breaking changes to the underlying Reventlov API are pinned via the X-Reventlov-API-Version header so a previously installed MCP keeps working when the API evolves.

Source

@reventlovmcp/mcp is open source under the MIT license.