Connect a client

First create a token in More → Developer access (see Access tokens) and keep it in an environment variable:

export FELLESLY_TOKEN=fly_...

Replace https://api.fellesly.no with your own API address if you host Fellesly yourself.

Claude Code

claude mcp add --transport http fellesly https://api.fellesly.no/v1/mcp \
  --header "Authorization: Bearer $FELLESLY_TOKEN"

Then run /mcp inside Claude Code to check that fellesly is connected.

Codex

In ~/.codex/config.toml (shared by the Codex CLI and IDE extension):

[mcp_servers.fellesly]
url = "https://api.fellesly.no/v1/mcp"
bearer_token_env_var = "FELLESLY_TOKEN"

Start Codex with FELLESLY_TOKEN set, and use /mcp in the TUI to see the server.

Other clients

Any client that supports Streamable HTTP with a custom header works: point it at /v1/mcp and send Authorization: Bearer <token>. A typical JSON config:

{
  "mcpServers": {
    "fellesly": {
      "type": "http",
      "url": "https://api.fellesly.no/v1/mcp",
      "headers": { "Authorization": "Bearer fly_..." }
    }
  }
}

Clients that only run local (stdio) servers can use a bridge such as mcp-remote:

{
  "mcpServers": {
    "fellesly": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.fellesly.no/v1/mcp",
        "--header",
        "Authorization: Bearer ${FELLESLY_TOKEN}"
      ],
      "env": { "FELLESLY_TOKEN": "fly_..." }
    }
  }
}

Try it with curl

curl -s https://api.fellesly.no/v1/mcp \
  -H "Authorization: Bearer $FELLESLY_TOKEN" -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"today","arguments":{}}}'