ClientSights · Developer documentation
The ClientSights MCP Server
Connect Claude — or any client that speaks the Model Context Protocol — directly to ClientSights. Your assistant gets the same view of your data you have in the product: nothing more, nothing less.
https://app.clientsights.ai/mcpQuick start
Claude (web and desktop)
- Open Settings → Connectors → Add custom connector.
- Paste
https://app.clientsights.ai/mcpand continue. - Sign in with your usual ClientSights single sign-on and approve the connection. That's it — ClientSights's tools appear in your conversations.
Claude Code
claude mcp add --transport http clientsights https://app.clientsights.ai/mcpOther MCP clients
The server speaks stateless Streamable HTTP with OAuth 2.1 authorization (PKCE and dynamic client registration). Clients discover the authorization server automatically via /.well-known/oauth-protected-resource/mcp — no API keys, no manual configuration.
What you can ask
- “Who has been talking to Acme in the last month, and about what?”
- “Summarize our relationship with Jordan at Initech.”
- “Which of my clients have gone quiet recently?”
- “Ask ClientSights: where are our client relationships trending down?”
Under the hood, three kinds of object come back: activity (row-level data), memory (pre-computed synthesis at daily, weekly, and monthly granularity), and observation (observer outputs that distill into memory). The get_insights tool chooses the right granularity for the question so long ranges stay digestible — your assistant does the storytelling from there.
Tools
| Tool | What it does |
|---|---|
| whoami | Who you are: your profile, the accounts you can access, and the limits on this connection. |
| search_companies | Find client companies by name. |
| get_company | One client company in full: the record, its contacts, who on your side talks to them, and the relationship summary. |
| search_persons | Find client contacts by name. |
| get_person | One client contact in full: the record, their affiliations, and the interaction summary. |
| get_insights | The primary tool. Give it companies or contacts and a timeframe; it picks the right level of pre-computed memory (daily, weekly, or monthly) to fit the range and returns them stitched chronologically. |
| get_activities | Raw activity rows anchored to a client company or contact — "who has been talking to Acme". |
| get_memories | Raw client memory rows at an explicit granularity — the pre-computed synthesis get_insights chooses from. |
| get_observations | Observer outputs about your clients for a period. |
| ask_clientsights | Ask ClientSights itself a free-form question through its chat engine and get the completed answer. Supports my-clients and all-clients subjects, and multi-turn conversations. |
Access, security, and limits
- Your permissions, exactly. Every call runs as you: the connection sees only the people, clients, and data your ClientSights account can see. Connections are read-only.
- Multiple accounts. Calls default to your default account; every tool accepts an
account_id, andwhoamilists the accounts you can choose from. - Rate limits. 60 requests per minute per connection, and at most 10 concurrent
ask_*questions. - Audit trail. Every request — including each individual tool call — is logged with your identity and the connected application.
- Revoking access. Disconnect from your AI assistant's connector settings at any time; tokens are no longer honored once revoked.