OpenClaw Setup

shield-check

This guide sets up Leadovaro as an MCP gateway for OpenClaw, giving you controlled access to cloud services with server-side token management and instant revocation.

Why This Approach

No browser automation for OAuth — OAuth flows happen through Leadovaro off-host, no credential exposure on your machine
Server-side token management — OAuth tokens stored in Leadovaro, never exposed to OpenClaw; all API calls proxied through MCP gateway
Lower token usage — More efficient than browser automation, reducing AI processing costs
Explicit MCP server authorization — You control which cloud services (Gmail, Calendar, etc.) OpenClaw can access via Leadovaro
OAuth scope enforcement — Least-privilege by default (e.g., read-only); OpenClaw must request elevation for write operations
Instant revocation — Terminate API access immediately without reconfiguring OpenClaw (revoke authorization or delete toolkit)
Centralized MCP gateway — Manage all cloud service access from Leadovaro dashboard
30-day token expiration — Leadovaro access tokens automatically expire, requiring periodic re-authorization

info

This approach secures OpenClaw's cloud API integrations via the MCP protocol. OpenClaw may have additional local capabilities outside Leadovaro scope. See "What This Setup Secures" below for critical security information.

What This Setup Secures (and What It Doesn't)

✅ What Leadovaro Controls

OAuth token management — Tokens issued and stored server-side in Leadovaro, never exposed to OpenClaw
MCP server authorization — You authorize MCP servers (e.g., "Gmail", "Google Calendar") that OpenClaw can access
OAuth scope enforcement — Least-privilege OAuth scopes (e.g., read-only Gmail initially) enforced at protocol level
API request/response logging — Complete audit trail of every tool call: tool name, parameters, response, and timestamp. Queryable via Leadovaro Chat (aggregated summary, line-by-line detail, or CSV export up to 5,000 lines). Retained ~30 days.
Guardrails at protocol layer — Block requests that violate configured rules (e.g., block write operations, size limits)
Instant token revocation — Terminate cloud API access immediately by revoking authorizations or deleting toolkit

❌ What Leadovaro Does NOT Control

Local file system access — OpenClaw can read/write files on the host machine without Leadovaro visibility
Terminal/shell commands — OpenClaw can execute system commands directly on the host
Network scanning tools — Capabilities like nmap, port scanning happen outside MCP protocol
Headless browser actions — Web automation that bypasses MCP gateway entirely
OpenClaw's other Skills — Any non-MCP capabilities OpenClaw has installed
Actions outside the MCP protocol — Leadovaro guardrails operate at the tool level within the Hub, but OpenClaw's local capabilities (file system, terminal) are outside Leadovaro's visibility
Self-installation of MCP servers — Unless restricted to a specific toolkit, OpenClaw can add MCP servers without user approval

triangle-exclamation

🚨 CRITICAL SECURITY WARNING

NEVER log into Leadovaro on the same machine where OpenClaw is running.

If you are logged into Leadovaro on the OpenClaw host machine, OpenClaw could potentially open your browser and perform authentication on your behalf, granting itself unauthorized access.

Safe Setup:

✅ Configure and authorize Leadovaro toolkit on a different machine
✅ Use OpenClaw on a separate machine that is NOT logged into Leadovaro
✅ Authorize OpenClaw's requests via links sent to your email or accessed on another device

Your Security Responsibilities

When using OpenClaw with Leadovaro, you must also:

Restrict OpenClaw to a specific Leadovaro toolkit — Prevents OpenClaw from self-installing MCP servers
Review and configure OAuth scopes — Start with least-privilege (read-only) and approve elevation requests
Set up guardrails — Configure parameter presets and constraints within each MCP server's settings
Monitor token expiration — Leadovaro tokens expire after 30 days; you'll need to re-authorize
Disable unsafe OpenClaw Skills — Turn off terminal access, network tools, file system access if not needed
Configure OS-level security — Set file permissions, firewall rules, sandboxing on OpenClaw host
Monitor OpenClaw's local logs — Local activity is not visible to Leadovaro

info

Leadovaro secures the cloud API layer via MCP protocol. OpenClaw's local capabilities and the security of the host machine remain your responsibility. For production use with sensitive data, implement comprehensive system-level hardening.

Install the Leadovaro Skill

For the best experience, install the official Leadovaro skill from ClawHub:

clawhub install leadovarotechuser/openclaw-leadovaro-skill

Or visit the skill page directly and download the .zip file to give to your agent:

Leadovaro Skill

Install the official Leadovaro skill for OpenClaw

This skill teaches OpenClaw how to connect to Leadovaro and use your configured MCP tools.

Quick Setup

The fastest way to get started is using our pre-configured OpenClaw toolkit prompt.

1
Open the setup prompt in Leadovaro (on a DIFFERENT machine)
triangle-exclamation
Perform this step on a different machine than the one running OpenClaw.
Visit the OpenClaw toolkit configuration:
OpenClaw Quick Setup
Launch the pre-configured OpenClaw toolkit in Leadovaro
This creates a toolkit with Gmail and Google Calendar in safety mode (read-only by default).
2
Authorize the services
Follow the prompts to authorize Gmail and Calendar access. You'll be redirected to Google to grant permissions with least-privilege OAuth scopes.
3
Copy your MCP URL and token
After setup, Leadovaro provides:
- MCP Gateway URL — safe to share (not secret)
- Access Token — keep this private (expires after 30 days)
Copy both values.

Configure OpenClaw (on the OpenClaw host machine)

Add the credentials to your OpenClaw environment. Create or edit ~/.openclaw/workspace/.env:

LEADOVARO_URL="/_sites/app.leadovaro.com/hub/mcp?accountId=YOUR_ACCOUNT_ID&profile=openclaw"
LEADOVARO_TOKEN="your-access-token"

Or configure via ~/.openclaw/openclaw.json:

{
  "skills": {
    "entries": {
      "leadovaro-mcp-bridge": {
        "enabled": true,
        "env": {
          "LEADOVARO_URL": "your-mcp-url",
          "LEADOVARO_TOKEN": "your-access-token"
        }
      }
    }
  }
}

5
Verify the connection
In OpenClaw, ask:
List the MCP tools I have access to
You should see Gmail and Calendar tools listed.

What's Included in Safety Mode

The quick setup configures these defaults with least-privilege OAuth scopes:

Service	Allowed	Blocked
Gmail	Read emails, search, create drafts	Send emails
Calendar	View events, check availability	Create, modify, delete events

Why safety mode?

Safety mode uses least-privilege OAuth scopes while you're getting familiar with the integration. When OpenClaw needs elevated permissions (e.g., to send an email), it will send you an authorization link. You can approve elevation requests as needed or enable full access by modifying the toolkit's OAuth scopes in Leadovaro.

Manual Setup

If you prefer to configure everything yourself or want different permissions:

1
Create a Leadovaro account (on a separate machine)
triangle-exclamation
Use a different machine than where OpenClaw runs.
Go to app.leadovaro.com and sign in.
2
Create a new toolkit
1. Click Create Toolkit
2. Name it (e.g., "openclaw" or "my-assistant")
3. Switch to this toolkit for the following steps
3
Add MCP servers
Add the MCP servers you want OpenClaw to access:
- Gmail (gmail) — email access
- Google Calendar (calendar) — calendar access
- Google Drive (google-drive) — file access
- PostgreSQL (postgresql) — database queries
- See all 85 available servers
info
Leadovaro authorizes OAuth connections at the MCP server level (e.g., "Gmail"). Use guardrails to control access at the individual tool level within each server.
4
Configure OAuth scopes
For each MCP server, configure the OAuth scopes:
- Start with least-privilege (read-only) scopes
- When OpenClaw needs elevated permissions, it will request approval via a link
- Approve elevation requests only when necessary and expected
5
Configure guardrails (optional)
Set up guardrails within each MCP server's settings:
- Use parameter presets to create hard limits the LLM cannot override
- Example: Limit Slack MCP server to only write to a specific channel
- Note: Guardrails apply per-MCP-server and cannot span across services
6
Generate your access token
In your Leadovaro profile settings, generate a private access token.
lock
Never share this token or paste it into chat. Store it securely. Token expires after 30 days.
7
Configure OpenClaw (on the OpenClaw host)
Add credentials to ~/.openclaw/workspace/.env:
LEADOVARO_URL="your-mcp-gateway-url" LEADOVARO_TOKEN="your-access-token"

Authorization Flow

When OpenClaw tries to use a service or needs elevated permissions:

1
OpenClaw requests access
Ask OpenClaw something like:
Check any meetings I have tomorrow
2
Leadovaro validates the request
Leadovaro checks:
- Is the MCP server authorized in this toolkit?
- Does the OAuth scope allow this operation?
- Do any guardrails block this request?
3
Approve if needed (on a different device)
If authorization or elevation is needed, OpenClaw provides a link. Open it on a different device (not the OpenClaw host) and approve.
4
Confirm completion
Return to OpenClaw and say:
Done
OpenClaw now has access to that service with the approved scope.

Managing Access

You stay in control at all times.

View active permissions

In Leadovaro, go to Authorizations to see all active MCP server connections and their OAuth scopes.

Revoke access

Click Revoke on any authorization to immediately disable access. Revocation is instant — OpenClaw loses API access immediately.

Why This Approach​

What This Setup Secures (and What It Doesn't)​

✅ What Leadovaro Controls​

❌ What Leadovaro Does NOT Control​

Your Security Responsibilities​

Install the Leadovaro Skill​

Quick Setup​

What's Included in Safety Mode​

Manual Setup​

Authorization Flow​

Managing Access​

View active permissions​

Revoke access​

Delete toolkit