Install

Server URL

Every client needs the same address. Use it exactly as shown.

https://mcp.neoautark.com/api/mcp

The steps below follow the vendors' own documentation as of 15 October 2026. Menu names change over time, and none of the clients has been walked through end to end against neo-mcp for this page.

Claude on the web and desktop

In Claude this is called a custom connector.

1. Open Customize > Connectors.
2. Click + Add, then Add custom connector.
3. Enter the name neo-mcp and paste the server URL from above, then click Continue.
4. Review the detected authentication settings, then click Continue and Add.
5. Click Connect and sign in (see below).
6. In a chat, click + in the lower left, choose Connectors and switch neo-mcp on for that conversation.

On Team and Enterprise plans only an owner can add a custom connector; members then find it under Customize > Connectors and click Connect. Claude reaches the server from Anthropic's cloud, so the server URL must be publicly reachable over HTTPS.

Not verified: whether the desktop app shows exactly the same menu as the web app, and which of the OAuth client options in step 4 is best for neo-mcp. Keep the defaults Claude detects.

Claude Code

Add the server once with this command.

claude mcp add --transport http neo-mcp https://mcp.neoautark.com/api/mcp

Then start Claude Code, run /mcp and follow the steps in your browser to sign in. You can check the result with the command below, which lists each server as connected, needing authentication, or failed.

claude mcp list

By default the server is stored for you in the current project only. Add --scope user to make it available in all projects.

Codex

Codex reads MCP servers from ~/.codex/config.toml. Add a table for the server.

[mcp_servers.neo-mcp]
url = "https://mcp.neoautark.com/api/mcp"

Then sign in from the terminal.

codex mcp login neo-mcp

Not verified: Codex's documentation shows codex mcp add with a --url option only in an example that also sets an OAuth client id, so this page uses the config file instead. Whether Codex can register itself automatically with neo-mcp has not been tested.

What you see on first connect

1. Your client opens a browser window with the neo-mcp login page. Log in, or create an account first.
2. A page titled Connect followed by the client's name shows your workspace and email and lists what the client may do: read accounts, numbers and proposals, and propose changes. Nothing changes until someone approves it. Click Allow.
3. The client returns and the tools are available.

Try this first: ask Claude "What is the status of my workspace?" It calls the status tool and reports the workspace, your role, connected accounts and waiting proposals. If nothing is connected yet, continue with first steps.