Clients

Every client below uses the same address, https://mcp.algomo.com/mcp, and the same sign-in.

ClaudeCopy Anchor Link

1. Open Settings, then Connectors, then Add custom connector.
2. Paste https://mcp.algomo.com/mcp and finish the sign-in.
3. Under the connector, set each tool to Always allow, Needs approval or Blocked. Reads are safe to allow. Leave publish on Needs approval.

ChatGPTCopy Anchor Link

1. Open Settings, then Connectors, and create a connector with the server address.
2. When it asks for an authentication method, choose OAuth and leave the client ID and secret blank. Choosing no authentication connects and then fails at the first tool call.
3. Finish the sign-in.

ChatGPT asks before a tool that writes runs. You can allow a tool for the rest of the conversation.

GrokCopy Anchor Link

1. Open Grok's settings and add a custom connector named Algomo with the address https://mcp.algomo.com/mcp.
2. If it asks for an authentication method, choose OAuth and leave the client ID and secret blank.
3. Finish the sign-in.

Claude CodeCopy Anchor Link

claude mcp add --transport http algomo https://mcp.algomo.com/mcp

Run /mcp inside Claude Code and choose Algomo to sign in.

CodexCopy Anchor Link

codex mcp add algomo --url https://mcp.algomo.com/mcp
codex mcp login algomo

CursorCopy Anchor Link

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json inside a project:

{
  "mcpServers": {
    "algomo": {
      "url": "https://mcp.algomo.com/mcp"
    }
  }
}

Then open Settings, then MCP, and sign in next to algomo.

VS CodeCopy Anchor Link

code --add-mcp '{"name":"algomo","type":"http","url":"https://mcp.algomo.com/mcp"}'

Run MCP: List Servers from the command palette, start algomo, and sign in when prompted.

Gemini CLICopy Anchor Link

Add the server to ~/.gemini/settings.json:

{
  "mcpServers": {
    "algomo": {
      "httpUrl": "https://mcp.algomo.com/mcp"
    }
  }
}

Then run /mcp auth algomo and finish the sign-in in the browser.

Other clientsCopy Anchor Link

Any client that supports remote MCP servers over Streamable HTTP with OAuth connects with the address alone. The server publishes the OAuth metadata clients look for and registers them dynamically, so there is nothing to configure on Algomo's side.

A client that cannot reach remote servers at all can bridge to this one through mcp-remote, run as a local server:

npx -y mcp-remote https://mcp.algomo.com/mcp

One line for a coding agentCopy Anchor Link

An agent that can read a URL and run commands can connect itself:

Connect me to Algomo by following every step in https://mcp.algomo.com/prompt.md

Two workspacesCopy Anchor Link

A connection is scoped to the workspace picked at sign-in. To work on two, add the server twice under different names (for example algomo and algomo-staging) and pick a different workspace for each.

Remove the connectionCopy Anchor Link

Remove the connector in your client. The sign-in it held expires on its own and is not renewed. Sessions the assistant staged stay in the workspace until someone publishes or discards them.