LIVE OBSERVABILITY LAYER

Add a visibility
and control layer
to your Cursor,
Cline, and
OpenClaw.

See every request. Track every cost. Catch sensitive data before it leaves. Connect in minutes. Read it like a spreadsheet. Works for solo developers and teams.

OpenClaw users
You ran it overnight. Find out exactly what it did, what it called, what it sent.
AI coding teams
Cursor, Cline, Claude Code all in one view.
AI agencies
Deliver agents with full audit logs built in.
leanmcp // agent log recording
time
agent
request
model
tokens
status
02:14:33
OpenClaw
reading /projects/api/.env for context...
gpt-4o
3,102
BLOCKED
02:11:17
OpenClaw
deploy this service to production via AWS CLI
claude-4.6
1,847
⚠ REVIEW
14:22:18
Cursor
debug this error: connection refused db:5432
gpt-4o
2,341
⚠ SECRET
14:19:55
Cline
write tests for the user auth module
claude-4.6
3,102
OK
14:17:30
Cursor
AWS_SECRET=AKIAIOSFODNN7EXAMPLE in context
gpt-4o
892
BLOCKED
14:15:02
Cline
refactor the payment processing module
claude-4.6
4,210
OK
14:12:44
OpenClaw
search for all .pem files in home directory
gpt-4o
1,204
⚠ REVIEW
What you get

Visibility. Cost.
Risk. Control.

01 · VISIBILITY

See every request

Every AI call your tools make — what was sent, which model, how many tokens. Plain language, no technical knowledge needed.

02 · COST

Track every cent

Broken down by person, tool, and session. Set limits before the bill surprises you.

03 · RISK

Catch sensitive data

Passwords, tokens, customer data — detected before they leave. Alert sent the moment something is found.

04 · CONTROL

Know who runs what

One view of every person, every tool, every session. Policies, limits, and an audit log you can share.

OpenClaw · 257,000+ GitHub stars · going viral right now

OpenClaw is the fastest-growing AI agent
ever built. It needs a control layer.

OpenClaw runs autonomously — reading files, sending emails, making hundreds of AI calls. It is powerful and it is unsupervised. LeanMCP gives you the log, the cost breakdown, and the alert layer it was never shipped with.

257K+
GitHub stars
12%
of sessions touch credentials
800+
malicious skills found
OpenClaw scenario

OpenClaw ran overnight. What did it send?

Ran for 6 hours, called GPT-4o 847 times, read through your project directory. Did it touch a .env file? Send a database string? Hit an external URL you didn't authorize? No way to find out.

LeanMCP: full per-session trace, file access log, secret detection alerts
OpenClaw scenario

A skill from ClawHub: what is it really doing?

Looked fine in the description. But Cisco found 26% of OpenClaw skills contain vulnerabilities, and some quietly exfiltrate data. No audit trail of what it called or sent.

LeanMCP: per-skill request log, anomaly detection, block on first suspicious call
Cursor / Cline scenario

Your .env file got sent. You didn't know.

Cursor's .cursorignore didn't protect it. Your .env with AWS_SECRET_ACCESS_KEY got included in context and sent to OpenAI's servers. No log, no alert — until the breach.

Detected by LeanMCP: AWS Access Key pattern in request body → alert sent
Team scenario

5 engineers, 5 agents. One bill, no breakdown.

OpenAI bill: $1,200. Which agent? Which engineer? Which session burned $300 in one run? No breakdown, no idea where to start cutting.

LeanMCP shows: cost per agent, per user, per session, per model
How it works

One URL change.
Complete visibility.

Visibility.
Every request.

