MCP Server

The Endpoint

One public endpoint, no session to manage. Point any MCP client at it and start asking.

https://mcp.webanion.com/mcp

• Transport: Streamable HTTP, JSON-RPC 2.0 over POST, stateless
• Authentication: None to start. Sign in once from your client, or send a free API key as a bearer header, and the full catalogue opens.
• Discovery: A machine-readable description of the server lives at /.well-known/mcp.json

claude mcp add --transport http webanion https://mcp.webanion.com/mcp
claude mcp login webanion

The first line adds the server, the second runs the sign-in from the shell. Or, in a session, open /mcp, pick webanion and choose Authenticate. A browser tab opens, you give your name and email, a six digit code arrives by email within a minute, you enter it and approve. That is the whole sign-in.

Claude Desktop and claude.ai

Add the endpoint URL as a custom connector and connect from the connector's settings. The same sign-in runs in the browser.

Cursor

Add the endpoint URL as a remote MCP server. Cursor reads the server's metadata and offers the login itself.

https://mcp.webanion.com/mcp

ChatGPT adds remote MCP servers as connectors: open Settings, then Connectors, enable developer mode, choose Add custom connector and paste the endpoint URL.

Approving lets the client read the full portfolio, the timeline, the blog and the people, and send Monir a message or subscribe to the newsletter as you. You can end it from the client at any time, with claude mcp logout webanion or Clear authentication in /mcp, and Monir can from his side.

No browser to open? Use the API key route instead.

Available anonymously

Signed in, or with an API key

Example prompts

Once the server is connected, ask in plain language and the assistant picks the tools.

How to register

1. Call request_access with your name and email address.
2. A six digit code arrives at that address within a minute.
3. Call verify_access with the email and the code. The key is shown once, so store it.
4. Send the key as an Authorization: Bearer header on every request, and reconnect your client so the header takes effect.

Copy, paste, done. Replace <key> with the key verify_access returned, or drop the Authorization header entirely to browse anonymously.

claude mcp add --transport http webanion https://mcp.webanion.com/mcp --header "Authorization: Bearer <key>"

{
  "mcpServers": {
    "webanion": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.webanion.com/mcp",
        "--header",
        "Authorization:${WEBANION_AUTH}"
      ],
      "env": { "WEBANION_AUTH": "Bearer <key>" }
    }
  }
}

{
  "mcpServers": {
    "webanion": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.webanion.com/mcp",
        "--header",
        "Authorization:${WEBANION_AUTH}"
      ],
      "env": { "WEBANION_AUTH": "Bearer <key>" }
    }
  }
}

Claude Desktop and Cursor speak stdio, so the small mcp-remote proxy bridges them to the HTTP endpoint.

A connection opened without the header keeps going without it. After configuring the key, reconnect the client, in Claude Code /mcp and reconnect, or the key changes nothing and every gated call keeps asking you to register.

• Reads: 120 per minute
• Writes: 5 per minute, and at most five contact messages per day
• Key requests: 3 per hour per email address, 10 per hour per network

A blown limit answers with a retry time, never a silent failure.