Setup
Configure Claude Code
Clustr connects two ways. Both register a server namedclustr — pick one.
- Sign in (OAuth)
- API key
Recommended. No API key, no Node.js. Run this in your terminal:Then run
/mcp in Claude Code and choose Authenticate to sign in with Clustr in your browser. The tools appear once you approve access.Other clients (Claude Desktop, ChatGPT, Cursor)
Add Clustr as a custom connector using the HTTP endpoint, then sign in with Clustr:Authorization: Bearer your-api-key header for clients that support custom headers.
Available Tools
Once connected, your AI assistant has access to the following tools:The tool set updates automatically, for every install. OAuth and
custom-connector clients talk to
https://api.clustr-ai.com/mcp directly. The
API-key install (npx -y @clustr-ai/mcp-server) is a stdio bridge to that same
endpoint: it declares no tools of its own and fetches the list from the server
every time a client asks for one, so new tools appear without an npm update.Removed in v1.4.0:
start_competitor_monitoring. A competitor scan now fires on exactly two events — a competitor being added, and the weekly schedule — everywhere, not just in the web app. register_competitor starts the new competitor’s first scan itself and tells you whether it started, so nothing replaces the removed tool. Use list_competitor_runs to see what is running.Owners are a directory, not a seat
An owner is the person accountable for a connector, and therefore for every opportunity that connector produces. In Clustr that is a directory entry scoped to your workspace, not a login, so it does not have to be one of your teammates. An investor, an advisor, a former colleague, or a friend can own an opportunity. That has three consequences worth knowing when you ask an assistant to assign work:- No email is sent. Creating an owner never notifies that person. If you want them to know, tell them yourself.
- No access is granted. An owner cannot sign in, see your network, or read the opportunity. The entry is a label on your data.
- No seat is used. Adding owners does not change your billing, so there is no reason to be sparing with them.
is_member: true, so an assistant can tell the two apart. Deleting an owner never deletes opportunities: every opportunity that person held is simply left with no owner, and delete_owner reports how many so you can reassign them.
Example Prompts
Here are some things you can ask your AI assistant once Clustr is connected:- “Run account research on Salesforce and give me the report link”
- “Find referral opportunities at Stripe”
- “What opportunities do we have through john-doe on LinkedIn?”
- “Show me my top opportunities by confidence score”
- “Give me an overview of my network”
- “Who are my connectors?”
- “Check the status of my last import”
- “Mark opportunity X as Contacted”
- “Assign that Stripe opportunity to sam@northstar.vc, he is our investor, create the owner if needed”
- “Who owns the most opportunities right now?”
- “Add Stripe as a target account”
- “List all our target accounts”
- “Add Globex as a competitor to monitor”
- “Which of my open-deal accounts did competitors touch this week?”
- “Show me every critical signal from Globex’s founders and AEs in the last 30 days”
- “Who at Northwind Trading have our competitors been talking to?”
- “Log that comment to the CRM, then snooze the rest of that thread for a week”
- “Show me the latest competitor report and which accounts are at risk”
Authentication
Clustr’s MCP server supports two auth methods:- OAuth (sign-in) — authorize in your browser; Clustr issues and refreshes tokens automatically. No key to manage. Recommended for Claude Code, Claude Desktop, and ChatGPT.
- API key — the same key as the REST API, set via the
CLUSTR_API_KEYenvironment variable. Best for headless or shared setups.