Docs

Connect your agent.

One server URL, browser sign-in, and a token only if your client needs one.

The server

Name
motif
URL
https://mcp.asv-labs.com/mcp
Transport
Streamable HTTP
Sign-in
OAuth 2.1 in the browser (discovered automatically), or an agent token

Signing in from an agent creates a free Motif account if you don't have one. With browser sign-in, no token appears in any command or config file.

Pick your client

Commands follow each client's documentation as of September 2026 and match the connect page in your account. Grok and other clients that support remote MCP servers with OAuth: use the settings under Other. The status next to each client says how far we've tested it ourselves.

Claude Code

Partly verified

In a terminal:

claude mcp add --transport http --scope user motif https://mcp.asv-labs.com/mcp

Or paste this to your agent:

Add the Motif MCP server for me by running: claude mcp add --transport http --scope user motif https://mcp.asv-labs.com/mcp — then tell me to run /mcp so I can sign in.

Then run /mcp in Claude Code, pick motif and choose Authenticate. A browser tab opens so you can sign in to Motif.

Checked against the live server: Claude Code detects Motif's browser sign-in. A full end-to-end workflow check is in progress.

Claude app

Not yet verified end to end
  1. Open Claude (web, desktop or mobile) → Settings → Connectors.
  2. Select Add custom connector.
  3. Name it Motif and paste https://mcp.asv-labs.com/mcp
  4. Select Add, then Connect, and sign in to Motif.

Turn Motif on in a chat from the tools menu, then ask Claude to use it.

ChatGPT

Not yet verified end to end
  1. Settings → Security and login → turn on Developer mode.
  2. Open Plugins (chatgpt.com/plugins) and select +.
  3. Name it Motif. Under Connection, paste https://mcp.asv-labs.com/mcp
  4. Choose OAuth, select Create, then sign in to Motif.

Developer mode is available on Plus, Pro, Business, Enterprise and Edu, on the web.

Grok

Not yet verified end to end
  1. Open grok.com/connectors and select New Connector, then Custom.
  2. Name it Motif and paste https://mcp.asv-labs.com/mcp
  3. Complete the sign-in when Grok asks, and sign in to Motif.

Grok discovers Motif's tools and offers them in chats. Using the xAI API instead? Add Motif as a remote MCP tool with server_url set to this address and an agent token in the authorization field (see the token section below).

Cursor

Not yet verified end to end

Or in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "motif": {
      "url": "https://mcp.asv-labs.com/mcp"
    }
  }
}

Cursor shows Motif under Settings → MCP with a Connect button. Select it and sign in.

VS Code

Not yet verified end to end

In a terminal:

code --add-mcp '{"name":"motif","type":"http","url":"https://mcp.asv-labs.com/mcp"}'

Start the server from the MCP view or when Copilot agent mode asks, then sign in.

Codex CLI

Not yet verified end to end

In a terminal:

codex mcp add motif --url https://mcp.asv-labs.com/mcp && codex mcp login motif

Or paste this to your agent:

Add the Motif MCP server by running: codex mcp add motif --url https://mcp.asv-labs.com/mcp — then run: codex mcp login motif

codex mcp login opens a browser tab so you can sign in to Motif.

Gemini CLI

Not yet verified end to end

In a terminal:

gemini mcp add --transport http motif https://mcp.asv-labs.com/mcp

Or paste this to your agent:

Add the Motif MCP server by running: gemini mcp add --transport http motif https://mcp.asv-labs.com/mcp — then tell me to run /mcp auth motif.

Then run /mcp auth motif inside Gemini CLI and sign in.

Windsurf

Not yet verified end to end

Or in ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "motif": {
      "serverUrl": "https://mcp.asv-labs.com/mcp"
    }
  }
}

Refresh MCP servers in Windsurf's Cascade panel and sign in when asked.

Devin

Not yet verified end to end
  1. In the Devin web app open Customize → MCPs and select Add custom MCP.
  2. Name it Motif, choose HTTP (Streamable HTTP) and paste https://mcp.asv-labs.com/mcp
  3. Set Authentication to OAuth, save, then select Connect and sign in to Motif.
  4. Select Test tools to confirm Devin can list Motif's tools.

Choose Personal access so each teammate signs in with their own Motif account.

Hermes Agent

Not yet verified end to end

In a terminal:

hermes mcp login motif

Or in ~/.hermes/config.yaml:

mcp_servers:
  motif:
    url: "https://mcp.asv-labs.com/mcp"
    auth: oauth

hermes mcp login opens a browser tab so you can sign in to Motif. In a running session, /reload-mcp picks up the change; hermes mcp test motif checks it.

OpenClaw

Not yet verified end to end

In a terminal:

openclaw mcp add motif --url https://mcp.asv-labs.com/mcp --transport streamable-http

Then sign in to Motif through OpenClaw's Settings → MCP (OAuth). openclaw mcp doctor motif --probe lists the tools it can see.

Other

Not yet verified end to end
  1. Server URL: https://mcp.asv-labs.com/mcp
  2. Transport: Streamable HTTP
  3. Sign-in: OAuth 2.1 (the client discovers it automatically), or an agent token from the section below

Any client that supports remote MCP servers with OAuth works without a token.

What happens when you sign in

  1. Your client finds Motif's sign-in details at https://mcp.asv-labs.com/mcp and opens a browser tab.
  2. You sign in to Motif with a one-time email code and see which client is asking and what it will be able to do.
  3. You approve; the client receives its own credentials. You can see every connected app, and disconnect it, under your account.

Agent tokens (scripts, CI, header-only clients)

Create a token on your account's Connect page. It's shown once. Keep it in an environment variable called MOTIF_TOKEN, never in a file you commit. Tokens count against the same account-wide allowances as everything else, and a revoked token stops working within 60 seconds.

Claude Code with a token

claude mcp add-json --scope project motif '{"type":"http","url":"https://mcp.asv-labs.com/mcp","headers":{"Authorization":"Bearer ${MOTIF_TOKEN}"}}'

Writes .mcp.json with ${MOTIF_TOKEN}; Claude Code reads the variable at start-up.

Codex CLI with a token

codex mcp add motif --url https://mcp.asv-labs.com/mcp --bearer-token-env-var MOTIF_TOKEN

Codex reads MOTIF_TOKEN from your environment on every request.

Cursor (mcp.json) with a token

{
  "mcpServers": {
    "motif": {
      "url": "https://mcp.asv-labs.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MOTIF_TOKEN}"
      }
    }
  }
}

Cursor substitutes ${env:MOTIF_TOKEN} when it starts the server.

Scripts and CI with a token

curl -s https://mcp.asv-labs.com/mcp -H "Authorization: Bearer $MOTIF_TOKEN" -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Store MOTIF_TOKEN as a CI secret.

Troubleshooting

The agent says Motif "needs authentication" or returns 401.
Run the client's sign-in step again (for example /mcp in Claude Code, codex mcp login motif, /mcp auth motif in Gemini CLI). A token that was revoked or has expired also gives 401; create a new one.
How do I check the connection without using my allowance?
Ask the agent to call get_usage. It shows your plan, each allowance and its reset time, and never counts against them. From a script, tools/list with your token (the Scripts and CI command above) should list the live tools.
"Too many requests" or a limit reached.
The error says which limit and when to retry (retry_after_seconds). Monthly allowances reset at the time get_usage shows. Nothing is ever charged for going over.
A premium guide says "plan required".
Free accounts get the free subset. The error includes a link to upgrade; your agent can keep using free guides and checks.
The tools don't appear after adding the server.
Restart the client or refresh its MCP list, and make sure the URL ends in /mcp. Then check service status.