Skip to content
openclaw-os
MCP

MCP servers cleanly scoped.

Model Context Protocol connects OpenClaw to your tools — Notion, Drive, CRM, GitHub and more. But only with clean scopes.

The problem

Why this matters right now.

MCP servers are often configured too generously: a Drive MCP with read/write on everything is a trust question nobody answered consciously. Without scoping, a single skill bug becomes a data disaster.

Our approach

Here's how we do it.

We install MCP servers per tool, scope permissions minimally, document auth paths and ship a per-server off-switch.

What's included

The full package.

NT

Notion MCP

Read/write on explicitly chosen workspaces or pages — never the whole workspace.

DR

Drive MCP

Google Drive or OneDrive: only selected folders, with file-level OAuth scopes.

CR

CRM MCP

HubSpot, Pipedrive, Salesforce: read on contacts and deals, write only via custom skill with approval.

GH

GitHub MCP

Repo read, issue write, PR review — own scopes per repo, never org-wide write.

DB

Database MCP

Postgres, MySQL, BigQuery: read-only on specific schemas, never raw SQL without skill sandbox.

OF

Off-switch

Per MCP server: one switch that cleanly disconnects it — for incidents or audits.

How it works

From first call to a productive OpenClaw workflow.

  1. 01

    Analyse

    30-min check + process map. We pinpoint the 3 workflows where OpenClaw saves time fastest, and which channels are mandatory.

  2. 02

    Setup

    Daemon, channels, skills, MCP, allowlists, requireMention, Tailscale and the live dashboard configured cleanly and live.

  3. 03

    Training

    Your team works on real tasks: WhatsApp inbox triage, weekly Slack-DM reports, voice-memo-to-CRM, skill maintenance.

  4. 04

    Operations

    calver updates, skill extensions, channel care, security reviews, backups and an emergency off-switch — so OpenClaw doesn't fade out.

Packages

Three entry points. One outcome: OpenClaw that works.

All packages & add-ons →

Starter

For small teams and 2–3 workflows on one channel

€1,850 one-time

+ from €180 / month maintenance & care

  • OpenClaw daemon installed, hardened, monitorable (launchd/systemd)
  • 1 messaging channel (WhatsApp, Telegram, Slack or iMessage) cleanly paired
  • 2–3 productive skills (inbox triage, research or reporting)
  • 2 MCP tool integrations (e.g. Drive, Notion, Slack, CRM, calendar)
  • Allowlists, requireMention, GDPR defaults and backup plan
  • 2-hour intensive training + 30 days of care
Book a check

Enterprise

For sensitive data, compliance and fleet rollout

from €14,900 one-time

+ from €1,290 / month maintenance & care

  • Enterprise setup with central config, fleet auth and audit trail
  • Custom MCP server or internal tool adapters incl. code review
  • 10+ skills, departmental playbooks, train-the-trainer programme
  • Voice, canvas, Tailscale, backup and SIEM integration
  • Governance documentation for ISMS, GDPR and ISO 27001
  • Monthly security and optimisation reviews
Book a check
Frequent questions

Still open questions?

Write us at hello@openclaw-os.com or book a call directly. We'll take the time.

What is MCP exactly?
Model Context Protocol — an open standard from Anthropic that OpenClaw adopted. Defines how agents call tools: function description, auth, inputs, outputs.
Do we need a server per tool?
Standard tools have ready MCP servers (Notion, Drive, GitHub, Slack). For proprietary internal tools we build custom MCP servers — see Add-ons.
Is MCP safe?
If scoped correctly: yes. If carelessly configured (e.g. Drive read/write all): no. That's exactly why this service exists.
What does a complete OpenClaw setup cost?
Starter starts at €1,850, Business at €5,900 and Enterprise from €14,900. Ongoing maintenance starts at €180/month. LLM costs (OpenAI, Anthropic, local models) run separately.
Is OpenClaw only useful for engineers?
No. That's the whole point of openclaw-os.com: OpenClaw becomes a work assistant for inbox, offers, reports, meetings, research, knowledge and routines — over the channels your team already uses (WhatsApp, Slack, Telegram, iMessage, voice).
Which channels make sense?
We usually start with the channel your team already lives in: WhatsApp and Telegram for external comms, Slack/Teams internally, iMessage on macOS, Discord for communities. The multi-channel strategy follows reality, not technology.
Next step

Book a call.
30 minutes that pay off.

Pick a slot — we confirm automatically and send you the Google Meet link.

Intro call · 30 min · free

Pick a slot that works.

No commitment. We review your OpenClaw use cases, surface three productive levers, and send a short recap afterwards.

Booking loads only after your click

Clicking the button loads the Cal.com calendar. Data may be transmitted to Cal.com at that point.

Open on Cal.com

The site works fine without Cal.com. Booking is a separate, voluntary feature.

Powered by Cal.com · The calendar loads only after your action. Trouble? Write to hello@openclaw-os.com.

This site only uses technically necessary features. Analytics loads only after consent. Cal.com booking loads only when you actively open it.