Set up an agent

This page gives each AI client the shortest path to adding this server. Nothing on it has to be typed out by hand.

The server address is https://mcp.oneagentharness.com/mcp Copy

Personal MCP address

Your own MCP address, shown on Set up an agent. An AI client connected to it works with the accounts you connected yourself.

Team address

A team's own MCP address, shown under each of your teams below. An AI client connected to it works under that team's settings and approval rules, still through your own connected accounts.

A team's address is on the Organisations page: open the organisation, then the team.

Claude

Last live test

2026-10-01

Last certified on release

v22

claude.ai, Claude Desktop and Cowork

1. Open Customize, then Connectors.
2. Choose "+", then "Add custom connector".
3. Paste https://mcp.oneagentharness.com/mcp Copy
4. Choose Add, then Connect, and sign in.

The connector still has to be enabled in a Cowork session before it is used there.

On Team and Enterprise plans, members cannot add a custom connector themselves. An owner adds it for the organisation under Organization settings, then Connectors. Members then find it under Customize, then Connectors, and press Connect.

Claude Code

One command adds the server for your user, so every project you open can reach it.

claude mcp add -s user --transport http onemcp https://mcp.oneagentharness.com/mcp

Copy

Then run /mcp in a Claude Code session to sign in.

To give a repository the same server instead, write it into that repository's .mcp.json:

{
  "mcpServers": {
    "onemcp": {
      "type": "http",
      "url": "https://mcp.oneagentharness.com/mcp"
    }
  }
}

Copy

Committing that file is enough: cloning the repository brings the server with it, and Claude Code picks it up from the file.

An agent handed this page's address, https://mcp.oneagentharness.com/setup, can read it and run the add command itself.

ChatGPT

Last live test

2026-10-01

Last certified on release

v22

Write tools through ChatGPT are confirmed by a live test.

1. Open Settings, then Apps, then Advanced settings, and turn on Developer mode. In a workspace, an admin may have to allow Developer mode first.
2. Go back to Settings, then Apps, and choose Create.
3. Enter a name, paste https://mcp.oneagentharness.com/mcp Copy as the server URL, and set Authentication to OAuth.
4. Confirm that you trust the app, choose Create, then sign in.
5. In a chat, turn the app on from the "+" menu, under More.

Workspace admins and owners can publish the app for everyone under Workspace settings, then Apps.

Not certified

The clients below work with a generic MCP configuration, but they are not certified. We do not test them on every release, and help with them is best effort.

Hermes

Add the server to ~/.hermes/config.yaml, under mcp_servers:

mcp_servers:
  onemcp:
    url: "https://mcp.oneagentharness.com/mcp"
    auth: oauth

Copy

Then sign in from a new terminal, not from inside a running Hermes session:

hermes mcp login onemcp

Copy

Run /reload-mcp in a chat, or restart Hermes, to pick the server up.

Other clients

Clients that read an MCP JSON file, such as Cursor, take an entry like this one. Key names vary by client: VS Code, for example, reads servers instead of mcpServers. Check your client's documentation.

{
  "mcpServers": {
    "onemcp": {
      "url": "https://mcp.oneagentharness.com/mcp"
    }
  }
}

Copy

A client that only speaks stdio can reach the server through mcp-remote:

{
  "mcpServers": {
    "onemcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.oneagentharness.com/mcp"
      ]
    }
  }
}

Copy

Whatever the client, it must support OAuth 2.1 with dynamic client registration and PKCE, because that is how you sign in to this server.

Signing in

You sign in with a Microsoft work or school account. You are admitted through an invitation from your organisation, through your organisation's subscription, or because the operator has allowed your domain.

What we store is described in the privacy statement, and the conditions you are agreeing to are in the terms of use.

For Microsoft 365 administrators

A tenant administrator can approve this application once for the whole organisation, so that people are not each asked for consent when they connect.

The approval is tenant-wide: it applies to every user in your organisation, and it lets the application ask for these permissions on behalf of each person who signs in and connects:

• openid
• profile
• email
• offline_access
• https://graph.microsoft.com/Tasks.Read
• https://graph.microsoft.com/Tasks.ReadWrite
• https://graph.microsoft.com/Mail.Read
• https://graph.microsoft.com/Mail.ReadWrite
• https://graph.microsoft.com/Mail.Send
• https://graph.microsoft.com/User.Read
• https://graph.microsoft.com/Sites.Read.All
• https://graph.microsoft.com/Sites.ReadWrite.All
• https://graph.microsoft.com/Files.Read
• https://graph.microsoft.com/Files.ReadWrite
• https://graph.microsoft.com/Calendars.Read
• https://graph.microsoft.com/Calendars.ReadWrite

Some of these permissions allow writes. They are used only for the accounts on which a person turns Write on themselves.

Until publisher verification is complete, Microsoft may show this application as unverified on the approval screen.

Approve for my organisation