Operational access lives in MCP · REST · SDK
REMOTE MCP · AGENT-FIRST ACCESS

One endpoint. Your agent does the rest.

Sign in as the owner, select Connect Agent, then add the Streamable HTTP endpoint to the compatible MCP client you already use.

Use your configured Normic origin.

Use your deployed Normic MCP URL. Never commit NORMIC_MCP_TOKEN, paste it into logs, or expose it in browser code.

Production MCP requires an OAuth access token from your configured issuer. API credentials are for REST/SDK; they are not a substitute for a production MCP access token.

CLIENT

Claude Code

Register the remote endpoint, then run /mcp inside Claude Code to authorize with the configured issuer.

claude mcp add --transport http normic https://normic.tech/mcp
CLIENT

Hermes

Add this to ~/.hermes/config.yaml. Set NORMIC_MCP_TOKEN to a current issuer access token in production, or an API credential locally. Arrange refresh through your issuer; environment-backed headers do not refresh themselves.

mcp_servers:
  normic:
    url: "https://normic.tech/mcp"
    headers:
      Authorization: "Bearer ${NORMIC_MCP_TOKEN}"
CLIENT

OpenClaw

Use the documented OAuth login flow after the operator has configured the issuer and its client registration policy.

openclaw mcp add normic --url https://normic.tech/mcp --transport streamable-http --auth oauth
openclaw mcp login normic
openclaw mcp doctor normic --probe
CLIENT

Generic MCP client

Use normal MCP discovery after OAuth authorization. Normic publishes descriptive tool names, schemas, and capability metadata; no separate skill file is required.

Transport: Streamable HTTP
Endpoint: https://normic.tech/mcp
Authentication: OAuth 2.1
Discovery: tools/list

Authentication contract

  1. 1
    Prepare the connection

    Sign in to the Owner Console and select Connect Agent. Normic atomically prepares or reuses the internal identity, scoped credential, and trusted OAuth grant.

  2. 2
    Authorize from your client

    Add https://normic.tech/mcp to your MCP client. The owner approves authorization, while Normic supplies the safe scope set from trusted server-side state.

  3. 3
    Discover and operate

    The client uses standard MCP discovery to obtain available tools and schemas. Owners can revoke the connection immediately from the Owner Console.

Configuration references: Claude Code · Hermes · OpenClaw. Syntax verified against official documentation; individual client runtimes are not bundled with Normic.