See exactly what was sent to every AI model — in plain text
Which tool triggered it — OpenClaw, Cursor, Cline, or your own code
How many tokens it used and what it cost
Sensitive data flagged and highlighted inline
Searchable history — find any session, any request
Export to CSV for audits or compliance
LEANMCP // AGENT LOG LIVE
TIME
AGENT
REQUEST
MODEL
TOKENS
STATUS
02:14:33
OpenClaw
reading /projects/api/.env for context...
gpt-4o
3,102
BLOCKED
02:11:17
OpenClaw
deploy this service via AWS CLI
claude-4.6
1,847
⚠ REVIEW
14:22:18
Cursor
debug: connection refused at db:5432
gpt-4o
2,341
⚠ SECRET
14:19:55
Cline
write tests for the user auth module
claude-4.6
3,102
OK
14:17:30
Cursor
AWS_SECRET=AKIAIOSFODNN7EXAMPLE
gpt-4o
892
BLOCKED

Cost.
Down to the agent.

Cost per person — see who spent what, on which tool
Cost per session — know which overnight run cost $28
Compare models — GPT-4o vs GPT-4o-mini across same tasks
Budget alerts via email or Slack at any threshold
Hard limits — block requests when spend hits your ceiling
COST BREAKDOWN — THIS MONTH
── By Agent ────────────────────────── OpenClaw (overnight) 847 calls $28.40 Cursor (alex@) 612 calls $14.20 Cline (sarah@) 203 calls $6.80 ────── Total this month $49.40 ── Budget Alert ────────────────────── Monthly limit: $60.00 Current spend: $49.40 (82%) ⚠ Alert sent via Slack · $50 threshold

Risk.
Know before it leaves.

Detects passwords, API keys, and private tokens in any request
Detects customer emails, phone numbers, credit card numbers
Detects internal files and business data being sent to models
You choose the action — log it, block it, or alert your team
Real-time alerts via email or Slack when something is found
🔑
API Keys & Secrets
AWS Access Keys
GitHub Tokens
OAuth Tokens
Private keys RSA/SSH
🗄️
Database & Infra
Connection strings
DB passwords
Internal URLs
Private IPs
👤
Personal Data
Email addresses
Phone numbers
Credit card numbers
SSNs
🏢
Business Data
Customer data patterns
Financial figures
Internal configs
Trade secrets

Team control.
One view for the whole team.

Per-person view — see what each team member's tools are doing
One shared dashboard — all agents, all spend, all in one place
Team policies — rules that apply to everyone automatically
Anomaly alerts — flag when any agent behaves unusually
Audit log — a record you can export and share when asked
👥
Per-user view
See alex@, sarah@, and dev@ separately. Know who's running which agent and how much it costs per person.
🛡️
Team policies
Set rules once — apply to all agents for all users. Block certain models, require approval for large sessions, limit spend per day.
📋
Audit log
Full exportable history of every request, every agent action, every alert. For your own records or for a customer who asks.
Your data, your rules

We never train
on your data.
You stay in control.

What we log

Request timing, model used, token counts, cost, and status. Your request content is stored in your account only — for your visibility. You set the retention period. Delete anytime.

What we never do

We never train on your data. Never read your content except to run the secret detection you configured. Never share or sell it. Your code stays yours.

You stay in control

Delete your logs from your dashboard anytime. Export everything before deleting. Your data leaves when you say so.

Compatible tools

Works with every AI tool
your team runs today.

Your engineers change one setting in each tool. That's it. Nothing else changes about how they work.

Cursor
Change one setting. Every Cursor request — every tab, every completion — logged immediately.
● Live
Cline
Full request visibility including every file Cline pulled in as context.
● Live
Windsurf
Drop-in via one settings change. Same full observability as Cursor.
● Live
Claude Code
Full agentic session tracing for every Claude Code run.
● Live
Custom agents
Any code that calls an LLM. Works with any OpenAI-compatible client.
● Compatible
OpenAI
● Live
Anthropic
● Live
xAI / Grok
● Live
Fireworks
● Live
ElevenLabs
● Live
Get started

Live in 4 steps.
Under 10 minutes.

01

Sign in and buy credits

Go to app.leanmcp.com. If you're not technical, this is your step — your engineers handle the rest.

02

Engineers connect their tools

Your team changes one setting in Cursor, Cline, or OpenClaw. Takes 2 minutes per person.

03

Open the dashboard

