Home API and integrations | Keys, endpoints and webhooks How to connect the Cloud Humans MCP Server to Claude

How to connect the Cloud Humans MCP Server to Claude

Last updated on Oct 02, 2026

The most up-to-date documentation for the Cloud Humans APIs is at docs.cloudhumans.com/api-reference. If this article and the reference differ, the reference prevails.

When to use

  • You want to manage your knowledge base content directly from Claude — list, create and edit without leaving the conversation
  • You want to stop maintaining the same knowledge base in several places
  • You use another MCP client (Claude Code, Cursor, VS Code) and want to connect it to Cloud Humans

The Cloud Humans MCP Server is in Beta. The content management features are already available, and new ones are being added. If something does not work as expected, contact your Cloud Humans support team.

Prerequisites

  • An active Cloud Humans account — the connector login uses the same email and password you already use on the platform
  • An MCP client that supports custom connectors (in Claude, this depends on your plan)
  • No token or API key needs to be generated, requested from Cloud Humans or pasted anywhere — authorization happens on the login screen

About this article

The Cloud Humans MCP Server is the address that gives your AI assistant access to the Cloud Humans tools. Once connected, you talk to Claude as usual and it can view and change your content in Cloud Humans.

The server address is:

https://mcp.cloudhumans.com/openapi/cloudhumans/mcp

This address is not a page to open in the browser. If you paste this URL into the address bar, you will see the message {"detail":"missing_token"}.

This is expected and is not an error: it does not mean you lack permission, nor that you need a token. The address only works when it is added as a connector inside your AI client, which is what the steps below explain.

This article covers connecting your AI assistant to Cloud Humans. If you are looking for the opposite path — connecting ClaudIA agents to external MCP servers —, see How to configure MCP servers for ClaudIA agents.

Step by step

Step 1 — Open the connector settings

  1. In Claude, open Settings

  2. Go to the Connectors section

Step 2 — Add it as a custom connector

  1. Click Add custom connector

It must be a custom connector. Cloud Humans does not appear in the list of ready-made connectors — if you look for it there, you will not find it.

  1. In Name, type something you will recognize later (for example, Cloud Humans)

  2. In URL, paste the server address:

https://mcp.cloudhumans.com/openapi/cloudhumans/mcp
  1. Confirm to add it

Step 3 — Log in and authorize

  1. Click Connect on the connector you just created

  2. A Cloud Humans login screen will open, asking for email and password

  3. Sign in with your Cloud Humans account — the same one you use on the platform

  4. After logging in, the browser automatically returns to Claude and the connector shows as connected

You have about 10 minutes to complete the login after clicking Connect. If it takes longer than that, the screen expires — just click Connect again and start over.

Step 4 — Test it

Go back to a conversation and ask for something simple, such as:

List the content in my knowledge base on Cloud Humans.

If Claude replies with your content, everything is working.

If your login has access to more than one account or project in Cloud Humans, say in the conversation which one you want to use. Otherwise, the assistant has no way to guess which one to act on and will ask you to specify.

Notes

  • The connection lasts 30 days and is renewed automatically while you use it. After that period, Claude asks you to log in again — just repeat Step 3.

  • Changing your password or losing access to your account ends the connection immediately. This is the expected behavior: whoever loses access to the platform also loses access through the connector.

  • Permissions are exactly those of your account. The connector neither expands nor reduces what you could already see and edit in Cloud Humans, and each person who connects uses their own account.

  • It works with other MCP clients. The address and the login flow are the same in any client that supports remote MCP servers with login — the only thing that changes is where the option to add the connector is located.

  • If the login screen does not open and you keep seeing {"detail":"missing_token"}, the address was almost always opened in the browser instead of being added as a custom connector. Redo Step 2.