Skip to content
Client integrations

Claude Code

Connect PeopleRouter to Claude Code with a remote MCP server.

Configure this client in Quick Start.

You will need Claude Code installed and a PeopleRouter account. This guide uses browser sign-in, so you do not need to paste an API key into a configuration file.

Add the server

In the project where you want to use PeopleRouter, choose either the terminal command or the project configuration.

Developer settings · API Key (optional)

Stored in this browser. It is only inserted into copied examples when you enable the checkbox above.

In your terminal:

claude mcp add --transport http peoplerouter https://mcp.peoplerouter.ai
claude mcp login peoplerouter
Or send this to your agent

Copy these instructions into your agent to help with setup.

paste to your agent
Connect PeopleRouter in Claude Code. Check the installed version first and use this setup:

claude mcp add --transport http peoplerouter https://mcp.peoplerouter.ai
claude mcp login peoplerouter

In your terminal:
Complete browser authorization. If your CLI has no mcp login command, open Claude Code and use /mcp to authenticate peoplerouter.
Or share this project configuration with your team:

When sign-in opens, wait for me to authorize DINQ in the browser. If sandbox restrictions block configuration or authorization through file, network or browser callback access, request the necessary permissions through the current agent's approval mechanism. Where outside-sandbox execution is supported, run the operation only after approval. I will complete browser authorization. Do not repeatedly retry in the same restricted environment, disable the sandbox or bypass approvals. If the environment cannot request permission, give me the exact steps to perform in my local terminal or app UI. Back up existing configuration and merge only peoplerouter, preserving other servers and settings. Check an existing entry instead of adding a duplicate. Web apps require adding the connector in their UI; guide me if you cannot do that directly. Confirm success only after tools load and capabilities succeeds; otherwise report the actual error.

The default scope makes the connection available to you in the current project. See Claude Code's MCP documentation for other installation scopes.

Sign in

This step applies to browser authorization. If you explicitly enabled an API Key in the setup example, see Authentication and API Keys instead.

The terminal example already includes claude mcp login peoplerouter. If you chose the .mcp.json configuration, run:

claude mcp login peoplerouter

Complete browser authorization. If your CLI has no mcp login command, start Claude Code and use its MCP menu to authenticate:

/mcp

Select peoplerouter and follow the authentication prompt. Complete sign-in and authorization in your browser, then return to Claude Code.

Check the connection

Open /mcp again and check that PeopleRouter is connected. Then ask Claude:

Use PeopleRouter to list the available capabilities. Explain which tools
could help me find contributors to a GitHub repository. Do not run a search yet.

This checks tool discovery before you choose a search. If the tools are unavailable, check the server status and finish any pending authorization in /mcp.

Run your first task

Once connected, describe who you need to find. Include a starting point and the evidence you want back. For example:

Find maintainers of https://github.com/vllm-project/vllm.
Before making calls, inspect the relevant tools and their prices.
Return public profile links and explain the evidence for each match.

Review the proposed calls and their prices before continuing. You can inspect subsequent usage in Activity.

If something goes wrong

  • Authentication required: reopen /mcp and complete the sign-in flow.
  • Server missing: run claude mcp list from the same project where you added it.
  • A tool call fails: read the actual error, check inputs against its schema, and check your account or credentials. A failed call does not mean there are no matching people.