Skip to main content
With peeps connected to Cursor, your AI coding assistant can look up team members, stakeholders, or contacts without you ever leaving your editor. Ask about the right person to CC on a pull request, find a vendor’s technical contact, or surface account owners — all from the same chat panel where you write and review code.

​
Prerequisites

  • A peeps API key (see Step 1 below)
  • Cursor installed
  • Node.js 18 or later

​
Setup

1

Get your API key

Log in to app.peeps.ai, navigate to Settings → API Keys, and create a new key. Copy it — you’ll paste it into the config file in Step 3.
2

Open Cursor MCP settings

You can configure MCP servers in Cursor in two ways:
  • Via Cursor Settings: Open Cursor Settings → Features → MCP and use the UI to add a new server.
  • Via config file: Create (or open) .cursor/mcp.json in your project root. This is the recommended approach for project-level config you want to commit or share with your team.
3

Add the peeps server configuration

Add the following to your .cursor/mcp.json, replacing your-api-key-here with your actual key. If the file already has an mcpServers block, add the "peeps" entry inside it.
.cursor/mcp.json
4

Reload Cursor

Open the Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows/Linux) and run Developer: Reload Window, or fully quit and relaunch Cursor.
5

Test the connection

Open Cursor’s AI chat and ask:
“Who are the engineering leads at our main client?”
Cursor’s AI will call the peeps MCP server and return matching results. If nothing comes back, verify that your API key is correct and that Node.js 18+ is on your PATH.

​
Global vs. project-level configuration

The .cursor/mcp.json file in your project root configures peeps for that project only. To make peeps available across all your Cursor projects, place the same config in your global Cursor settings file instead — accessible via Cursor Settings → Features → MCP. Use project-level config when you want to scope peeps access to a specific codebase or share the config with teammates through version control.
Avoid committing your raw API key to version control. Consider using an environment variable reference or a secrets manager, and add .cursor/mcp.json to your .gitignore if it contains credentials.

​
Example use cases while coding

  • “Find the team contact for our API vendor so I know who to reach out to about rate limits.”
  • “Who should I CC on this PR for the billing integration?”
  • “Look up the account owner for Acme Corp in peeps.”
  • “Show me the contact details for the DevRel lead at our primary partner.”
  • “Which people in my peeps workspace work at the company we’re building this integration for?”
Add a peeps search instruction to your Cursor rules (.cursorrules or the Rules for AI setting) so Cursor automatically uses peeps when you mention a person or company. For example: "When I mention a person or organization, use the peeps MCP tools to look them up."