MCP

Clous is MCP-native. Alongside the REST API, the Model Context Protocol server lets AI agents call Clous tools directly, without writing HTTP glue.

Install

npx @clousai/mcp

Add it to an MCP client (Claude Desktop, Claude Code, Cursor, …):

{
  "mcpServers": {
    "clous": {
      "command": "npx",
      "args": ["-y", "@clousai/mcp"],
      "env": { "CLOUS_API_KEY": "clous_live_..." }
    }
  }
}

Hosted endpoint

• MCP server: https://mcp.clous.ai
• Auth: the same Bearer key as REST — Authorization: Bearer clous_live_...
• Envelope: tools return the same { data, page, as_of, source, query_echo, warnings } envelope as the REST API, so what you learn here transfers directly.

Why MCP

• No glue code. An MCP-capable agent discovers Clous tools and their typed parameters automatically.
• Consistent contract. Tool results use the same envelope and the same error codes as REST.
• Source-linked. Every record still carries provenance and freshness, so an agent can cite the underlying filing.

Example agent prompts

An agent connected to Clous (local or mcp.clous.ai) can act on prompts like:

• "List New York investment advisers with over $1B in regulatory AUM and tell me which report private funds."
• "Resolve CRD 105958 to a canonical entity and summarize its Form ADV profile."
• "Find advisers with disciplinary history in California and link each to its source filing."

In the meantime

Use the live REST endpoints — see the Quickstart and the Advisers API Reference. The machine-readable llms.txt index lets agents navigate the API today.