OpenClaw remote MCP setup

Start by preparing one authorized vault. Hosted MCP requires Premium or higher; credit packs do not grant MCP access.

Configure the client

OpenClaw documents outbound Streamable HTTP MCP and OAuth. Merge a named entry into the existing mcp.servers configuration:

{
  "phasoric": {
    "url": "https://phasoric.com/api/mcp",
    "transport": "streamable-http",
    "auth": "oauth",
    "oauth": { "scope": "mcp:read offline_access" }
  }
}

Run openclaw mcp login phasoric on the owning host and review Phasoric consent. This starts with read access. See the official transport and OAuth reference, checked September 17, 2026.

Verify the actual runtime

Ask the intended agent runtime to list Phasoric vaults and read one project decision with its source path. A saved registry entry alone does not establish tool availability. OpenClaw's default OAuth credentials are operator-shared, so choose the appropriate identity model before exposing a connection to other people.

These settings are inferred from the documented transport/authentication match with Phasoric, not an authenticated OpenClaw interoperability test. Runtime projection and client versions can differ.

Retain the decision deliberately

Phasoric does not capture OpenClaw conversations automatically. Before adding write access, use the shared preview, approval and mapping-permission checks. A client automation setting cannot authorize a Phasoric note change.