Developer · Remote MCP server
OpenClaw Direct
Deploy, monitor, and manage your OpenClaw AI assistants via natural language.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
direct.openclaw/mcp- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-03-12
- Updated
- 2026-03-12
- Publisher
- direct.openclaw
- Namespace
- Namespace verified by the MCP Registry via the domain openclaw.direct · how
- Website
- openclaw.direct/openclaw-mcp-integration
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://openclaw.direct/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect OpenClaw Direct
OpenClaw Direct is a remote MCP server: there is nothing to install. Its endpoint is https://openclaw.direct/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| openchronicle-mcpMemory database for LLM agents - persistent semantic + keyword memory, project namespacing, served o. | Local · stdio |
| OpenClaw Agent Instruction RegistrySearch and retrieve agent instruction files: system prompts, skills, workflows, and safety filters. | Local · stdio |
| OpenClaw Consensus9-LLM consensus + disagreement scoring + cheapest-route picks to fight hallucinations. | Local · stdio |
| Openclaw Control MCPMCP server bridging Claude Code to the OpenClaw gateway management plane via JSON-RPC. | Local · stdio |
| OpenClaw FinOpsVerified cloud cost forecasting for AI agents. AWS, GCP, Azure pricing matrix. | Remote · HTTPLive check: sign-in required |
| Openclaw Health MCPMCP server for OpenClaw deployment health: gateway, resources, errors, skills, upgrades, disk. | Local · stdio |
| opencode subagentsRun Claude Code subagents on cheaper opencode models (DeepSeek, opencode Go) with native parity. | Local · stdio |
| Opencode WorkbenchProvision an OpenCode workbench and MCP stack on any Linux box, local or over SSH. | Remote & Local · HTTP, stdioLive check: ✓ handshake |