Skip to content

Connect your agent

Validated against app ae3b0ef2 and Collector 0.9.0 (54621da), 11 November 2026. This page as Markdown

Give your agent one URL and approve the connection in your browser. From then on it can read how the people of your Teams want to be asked, and your own profile.

  • You signed in to https://app.humanload.eu at least once (Quickstart, step 1).
  • Your agent runs in a client that speaks MCP, the protocol an agent uses to call the tools of a service.
  • You have a browser on the same computer, to approve the connection.

A profile is not required. Without one, the agent connects and receives {"status":"none"} for your own profile.

  • URL: https://app.humanload.eu/api/humans/mcp
  • Transport: HTTP
  • Sign-in: OAuth 2.1, in your browser. There is no key or token to copy.
  • Name used on this page: humans

This server is the Team MCP: it serves the profiles that the people of your Teams chose to share. A Team (Équipe in the French interface) is the group of people who share the same team view. MCP tools lists its six tools.

Status: seen working against a local copy of the server. On 10 November 2026, Claude Code 2.1.319 loaded the server’s instructions and called resolve_person, then get_profile, on a copy of the server running on the developer’s computer. Its sign-in was seen six times on the same local port. A run against app.humanload.eu is not recorded in the repository.

  1. In a terminal, run:

    Terminal window
    claude mcp add --transport http --scope user humans https://app.humanload.eu/api/humans/mcp

    --scope user adds the server for all your projects on this computer.

  2. In Claude Code, type /mcp, choose humans, and sign in. From a terminal, claude mcp login humans does the same.

  3. In the browser page that opens, check the Teams under Teams it may read, then choose Allow. What the consent page asks explains each box.

You should see the agent under Connected now, on the page Connect your agent of the app (https://app.humanload.eu/me/connect). It is also under Connected agents at https://app.humanload.eu/me/account.

Status: not checked yet. The server accepts the way Codex identifies itself; no sign-in from Codex was seen working.

  1. In a terminal, run:

    Terminal window
    codex mcp add humans --url https://app.humanload.eu/api/humans/mcp
    codex mcp login humans
  2. In the browser page that opens, check the Teams under Teams it may read, then choose Allow.

The app’s guide records that Codex uses a new local port at each sign-in. Each sign-in then leaves one more entry under Connected agents; each entry ends within 30 days, and you can disconnect it there.

Status: not checked yet. This path needs no terminal. The app says the same: “This path is not confirmed end to end in this beta yet; the Claude Code one is.”

  1. In claude.ai or Claude Desktop, open the settings, then the connectors, and choose “Add custom connector”.
  2. Give it a name, for example Humanload, and paste https://app.humanload.eu/api/humans/mcp.
  3. Keep “Sign in now” and Claude’s published identity. Add no header, and do not choose automatic registration.
  4. In the browser page that opens, check the Teams under Teams it may read, then choose Allow.
  5. Turn the connector on in the conversation where you need it: connectors are switched on per conversation.

On a Claude Team or Enterprise plan, an Owner of that plan adds the connector once, then each member connects.

  • Claude Desktop set up for a third-party cloud: it registers in a way this server refuses.
  • Claude in Slack: one administrator connects for everyone, and this server works for one person at a time.

The page is titled Connect an agent to Humanload. It shows, in this order:

  1. The name of the app that asks, and the domain that publishes its description.
  2. Where the access goes. For an app on your computer it says: “Access goes to an app on this computer. Continue only if you just started the connection from it.”
  3. Teams it may read: each of your Teams, already ticked. Untick a Team the agent must not read. The agent reads the preferences your colleagues chose to share with the ticked Teams, never their Counts. With no Team ticked, every lookup of a colleague returns {"status":"none"}, and the agent reaches your own profile only.
  4. Save or delete my profile (How to ask me): a separate box. It is ticked when the client asks to write, or states nothing. Untick it unless you want your agent to write your profile.
  5. Allow or Deny.

The connection lasts 30 days at most. After that, the agent asks again.

Say this to your agent:

Read my Humanload profile and tell me how I want to be asked.

You should see one of two answers:

  • the lines of your profile, such as Open with the decision you need from the recipient.;
  • that you have no profile yet. The tool then answered {"status":"none"}.

Both prove the connection. To set up a profile through this agent, say “Set up my Humanload profile” and describe, in your own words, how you want to be asked: How to ask me says what the agent is told to do with that.

Then check the read in the app. Open Connect your agent in the app (https://app.humanload.eu/me/connect). Under Check that it works, the page says “Your agent last read your profile on”, then the date and the time, in UTC. “Reload this page to check again.” is the line below it. When you have no profile, the page says there is nothing to read yet.

The server answers with an HTTP status. Your client usually turns it into a message.

Status What it means What to do
401 No valid access: first call, access expired, agent disconnected, or the 30 days are over. Start the sign-in again from your agent.
403 insufficient_scope: the agent called put_my_profile or delete_my_profile, and Save or delete my profile (How to ask me) was not ticked. Let the agent ask again and tick the box, or keep it read-only.
404 The Team MCP is switched off on the service. Nothing on your side. Tell the person who invited you.
429 Too many calls in one minute. Wait 60 seconds, then try again.

A tool can also answer inside a successful call:

Answer What it means
{"status":"none"} Nothing to serve. The answer does not tell apart three cases: no profile, a private profile, and a Team the agent may not read. The agent writes as it would without a profile.
Invalid arguments. The agent sent arguments the tool does not accept. The answer never repeats them.
Internal error. The service failed. Try again later.

Open https://app.humanload.eu/me/account, find the agent under Connected agents, and choose Disconnect. Its next call is refused. Remove everything covers the rest.