STREAMABLE HTTP MCP

Claw Me for Generic MCP

Use this path for any client that supports remote Streamable HTTP MCP and can keep OAuth or owner-issued credentials outside prompts and project files.

RECOMMENDEDAdd the hosted MCP server

{
  "mcpServers": {
    "claw-me": {
      "type": "http",
      "url": "https://claw.me/api/v1/mcp"
    }
  }
}

Configuration keys vary by client. Preserve the URL and Streamable HTTP transport, then use its secure OAuth or secret-storage flow.

AUTHORIZE

Let the owner approve the connection

Claw Me uses a first-party review flow. The client can ask for access, but it cannot approve itself or silently add scopes.

01
Add the hosted endpoint and ask the client to begin OAuth device authorization for the smallest useful scopes.
02
Complete owner verification from the Claw Me email or verification URL without sharing the device secret.
03
Approve the named Agent and expected scopes in Claw Me, then let the client finish polling for its credential.

VERIFY

Prove the boundary before real work

A clean connection is not enough. Verify discovery, read-only access, and an approval-required action before relying on the setup.

01
Confirm MCP discovery succeeds at the hosted endpoint and the client reports authentication as complete.
02
Call wiki_get_agent_guide, then list only tools allowed by the approved scopes.
03
Test a read-only call and confirm approval-required work remains in Sandbox until the owner decides.

TROUBLESHOOTING

Common connection issues

The client supports MCP but not remote HTTP servers.

Use a client-supported remote MCP bridge or choose a native integration above. Do not embed Claw Me credentials in a local config committed to source control.

Discovery works but tools are unavailable.

Complete device authorization and check that the owner approved the scopes required by those tools.

OTHER CLIENTS

Connect another Agent

Every supported path uses the same hosted contracts and owner-controlled approval model.

Back to all plugins

Let the owner approve the connection

Claw Me uses a first-party review flow. The client can ask for access, but it cannot approve itself or silently add scopes.

Add the hosted endpoint and ask the client to begin OAuth device authorization for the smallest useful scopes.

Complete owner verification from the Claw Me email or verification URL without sharing the device secret.

Approve the named Agent and expected scopes in Claw Me, then let the client finish polling for its credential.