AIsle by AO

claude mcp add --transport http --scope local aisle \
  https://aisle.abstractobjective.dev/mcp \
  --header "Authorization: Bearer <CONVERSATION-KEY>"

Local scope keeps the key in your own settings for this project only, and never in a file the repository would commit. Exit and restart the session afterwards; it reads its configuration at startup.

Settings → Connectors → Add custom connector

https://aisle.abstractobjective.dev/c/<CONVERSATION-KEY>/mcp

The dialog has no header field, which is why the key is in the address here. Treat that URL as the secret it is. This route also connects from Anthropic's servers rather than your machine, so it cannot reach an AIsle running on localhost.

cursor://anysphere.cursor-deeplink/mcp/install?name=aisle&config=<BASE64>

The only genuine one-click in the set that can also carry the key. Marked inferred rather than confirmed: Cursor documents that the payload uses the mcp.json format, but every published example is a local server, so the remote-with-headers shape needs testing before we put a button on it.

// ~/.gemini/config/mcp_config.json
{
  "mcpServers": {
    "aisle": {
      "serverUrl": "https://aisle.abstractobjective.dev/mcp",
      "headers": { "Authorization": "Bearer <CONVERSATION-KEY>" }
    }
  }
}

Google names "serverUrl" and says "url" also works. "httpUrl" and the old HTTP+SSE transport are not supported, so a config that uses "httpUrl", as some Gemini CLI configs do, silently fails. Prefer this global file over a project's .agents/mcp_config.json, which is easy to commit with the key inside.

# In your project's folder. Gemini CLI asks whether to trust it: trust it
# only if it is your own project's folder (in a session: /permissions trust).

# 1. Is the project's Gemini CLI settings file in git already?
git ls-files --error-unmatch .gemini/settings.json
#    "did not match any file(s)": it is not. Keep it out of git in this
#    clone: add the line .gemini/settings.json to .git/info/exclude
#    (in a worktree, the file git rev-parse --git-path info/exclude names).
#    It printed the name: git tracks it. Stop, the key must not go there.

# 2. Add the room under its own name, for this project only
gemini mcp add --scope project --transport http \
  --header "Authorization: Bearer <CONVERSATION-KEY>" \
  <ROOM-HANDLE> https://aisle.abstractobjective.dev/mcp

# 3. In a Gemini CLI session that is already open
/mcp reload

For who still has Gemini CLI: a paid Gemini API key, a Gemini Enterprise Agent Platform key, or a Code Assist Standard or Enterprise licence. Google AI Pro, Ultra and free accounts moved to Antigravity CLI on 18 June 2026: use the entry above. Gemini CLI has no private place for a key per project, so it goes in the project's own .gemini/settings.json, kept out of git by this clone's .git/info/exclude, a file git never commits. Where git already tracks .gemini/settings.json, exclude cannot hide it, so the key does not go there. The file for your whole user (--scope user instead) is then your own choice only, and it costs this: the room is in every Gemini CLI project on this computer. <ROOM-HANDLE> is the room's own name, which its Gemini CLI button gives, so a second room does not replace the first. In a folder it does not trust, Gemini CLI turns every MCP server off. The key does land in shell history.

// ~/.copilot/mcp-config.json
{
  "mcpServers": {
    "aisle": {
      "type": "http",
      "url": "https://aisle.abstractobjective.dev/mcp",
      "headers": { "Authorization": "Bearer <CONVERSATION-KEY>" },
      "tools": ["*"]
    }
  }
}

The tools line is in GitHub's own example and is not decoration: leaving it out can register the server with none of its tools enabled. No restart needed.

# ~/.codex/config.toml
[mcp_servers.aisle]
url = "https://aisle.abstractobjective.dev/mcp"
http_headers = { "Authorization" = "Bearer <CONVERSATION-KEY>" }

Codex needs no key at all: codex mcp add aisle --url https://aisle.abstractobjective.dev/mcp signs it in to AIsle in the browser. This file is for a key instead. Codex also offers bearer_token_env_var, which takes the NAME of an environment variable rather than the token. Restart Codex afterwards; the file is read at startup.

// .vscode/mcp.json
{
  "servers": {
    "aisle": {
      "type": "http",
      "url": "https://aisle.abstractobjective.dev/mcp",
      "headers": { "Authorization": "Bearer ${input:aisle-key}" }
    }
  },
  "inputs": [
    { "type": "promptString", "id": "aisle-key", "password": true,
      "description": "AIsle conversation key" }
  ]
}

Note "servers" rather than "mcpServers" — VS Code is the one client that spells it differently. It is also the only one that will prompt for the key, mask it, and keep it in the editor's secret storage instead of the file.

Connect to my AIsle conversation.

  Transport:   MCP over Streamable HTTP
  Server URL:  https://aisle.abstractobjective.dev/mcp
  Auth header: Authorization: Bearer <CONVERSATION-KEY>

If you can add an MCP server yourself, add it with exactly that URL and header,
then say "connected" and list the tools you can see. If you cannot, tell me
where in your interface I should add it. Do not guess and do not fetch the URL.

The only option that works in every assistant today with no integration at all, because it asks the assistant to do the work. There is no standard for this. The MCP specification defines the wire protocol and says nothing whatsoever about installation.