Skip to main content
The MCP server is in beta. It is safe to use — it goes through the same permissions as everything else — but tools may change between releases as we refine the surface.
The Cloud Humans MCP server exposes the same curated surface as the public APIs as tools an AI assistant can call. Connect it once and your assistant can work with your Cloud Humans data in plain language — everything in the API reference is available as a tool, and the set grows as the API does.
It speaks the standard Model Context Protocol over Streamable HTTP, so anything that can act as an MCP client can use it: Claude (web and desktop), Claude Code, Cursor, or your own agent.

​
Connecting

There are no API keys to create. The server authenticates with OAuth: the first time your client connects, a browser window opens and you sign in with your regular Cloud Humans credentials — the same email and password you use in the app. Everything the assistant can see and do is bounded by what your user can see and do.
Go to Settings → Connectors → Add custom connector and paste the server URL:
Claude opens the sign-in page. After you approve, the tools appear in every new conversation.

​
Accounts and projects

One login covers the whole platform, and the assistant can only see and do what your user can. If your login has access to more than one account or project, just name the one you mean in conversation (“on the Acme account…”) — or ask the assistant which ones you have, and it will list them.

​
Good to know

  • If a tool reports something missing that you know exists, the assistant probably targeted the wrong account or project — say which one you mean and try again.
  • Sessions expire like any login. If tools start failing after a long idle period, reconnect — most clients re-run the sign-in automatically.

​
MCP or REST?

Same data, same permissions, two doors:
  • MCP when a person with an assistant is doing the work: exploring, reviewing, making judgment calls. Zero code.
  • REST API when a system is doing the work: scheduled syncs, integrations, anything that runs unattended and needs deterministic behavior.
They compose: teams typically prototype a workflow over MCP in conversation, then harden the parts worth automating into REST calls.