Connect ChatGPT
Use Rampsend from ChatGPT (web)
ChatGPT connects to remote MCP servers through developer mode. Turn it on, point a custom app at the Rampsend endpoint, and ChatGPT can send email, look up deliveries and read your stats in the conversation.
Paste into chatgpt.com/plugins → + → Connection
https://app.rampsend.com/api/mcpSet it up
- 1
Turn on developer mode
In ChatGPT on the web, go to Settings → Security and login and switch Developer mode on. This unlocks full MCP tools rather than search-only connectors.
- 2
Create the connection
Open chatgpt.com/plugins and click + to create a developer-mode app for a remote MCP server.
- 3
Paste the endpoint
Give it a name and description, then under Connection paste the endpoint — including the /api/mcp path. A bare domain will not reach the server.
Endpoint https://app.rampsend.com/api/mcp - 4
Choose OAuth and approve
Pick OAuth as the authentication mode and finish the sign-in, approving one Rampsend workspace. ChatGPT reads the tool list and shows it for review; the app then lands under Drafts.
- 5
Select it in a conversation
Open the + menu in the composer, choose Developer mode, and select Rampsend for that chat. Naming it helps the first few times: “use Rampsend to…”.
Check it works
Ask “How many Rampsend credits do I have left?”. A number back means you are connected. That call only reads your account, so testing costs nothing.
What trips people up
- The naming moved twice: connectors became apps, and a plugin is the newer wrapper around apps. Guides that say Settings → Connectors are stale — the current route is Settings → Security and login → Developer mode, then chatgpt.com/plugins.
- Paste the full URL with /api/mcp on the end. This is the most common setup failure.
- Actions that change something ask for approval by default, so expect a confirmation prompt the first time ChatGPT sends an email.
- When we ship new tools, open the app’s details page and click Refresh to re-read the tool list. It does not update by itself.
- This is web only. The ChatGPT desktop app uses a separate mechanism shared with Codex — see the Codex guide.
- Sign-in covers sending, stats, email lookups, contacts and domain checks. Adding a new sending domain needs a Full access API key, so add the domain in the app under Deliverability → Domains and let the assistant check it from there.
Try asking
- “Use Rampsend to show my sending stats for the last 30 days.”
- “Which of my recent emails bounced, and why?”
- “Add ada@example.com as a contact with plan set to pro.”
- “Send a short test from hello@acme.com to me@acme.com.”