MCP server

Give Claude Code, Cursor or any MCP client the Search People and Enrich Person tools.

Social Search is also an MCP server, so an agent can find people and enrich them without writing API calls. It has two tools:

Tool	Does the same as
search_people	Search People: a description to professional profiles or Reddit accounts, with profile and evidence links
enrich_person	Enrich Person: a LinkedIn address to the professional profile and matched socials, or a Reddit profile URL to its public profile and activity

Each tool call spends credits from your workspace and shows on the Usage page, exactly like the API call it matches. Its result’s usage has the credits it cost and credits_remaining, the workspace’s credits left after it, so an agent can see its balance.

MCP results omit picture_url fields to keep the agent’s context smaller. The REST API still returns them, and the dashboard preview still displays profile photos.

Connect

The server is at https://www.constants.io/people-search/mcp (Streamable HTTP). Your agent signs in with your Constants account over OAuth, so no key goes into its config: the first time it connects, a browser window asks you to sign in and approve the connection. Its calls spend your default workspace’s credits.

Claude Code

claude mcp add --scope user --transport http constants-people-search \
  https://www.constants.io/people-search/mcp
claude mcp login constants-people-search

claude mcp login opens your browser to sign in to Constants. An agent setting this up for you should run it too, rather than leave sign-in for later. If your browser doesn’t open, run /mcp in Claude Code, choose constants-people-search and sign in there. Start a new session if the tools don’t show.

Cursor and others

Add this to ~/.cursor/mcp.json, or your client’s MCP config, and sign in when your client asks:

{
  "mcpServers": {
    "constants-people-search": {
      "url": "https://www.constants.io/people-search/mcp"
    }
  }
}

With an API key

For clients that can’t sign in, such as scripts or CI, send an API key as Authorization: Bearer <key> instead. A key bills its own workspace.

claude mcp add --scope user --transport http constants-people-search \
  https://www.constants.io/people-search/mcp \
  --header "Authorization: Bearer $CONSTANTS_API_KEY"

The key goes into your agent’s config in plain text. Use a key made for the agent, and delete it under API Keys if it leaks.

You can also open MCP in the dashboard’s sidebar and copy set-up text to paste into your agent.

Using it

Ask in plain words, such as “find engineering managers at Stripe in Dublin” or “enrich the second one”. The agent calls search_people, then enrich_person with the linkedin_url of the person you mean. For Reddit discovery, ask for something like “Reddit users looking for a cheaper Intercom alternative”. Reddit results include the supporting conversation; pass their profile_url to enrich_person for the account profile, avatar, posts and comments. search_people searches one platform per call. Set platform to linkedin, reddit, x, instagram, tiktok, or facebook; omission enables Auto, which uses an LLM to select one platform, not all platforms. The response includes the selected platform. Facebook searches public posts and reads their comments, with exact supporting quotes; no group URL is needed. Search returns up to 20 posts per query without search pagination, while comments paginate. Facebook profile URLs do not support enrich_person. Instagram returns Reels/comment/reply evidence. TikTok reads transcripts and comments with exact supporting quotes. Auto chooses among LinkedIn, Reddit, X, Instagram, TikTok and Facebook. For multiple platforms, call the tool separately with explicit platforms and separate budgets and result limits. Both tools take the same parameters as their API endpoints, and errors such as running out of credits come back as the API’s message.