All assistants

With a key

Connect Clad9 to Anything else

Your own script, an agent framework, any client that sends a header.

Step by step

  1. Create a connection key below and tick what it may do. It is shown once and never again.

  2. Point your client at this endpoint.

    https://clad9.com/mcp
  3. Send the key on every request in an Authorization header. That is the whole protocol surface — one HTTP endpoint, one header.

    Authorization: Bearer YOUR_CONNECTION_KEY

You'll need a Clad9 account

The key is tied to your closet, so it can only be created from inside Clad9. Log in and come back to this page: the form appears right here.

This is the shape of what you'll paste:

{
  "mcpServers": {
    "clad9": {
      "httpUrl": "https://clad9.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CONNECTION_KEY"
      }
    }
  }
}

You'll know it worked when

A tools/list call comes back with 17 tools. A missing or revoked key answers 401 with a WWW-Authenticate header, never a 500.

Nothing to answer from? An assistant can only use clothes Clad9 knows about, so catalogue your closet first. If it can't connect at all, that's ours to fix: tell us.

Using something else?

What an assistant can and can't do, including what it's never offered, whatever you tick.