Go to app.leanmcp.com. Requests, costs, and alerts are already there. Read it like a spreadsheet.

04

Know what's happening

See what was sent, what it cost, and whether anything needs attention. Now you have a real answer.

In your OpenClaw config.yaml, set the API base URL to the LeanMCP endpoint:

openai_base_url: https://aigateway.leanmcp.com/v1/openai
openai_api_key: your_leanmcp_api_key

Every OpenClaw session is now fully logged by skill, by model call, and by cost. Full guide: docs.leanmcp.com/ai-gateway/openclaw →
Cursor → Settings → Models → API Base URL → paste https://aigateway.leanmcp.com/v1/openai → enter your LeanMCP key → Save.

Full guide: docs.leanmcp.com/ai-gateway/cursor →
Cline settings → API Provider → Custom → Base URL: https://aigateway.leanmcp.com/v1/openai → API Key: your LeanMCP key.

Full guide: docs.leanmcp.com/ai-gateway/cline →
export ANTHROPIC_BASE_URL=https://aigateway.leanmcp.com/v1/anthropic
export ANTHROPIC_API_KEY=your_leanmcp_api_key

Full guide: docs.leanmcp.com/ai-gateway/claude-code →
Pricing

Try it yourself.
Or set it up
for your team.

Try it yourself
Pro
$29 / month
Connect one or more AI tools. See everything — costs, requests, alerts. Know what's happening within 10 minutes of signing up.
What you get →
Full dashboard — 30-day log history
Cost breakdown by person, tool, and day
Real-time alerts when sensitive data is detected
Budget limits — stop spending before it surprises you
Export logs for audits or compliance
See your first log → app.leanmcp.com
Just want to explore
Credits
Pay as you go
No subscription. Buy a small amount of credits, connect one tool, see your first request. Upgrade when you're ready.
Includes →
Full gateway — all 5 AI providers
7-day basic log view
Sensitive data detection visible in logs
No alerts or team features
Upgrade to Pro anytime
Start with credits → app.leanmcp.com

How credits work: Credits cover the cost of routing your AI requests through our gateway — roughly the same as going direct to OpenAI, plus a tiny extra fee (~0.5%). Most teams spend $2–10/month on credits on top of their existing model costs. The subscription adds the dashboard features. Both are separate and optional to start.

8,000+
developers
<10min
to first log
~$0.05
gateway overhead per 1K requests
“I set it up in 5 minutes. First thing it showed me was that Cline had been sending my entire package.json on every request. I had no idea.”
dev using Cline + LeanMCP
Common questions
What are credits exactly?
Credits pay for token routing through the LeanMCP gateway. When your tools make a request to OpenAI or Anthropic via the gateway, a tiny amount of credits is deducted, roughly equivalent to ~0.5% of the model call cost. Your model provider charges your original API key separately as normal. Credits are just for the gateway routing layer.
Do I need a subscription, or just credits?
Credits alone are enough to use the gateway and see basic logs (7-day history, no alerts). The Pro ($29/mo) and Team ($99/mo) subscriptions add the features that turn logs into action: 30-day history, real-time Slack/email alerts when a secret is detected, budget limits, cost breakdowns, and team controls. Most serious users subscribe once they see their first alert.
Does the subscription replace my API credits?
No. They are separate. Credits pay for routing (small per-request fee). The subscription pays for dashboard features. Both are billed independently. You need credits to use the gateway regardless of whether you have a subscription.
What’s the right amount of credits to start with?
Start small. If you route 1,000 GPT-4o requests through the gateway per day, that’s roughly $0.05/day in gateway credits. Most individual developers spend $2–10/month on credits on top of their model costs.
I have more than 10 team members. What then?
Email us and we’ll set up a custom plan. Teams with 10–50 members are our sweet spot right now. Enterprise pricing and compliance documentation available on request.

Your agents are running right now.
See your first log in under 10 minutes.

app.leanmcp.com · buy credits · change one URL · open dashboard

Go to app.leanmcp.com →