Last checked: October 9, 2026

The easiest way to use PitchPrfct with ChatGPT is through Codex. Codex is included with your ChatGPT plan, you sign in with the same OpenAI account, and you chat with it in plain English just like ChatGPT. (Regular chats on chatgpt.com don't support PitchPrfct's sign-in method yet. PitchPrfct's API docs list "Sign in with PitchPrfct" for ChatGPT as coming soon, so Codex is the way to go for now.)

Once PitchPrfct is connected, you can ask Codex things like "list my PitchPrfct contacts" or "show me my PitchPrfct campaigns." Behind the scenes, PitchPrfct's MCP server (MCP is a standard way for AI assistants to use other apps) turns the PitchPrfct Developer API into tools Codex can use, one tool for each API action: listing and creating contacts, sending messages, managing campaigns and workflows, and more. Codex can only do what your API key allows, and its tool calls count toward the same rate limits as your other API requests.

How it's the same, and what's different

The same as ChatGPT:

Same OpenAI account and the same ChatGPT plan. No new subscription.
You type requests in plain English and get answers back in a chat.
If you use the ChatGPT desktop app, Codex lives right inside it.

What's different:

In the desktop app, you pick Codex instead of ChatGPT when you start a chat.
Codex can use your PitchPrfct tools, and it can ask your permission before each one (we show you how to turn that on below).
Codex usage counts toward your plan's Codex and ChatGPT Work limits, which vary by plan.

What you 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 ChatGPT account. Codex is included with ChatGPT plans. On Free and Go, Codex access is limited and centered on the desktop app (OpenAI notes it's subject to rollout). Plus and higher also include the Codex CLI and IDE extension. If you're in a ChatGPT Business or Enterprise workspace, your admin may control which MCP servers you can use.
The ChatGPT desktop app for macOS, Windows, or Linux (download it from https://chatgpt.com/download/). Or, if you prefer, the Codex CLI or Codex IDE extension (see "Other ways to connect" below).
A PitchPrfct API key. Step 1 shows you how to create one.

Connection details, for reference:

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 Codex, 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. You'll use the Codex CLI snippet from that tab in Step 2.

Step 2: Connect PitchPrfct in the ChatGPT desktop app

Open the ChatGPT desktop app and sign in with your ChatGPT account.
Open Settings (from the app menu, or press Cmd+, on Mac or Ctrl+, on Windows).
Go to Configuration. At the top of the page, open the scope dropdown (it may say Work) and choose Codex.
With Codex selected, click Open config.toml on the right. This opens Codex's settings file.
In PitchPrfct, open the Developer API page (https://app.pitchprfct.com/app/developers), select the MCP tab, then select the Codex CLI tab and click Copy. (The page says to add it to ~/.codex/config.toml. That's the same file you just opened.)
Paste it at the end of config.toml. It looks like this:
```
[mcp_servers.pitchprfct]
url = "https://app.pitchprfct.com/api/mcp"
http_headers = { "x-api-key" = "YOUR_API_KEY" }
```
Replace YOUR_API_KEY with your PitchPrfct key. Keep the quotation marks. (If you click Create API key on the MCP tab, PitchPrfct puts the new key in the snippet for you.)
- Recommended: add this line right under it, so Codex asks you before it uses any PitchPrfct tool:
```
default_tools_approval_mode = "prompt"
```
When you're done, the PitchPrfct part of your file should look like this (with your real key):
Save the file.
Back in Settings, select Plugins (under Integrations), then the MCPs tab. You can also type MCP in the Settings search box. Under Servers, find pitchprfct and make sure its switch is on. If it isn't listed yet, quit and reopen the ChatGPT desktop app so it reloads config.toml.
Start a chat: choose Codex, then start a New chat.
Type /mcp in the chat box. A status panel lists your MCP servers. PitchPrfct should be listed as enabled.

Prefer a form instead of editing the file? In Settings > Plugins > MCPs, click Add to open Connect to a custom MCP. Enter a Name (for example pitchprfct), set Type to Streamable HTTP, and enter the URL https://app.pitchprfct.com/api/mcp. Under Headers, put x-api-key in Key and your PitchPrfct API key in Value, then click Save. (The form also has Bearer token env var and Headers from environment variables fields. PitchPrfct doesn't need them.) You still need the approval-mode line in config.toml if you want Codex to ask before each tool (default_tools_approval_mode = "prompt"). Pasting the PitchPrfct snippet into config.toml remains a reliable one-step option.

Connect to a custom MCP form with Streamable HTTP and Headers fields

Step 3: Try it out

In your Codex chat, try any of these:

"List my PitchPrfct contacts."
"Show me my PitchPrfct campaigns."
"Find the PitchPrfct contact named Jane Smith and show me her details."
"Show me my PitchPrfct workflows and tell me which ones are active."

Codex asks permission the first time it uses each PitchPrfct tool. Read what it plans to do, then approve. If you see your real PitchPrfct data, you're all set.

Tips:

If Codex tries to do something else (like search the web), say: "Only use the PitchPrfct MCP tools for this."
To see every PitchPrfct tool Codex can use, type /mcp or ask Codex to "list your PitchPrfct tools." There are 111, one for each Developer API action, with names like contacts_list, messages_send, campaigns_list, and workflows_enroll. The full table is in the PitchPrfct API docs (MCP Server section). Every tool shows up, even ones your key doesn't have permission for; those fail with a permission error when Codex uses them.
Be specific when you ask Codex to change things, for example "Add the tag 'Hot Lead' to Jane Smith in PitchPrfct." Double-check before you approve anything that sends texts or starts a campaign.

Other ways to connect: Codex CLI or IDE extension

The ChatGPT desktop app, the Codex CLI, and the Codex IDE extension (for editors like VS Code) all share the same settings file, ~/.codex/config.toml. If you already set things up in the desktop app, PitchPrfct is ready in the CLI and IDE extension too.

To set it up from scratch:

Open ~/.codex/config.toml in a text editor (on Windows: C:\Users\<your name>\.codex\config.toml). Create it if it doesn't exist. In the IDE extension, you can open it from the gear icon: Codex Settings > Open config.toml.
Paste the Codex CLI snippet from PitchPrfct's MCP tab (the same one from Step 2), with your key in place of YOUR_API_KEY. We recommend the extra approval line too:
```
[mcp_servers.pitchprfct]
url = "https://app.pitchprfct.com/api/mcp"
http_headers = { "x-api-key" = "YOUR_API_KEY" }
default_tools_approval_mode = "prompt"
```
Save the file.
Load the new settings:
- Codex CLI: run codex mcp list to check that pitchprfct is there. Then run codex and type /mcp to see it.
- IDE extension: open the gear menu, select MCP servers, make sure pitchprfct is enabled, and select Restart extension.

Optional, for people comfortable with environment variables: keep the key out of the file by storing it in an environment variable (for example PITCHPRFCT_API_KEY) and using this line in place of http_headers:

env_http_headers = { "x-api-key" = "PITCHPRFCT_API_KEY" }

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.

PitchPrfct doesn't show up in /mcp or under Settings > Plugins > MCPs.

Make sure you saved config.toml, and that the first line of the snippet is exactly [mcp_servers.pitchprfct].
A small typo (like a missing quotation mark) can stop the file from loading. Compare it to the snippet above.
Quit and reopen the ChatGPT desktop app (or restart the CLI or IDE extension) so it reloads config.toml.
Make sure you started a Codex chat, not a ChatGPT chat.

It shows up but won't connect, or I see 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. It must be exactly x-api-key.
Invalid API key means the key is wrong, was deleted, or was regenerated. Create a new key and paste it into config.toml.
If you used env_http_headers, make sure the environment variable is set where Codex runs.

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 Codex, the url = ... snippet above already uses Streamable HTTP. If you used the Add form, make sure Type is set to Streamable HTTP.

A tool fails with a permission error (403).

Every PitchPrfct tool shows up in Codex's list, even if your key doesn't have the permission it needs. When Codex 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 update config.toml.

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 Codex to work in smaller batches.

I tried adding PitchPrfct on chatgpt.com and there's nowhere to put my API key.

That's expected for now. Regular ChatGPT chats only support other sign-in methods for custom MCP servers. PitchPrfct's API docs list "Sign in with PitchPrfct" for ChatGPT as coming soon, with no date yet. Until it's live, use Codex as shown above.

My ChatGPT Business or Enterprise workspace blocks it.

Workspace admins can control which MCP servers members can use. Ask your ChatGPT workspace admin.

Security tips

Treat your API key like a password. Don't paste it into a chat message, email, or shared document.
Your key is saved in config.toml on your computer. Don't share that file, and never put the key in a project-level .codex/config.toml that might be shared or committed to Git. The environment variable option keeps the key out of the file.
Give Codex 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 Codex 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.
Keep approvals on. Add default_tools_approval_mode = "prompt" (see Step 2) and read each request before you approve it.
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 update config.toml with a new key and restart Codex.
Watch for odd behavior. If Codex 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

Use PitchPrfct with ChatGPT (via Codex)