MCP

Paminga runs an MCP server, so the AI assistant you already use (Claude, ChatGPT, Claude Code, or any other client that speaks the Model Context Protocol) can answer questions about your Paminga data.

Connect once, then ask the way you'd ask a colleague: "What's our open rate this month?" "Who clicked the pricing link in last week's newsletter?" "Can I delete this list, or does something still use it?" Your assistant works out what to ask Paminga, Paminga answers from your live account, and your assistant writes the reply.

Because the assistant is yours, you can ask it to combine Paminga's answers with anything else it's connected to: a spreadsheet, your CRM, your notes.

How It Works

Paminga doesn't write the answer. Your assistant does.

1. You ask a question in your assistant.
2. Your assistant picks the Paminga tools that answer it and calls them.
3. Paminga runs those requests against your account and returns the results: counts, rates, rows, and named contacts with links back to their records.
4. Your assistant reads the results and answers you in plain language.

Every request is made as you, against your own account. The connection is read-only: your assistant can look things up, but it can't create, edit, send, or delete anything in Paminga.

The numbers are only as good as your assistant's reading of them. Paminga returns the same results to every assistant, but a more capable model is better at choosing the right request and explaining what comes back.

What You Can Ask

Your assistant can reach the same reporting data that powers Paminga's dashboards and the Looker Studio connector. That includes:

• Email performance: sends, opens, clicks, bounces and unsubscribes, by automation or by email, with open and click rates that match the ones you see in Paminga.
• Who engaged: the contacts who opened, clicked, bounced or unsubscribed, or who didn't open or click.
• Forms and content: form submissions and file downloads, by form, page, or campaign.
• Leads and opportunities: volume, stage, and lead score activity.
• Workflows: activity and health across your automations.
• CRM sync: sync runs and the errors they hit.
• What changed: a sweep for metrics that moved unusually over the last week, compared against the 90 days before it.
• What uses what: everything that references a list, segment, email, signature, tag, or custom field, before you change or delete it.
• How your account is set up: integrations, CRM, custom fields, and scoring.
• Saved reports: run one of your saved reports by name, so your assistant's numbers match the ones your team already agreed on.

Ask comparison questions too. "How did September compare to August?" and "Are form submissions up or down against last quarter?" are both fair game.

When Paminga can't answer something, your assistant is told so, along with the reason, rather than given a different number that only looks like an answer.

Connect Your Assistant

Go to Personal Settings → Connect an AI Assistant. That page shows your Server URL and the setup steps for each assistant, ready to copy.

There are two ways to connect. Signing in is the better choice for most people.

Sign In (Recommended)

Your assistant sends you to Paminga to sign in and approve access. You never handle a token.

• claude.ai and Claude Desktop: open Customize, then Connectors, choose Add custom connector, and paste your Server URL. On a Team or Enterprise plan, an organization owner adds the connector first, under Organization settings.
• ChatGPT: add a custom MCP server with your Server URL, and sign in when asked. Where ChatGPT keeps this setting, and which plans allow it, has changed more than once. In a Business or Enterprise workspace, an admin may need to allow it.
• Claude Code: run the command shown on the Connect page, then run /mcp inside Claude Code to sign in.

Access granted this way lasts 90 days at a time and renews itself while you keep using it.

Use a Token

Some clients can't sign in. For those, create a token on the Connect page: give it a name and an expiration date, and click Create Token. Paminga fills the token into the setup text for you:

• Claude Code: the command reads the token from a PAMINGA_TOKEN environment variable each time it connects, so the token never sits in your command history.
• Claude Desktop: a ready-made entry for claude_desktop_config.json.

Treat the token like a password. It also works with Paminga's API.

Existing tokens don't work here

A token only connects an assistant if it was created with AI assistant access turned on. Tokens you created for the API before don't qualify, even ones that work everywhere else. Create a new one on the Connect page, or tick Allow AI assistant (MCP) access when you create one under Personal Access Tokens.

Disconnecting

To cut off a token, revoke it under Personal Access Tokens. The AI Assistant column there shows which of your tokens can connect an assistant.

To disconnect an assistant you signed in with, remove the Paminga connector in that assistant's settings.