Put public data inside
Claude or Codex.

1. 1. Open Customize → Connectors.
2. 2. Select + → Add custom connector.
3. 3. Name it Humaps and enter https://api.humaps.org/mcp.
4. 4. Add it, then enable Humaps from the conversation's connector menu.

Claude's hosted custom connectors support authless or OAuth servers. Humaps' free toolset works there today. Account-scoped agentic research currently uses a Bearer API key in clients that support custom headers, such as Claude Code and Codex; the key is never a tool argument.

In Codex settings, add a remote MCP server and paste the endpoint. For config-as-code, add:

[mcp_servers.humaps]
url = "https://api.humaps.org/mcp"

For account-scoped research, create a key in Humaps and keep it in an environment variable:

[mcp_servers.humaps]
url = "https://api.humaps.org/mcp"
bearer_token_env_var = "HUMAPS_API_KEY"

Add the public connector from a terminal:

claude mcp add --transport http humaps https://api.humaps.org/mcp

For authenticated use, Claude Code expands environment variables inside .mcp.json headers:

{
  "mcpServers": {
    "humaps": {
      "type": "http",
      "url": "https://api.humaps.org/mcp",
      "headers": {
        "Authorization": "Bearer ${HUMAPS_API_KEY}"
      }
    }
  }
}

Keep HUMAPS_API_KEY in your environment or secret manager; never paste it into a prompt, commit it, or put it in a URL. Claude Code refuses to parse this configuration if the variable is missing.