Last checked: October 9, 2026

PitchPrfct has an MCP server. MCP (Model Context Protocol) is a standard way for AI assistants like Claude to use other apps. Once you connect it, you can ask Claude to work in your PitchPrfct account in plain English, for example "list my PitchPrfct contacts" or "show me my PitchPrfct campaigns."

The PitchPrfct MCP server turns the PitchPrfct Developer API into tools Claude can use, one tool for each API action. That covers things like listing and creating contacts, sending messages, and managing campaigns and workflows. Claude can only do what your API key allows, and its tool calls count toward the same rate limits as your other API requests.

This guide covers three ways to connect:

Option A: Claude on the web or the Claude desktop app (a "custom connector"). Best for most people.
Option B: Claude Code (Claude's command-line tool). Use this if Option A isn't available to you yet, or if you already use Claude Code.
Option C: The Claude desktop app's config file (uses a small free bridge called mcp-remote). Use this if you use the Claude desktop app and Option A isn't available to you yet.

Coming soon: PitchPrfct's API docs say a "Sign in with PitchPrfct" option for Claude.ai connectors is on the way. Once it's live, you'll be able to add the connector without pasting an API key or setting headers. Until then, use one of the options below.

Before you start

You'll need:

A PitchPrfct account ready for the Developer API. The API Keys and MCP tabs appear once your account has a verified phone number, an active subscription, and a 10DLC campaign at least at the pending-review stage. Until then, the Developer API page only shows OAuth Apps. Team members cannot create or change API keys.
A Claude account.
- For Option A: any Claude plan (Free, Pro, Max, Team, or Enterprise). The Free plan can add only one custom connector. On Team and Enterprise plans, only an Owner (or, on Enterprise, someone with a role that can manage libraries) can add a custom connector for the organization.
- For Option A you also need the Request headers option in Claude's "Add custom connector" dialog. Anthropic says this option is in beta and only available to some organizations right now. If you don't see it, use Option B or Option C.
- For Option B: a paid Claude plan that includes Claude Code (Pro, Max, Team, or Enterprise), or an Anthropic Console account, plus Claude Code installed on your computer.
- For Option C: the Claude desktop app for macOS or Windows, plus Node.js 18 or later installed on your computer.
A PitchPrfct API key. Step 1 below shows you how to create one.

Here are the connection details you'll use:

MCP server URL: https://app.pitchprfct.com/api/mcp
Transport: Streamable HTTP
How it signs in: API key, sent in a header named x-api-key. (Developers whose app connects through PitchPrfct OAuth Integrations can send an OAuth access token as Authorization: Bearer instead. You don't need this for the steps below.)

Step 1: Create a PitchPrfct API key

Log in to PitchPrfct at https://app.pitchprfct.com.
Open the Developer API page. You can go straight to https://app.pitchprfct.com/app/developers, or click Settings at the bottom left of the sidebar, then select Developer API.
You'll see four tabs: API Keys, MCP, Webhooks, and OAuth Apps. The API Keys tab opens first. If you haven't made a key before, it says No API keys yet.
Click Create API key. A Create API key window opens that says "Name the key and pick what it may do."
In Name, type a name between 4 and 30 characters, such as Claude, so you'll know later what the key is for.
Under Access, choose one:
- Full access (selected by default): "Anything this account can do, including capabilities added later."
- Custom (our recommendation): "Choose exactly what this key is allowed to do." You'll see 34 permissions in four groups: Contacts, Messaging, Campaigns & Workflows, and Account Management. Tick at least one.
Tip: start with read-only permissions like Read Contacts, Read Conversations, and Read Campaigns. You can always make a new key with more permissions later.
Click Create API key. (Click Cancel if you change your mind.)
Copy your key right away and store it somewhere safe, like a password manager. You'll paste it in the next step.

Good to know: the MCP tab on the same page (heading MCP Server) has ready-made setup snippets for Claude Code, Codex CLI, Cursor, and Gemini CLI, each with a Copy button. As the page says, you "replace YOUR_API_KEY with a key from the API Keys tab. Create a key here and we put it in the snippet for you." Cursor users also get a one-click install from that tab right after creating a key. If you'll use Claude Code (Option B below), the Claude Code tab there gives you the exact command to copy.

Option A: Add PitchPrfct as a custom connector (Claude web or desktop app)

If you're on a Free, Pro, or Max plan

In Claude, go to Customize > Connectors.
Click + Add, then Add custom connector.
Enter a name, such as PitchPrfct.
For the remote MCP server URL, enter:
```
https://app.pitchprfct.com/api/mcp
```
Click Continue.
Claude shows the authentication settings it detected. Click Continue.
Under Authentication, choose No sign-in. (PitchPrfct uses an API key, not a sign-in screen.)
Open Request headers:
- For the header name, select x-api-key from the list.
- For the value, paste your PitchPrfct API key exactly as you copied it. Don't add "Bearer" or anything else in front of it.
- Mark the header as Required.
Click Add.

Note: Anthropic is rolling out a new version of this dialog gradually. If yours shows the name, URL, and Advanced settings on a single screen with only OAuth fields and no Request headers section, your account doesn't have header support yet. Use Option B or Option C for now.

If you're on a Team or Enterprise plan

An Owner adds the connector once for the whole organization:

Go to Organization settings > Connectors.
Click Add, hover over Custom, then select Web.
Follow steps 3 to 8 from the section above.

Then each member:

Goes to Customize > Connectors.
Finds PitchPrfct (it usually has a "Custom" label).
Clicks Connect.

Important for teams: with a header-based API key, everyone in your Claude organization who uses this connector reaches PitchPrfct with that same key. Use a key with only the permissions your team members should have.

Turn it on in a chat

Click the + button at the bottom left of the chat box, select Connectors, and make sure PitchPrfct is switched on.

Option B: Connect with Claude Code

Install Claude Code and sign in (see Anthropic's Claude Code docs).
In PitchPrfct, open the Developer API page (https://app.pitchprfct.com/app/developers), select the MCP tab, then select the Claude Code tab and click Copy. The command looks like this:
```
claude mcp add --transport http pitchprfct https://app.pitchprfct.com/api/mcp --header "x-api-key: YOUR_API_KEY"
```
Replace YOUR_API_KEY with your key. Or click Create API key on the MCP tab, and PitchPrfct puts the new key in the command for you.
Paste the command into your terminal and press Enter. You should see an "Added" message.
- Optional: add --scope user before pitchprfct to make PitchPrfct available in all your projects, not just the current folder.
Check the connection:
```
claude mcp list
```
PitchPrfct should show Connected. Inside Claude Code you can also type /mcp to see its status and tools.

Option C: Connect the Claude desktop app with its config file

If Option A isn't available to you yet, the Claude desktop app can still reach PitchPrfct through mcp-remote, a small bridge that runs on your computer and passes your API key along. This is the Claude Desktop setup from PitchPrfct's API docs.

Install Node.js 18 or later from https://nodejs.org. The bridge runs through npx, which comes with Node.js.
Open Claude Desktop's config file:
- Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json

Paste this in. If the file already has an "mcpServers" section, add just the "pitchprfct" part inside it.

{
  "mcpServers": {
    "pitchprfct": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.pitchprfct.com/api/mcp",
        "--header",
        "x-api-key:${PITCHPRFCT_API_KEY}"
      ],
      "env": {
        "PITCHPRFCT_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with your PitchPrfct key. Keep the quotation marks, and leave the ${PITCHPRFCT_API_KEY} line exactly as it is.
Save the file, then quit Claude Desktop completely and open it again.
In a new chat, ask Claude to "list your PitchPrfct tools."

Check that it works

Start a new chat (or a new Claude Code session) and try:

"List my PitchPrfct contacts."

Then try:

"Show me my PitchPrfct campaigns."

The first time Claude uses a PitchPrfct tool, it asks for your permission. Review what it plans to do, then allow it. If Claude replies with your real contacts or campaigns, you're connected.

You can also ask Claude to "list your PitchPrfct tools." In Claude Code, /mcp shows pitchprfct as connected, along with its tool count.

Want to see the full list of tools? There are 111, one for each Developer API action, named after the area they belong to. A few examples: contacts_list, contacts_create, messages_send, conversations_list, campaigns_list, campaigns_start, workflows_enroll, tags_list, and ten_dlc_brands_list. The full table, with what each tool does, is in the PitchPrfct API docs (MCP Server section). In Claude, you can also open Customize > Connectors and select PitchPrfct. In Claude Code, type /mcp.

Every tool shows up in the list, even ones your key doesn't have permission for. Those tools fail with a permission error when Claude tries to use them (see Troubleshooting).

Troubleshooting

I only see the OAuth Apps tab in PitchPrfct (no API Keys or MCP tab).

The API Keys and MCP tabs only show once your account has a verified phone number, an active subscription, and a 10DLC campaign at least at the pending-review stage. Check those setup steps, or contact PitchPrfct support.

I don't see "Request headers" in Claude.

Request header support is in beta and only available to some Claude organizations. Use Option B (Claude Code) or Option C (desktop config file) until it shows up for you.

Claude says the connection failed, or Claude Code shows "Failed to connect" with a 401 error.

API key is required. Provide it via x-api-key header. means the header is missing or was sent under another name. The header name must be exactly x-api-key.
Invalid API key means the key is wrong, was deleted, or was regenerated. Create a new key, then add it again.
In Claude, you can't edit a connector's header after saving it. Remove the connector (Customize > Connectors, then Remove or the three-dot menu) and add it again with the new key.
In Claude Code, run claude mcp remove pitchprfct, then run the add command again with the correct key.
With Option C, fix the key in claude_desktop_config.json, then restart Claude Desktop.

I see a "405 Method Not Allowed" error.

PitchPrfct's MCP server only accepts POST requests over the Streamable HTTP transport. If your tool is set to the older SSE transport, switch it to Streamable HTTP. In Claude Code, use --transport http (as in the command above), not --transport sse.

A tool fails with a permission error (403).

Every PitchPrfct tool shows up in Claude's list, even if your key doesn't have the permission it needs. When Claude uses a tool outside your key's permissions, PitchPrfct returns a 403 error that names the missing permission, for example Insufficient permissions (requires contacts:read). A 403 can also mean your account can't use that feature yet, for example subscription_required when you send messages or start campaigns without an active subscription. Create a key with the permission you need and reconnect.

I get a "Too many requests" (429) error.

PitchPrfct allows up to 1,000 API requests per minute and 100 per second per PitchPrfct user. This limit is shared by all of your API keys, connected OAuth integrations, and AI tools, and each tool call counts as one request. When you go over, PitchPrfct pauses your requests for about 1 second (per-second limit) or up to 60 seconds (per-minute limit). Wait a minute and try again, or ask Claude to work in smaller batches.

Claude Desktop shows no PitchPrfct tools (Option C).

Make sure Node.js 18 or later is installed, check that claude_desktop_config.json is valid JSON (a missing comma or quotation mark stops it from loading), and restart Claude Desktop.

PitchPrfct doesn't show up in my chat.

Click + in the chat box, select Connectors, and switch PitchPrfct on.

I'm on the Free plan and can't add the connector.

Free plans can have only one custom connector. Remove the other one, or upgrade.

I'm a Team or Enterprise member and can't add a custom connector.

Ask your Claude organization Owner to add it (see Option A).

Security tips

Treat your API key like a password. Don't paste it into a chat message, email, or shared document.
Give Claude only the permissions it needs. Use Custom access when you create the key. Be extra careful with sensitive permissions like Send Messages, Write Campaigns, Write Opt-Outs, and Write Phone Numbers.
Remember these are real texts to real people. If you let Claude send messages or start campaigns, those messages go out from your PitchPrfct numbers, use your credits, and must follow the same compliance rules as any other text you send.
Read Claude's permission prompts. Only choose "Always allow" for tools you trust to run without checking, and never for sending messages or starting campaigns. You can also block individual tools under Customize > Connectors.
Teams share one key. On Claude Team or Enterprise, everyone using the connector uses the same PitchPrfct key.
Claude Code saves your key on your computer. Don't add PitchPrfct with --scope project, because that writes the key into a project file (.mcp.json) that may be shared or committed to Git.
The Claude desktop config file stores your key in plain text. If you use Option C, don't share claude_desktop_config.json.
Lost a key, or someone left your team? In PitchPrfct, go to Settings > Developer API > API Keys, open the three-dot menu next to the key, and choose Regenerate or Delete. Then reconnect Claude with a new key and restart Claude (or Claude Code).
Watch for odd behavior. If Claude tries something you didn't ask for, stop and deny the request.

Need help? Contact PitchPrfct support through the in-app chat or at info@pitchprfct.com.

Connect PitchPrfct to Claude