For your AI
Client compatibility
Every app that speaks MCP over HTTP gets Hamloy's 13 tools. Claude Code and Codex get more, through the hamloy program. Here is each client side by side.
Updated 11 October 2026
How each one connects
| Client | How it connects | Where it's set up | Signs in through the browser |
|---|---|---|---|
| Claude Code | The program, or the remote link | Per folder, or a .mcp.json in the repo |
Yes |
| Codex | The program, or the remote link | Once for you on the computer | Yes |
| Claude (web, desktop, phone) | Remote link, as a custom connector | Once for your Claude account | Yes |
| ChatGPT (on the web) | Remote link, as a custom MCP server | Once for your ChatGPT account | Yes |
| Cursor | One-click install, or remote link in mcp.json |
Every folder, or per folder | Yes |
| VS Code | One-click install, or remote link in .vscode/mcp.json |
Every folder, or per folder | Yes |
| Windsurf | Remote link in its mcp_config.json |
Once on the computer | Its docs say yes |
| Cline | Remote link over streamable HTTP | In Cline's MCP settings | Its docs say yes in the Cline CLI, and show a token header in the editor |
| Zed | Remote link in its MCP settings | In Zed's settings | Its docs say yes |
| Gemini CLI | Remote link, as httpUrl |
Per project, or for your user | Its docs say yes, with /mcp auth |
| Any other MCP client | Remote link, or an API token | As the client keeps it | If it supports MCP sign-in |
What each one gets
Every client gets the 13 tools. These come on top.
| Client | Hooks | Panel | Status line | Tested by us |
|---|---|---|---|---|
| Claude Code | Yes, with the program | Yes | Yes, opt-in | Yes |
| Codex | Yes, with the program, approved once with /hooks |
Yes | No | Yes |
| Claude (web, desktop, phone) | No | No | No | Yes |
| ChatGPT | No | No | No | Yes |
| Cursor | No | No | No | Yes |
| VS Code | No | No | No | Yes |
| Windsurf | No | No | No | Not yet |
| Cline | No | No | No | Not yet |
| Zed | No | No | No | Not yet |
| Gemini CLI | No | No | No | Not yet |
| Any other MCP client | No | No | No | No |
The other clients' rows were read from their own documentation on 10 October 2026. Windsurf's documentation now lives under the name Devin Desktop.
What each column means
How it connects. The remote link is Hamloy's address,
https://hamloy.com/mcp for every project you're on, or a project's own address
from its page. The program is hamloy, installed with one paste in the folder
you work in; it signs in once and sets up Claude Code and Codex, tools and hooks
together. An API token is for a machine nobody signs in on. See
remote link or token and the program.
Where it's set up. Some clients keep a server per folder, so a folder reaches one project and a file in the repo can carry it to every clone. Others keep one connection for your account; they get the address for every project, and their calls name the project when you're on several.
Signs in through the browser. The client opens Hamloy in your browser the first time, you sign in, and no key is written anywhere (OAuth).
Hooks. The program's hooks tell Hamloy which repo, branch and files the agent touches, and bring the lists' news into the session. With them a session starts knowing what's open and which task to take next, a closed session lets go of its claims at once, an agent is told when it edits a file another session changed, and a task ticked on a branch stays "not merged yet" until its commit reaches main. See git. Without hooks, an agent gets the rules with its first tool reply and the news under each reply after.
Panel. hamloy panel keeps the lists drawn beside the agent in the terminal:
a split in tmux, Zellij, iTerm2, WezTerm, Kitty and Windows Terminal, and a
window beside it in other terminals.
Status line. hamloy statusline on adds a Hamloy line to Claude Code's
status line: the task this session is on, and what waits for you. Codex's status
line takes only its own items, so there is none there.
> Do the streak counter next.
⏺ hamloy - Claim an item (MCP)(key: "B-k3f9")
⎿ B-k3f9@2 claimed by this session
⏺ Writing the streak count for each habit now.
Hamloy ◐ B-k3f9 Streak counter on the… 2 for you · 5 ready
How should a shared streak look?
claude · 2d agoWhich sign-in should Pebble have at launch?
claude · 5d agoEvery client, the same lists
Whatever the client, it's the same 13 tools and the same rules. A task Claude Code holds is refused to Codex, Cursor or ChatGPT, and a question any of them asks waits on your one board:
• Called hamloy.claim({"key":"B-k3f9"})
└ B-k3f9 is claimed by claude since 4m ago; pick another item (B-vaxb is free), message them with the message tool (to: B-k3f9), or pass force to take it over
See all integrations for a page per client, and the tools for what each one does.
Questions
What does "tested by us" mean?
We connect that client to a scratch project ourselves, sign in, and use the tools through it. The others are written from their own documentation, read on 10 October 2026, and we haven't run them ourselves yet.
My client isn't here. Will it work?
If it speaks MCP over HTTP, yes. Give it https://hamloy.com/mcp. If it can't sign in through the browser, send an API token as the Authorization header.
Why do only Claude Code and Codex get hooks?
Hooks are run by the client on your computer, and the hamloy program sets them up for these two. Other clients get the same tools, the rules with their first tool reply, and the news under every reply after.