ppl resources · Client guides

Use ppl with Cursor

Add ppl to Cursor with a personal MCP configuration and use relationship notes without mixing them into your project files.

Updated October 10, 2026 · ppl team

Your contacts should not disappear when you switch projects. A personal ppl connection gives Cursor access to the relationship record you keep, so it can help you prepare for a meeting or remember a follow-up alongside your other work.

Add the hosted server

Open your personal ~/.cursor/mcp.json configuration. Merge this entry into the existing mcpServers object; do not replace other servers you already use.

{
  "mcpServers": {
    "ppl": {
      "url": "https://withppl.com/mcp"
    }
  }
}

Cursor supports remote HTTP MCP servers and OAuth authorization. Open the MCP controls in Cursor, connect ppl, and follow the browser prompt to sign in and approve permissions. The personal file applies across projects; .cursor/mcp.json is the project-specific alternative. See Cursor’s MCP configuration documentation for its current controls.

Make the first request a read

Use ppl to find the contact I am meeting today. Ask me for their name
if you need it, and ask me to choose between matching contacts.
Summarize their recent notes without editing anything.

This checks three things that matter: Cursor is actually using ppl, it reaches the account you intended, and it can identify the person before acting. You should be able to recognize the notes in your account. If not, stop and check which account was approved.

Keep relationship details out of the repository

Use ppl to store the follow-up, rather than adding a contact’s personal details to a source file. If Cursor suggests writing a meeting summary into your project, review whether that belongs there. You can ask for a conversation-only summary and a separately reviewed ppl note.

We discussed sending a portfolio next Friday. Show me a proposed ppl
note and follow-up task. Ask which Friday I mean before setting a date.
Do not create a file or send anything to the contact.

Fix common configuration problems

If the server is missing, check the JSON syntax and whether you edited the personal file or a different project’s file. If it appears but has no usable tools, check authentication and your organization’s MCP restrictions. A project configuration with the same server name can override the personal one. Keep bearer tokens out of committed configuration files; the OAuth flow avoids having to put a token in this entry.

Read the daily routine for requests you can reuse across clients. You can remove the Cursor entry when you stop using it, and revoke its account access in ppl’s Settings > API.