🔒 Read-only. Your AI assistant can query and report on your data. It cannot create cards, approve transactions, change spending limits, or modify anything in Pemo.
Pemo MCP connects Pemo to AI assistants such as Claude, ChatGPT, Gemini, and Copilot. You can ask questions in plain English and get answers from your live Pemo data. It works with any client that supports MCP connectors.
What you can ask
Data type | Example questions |
Transactions | Show recent transactions, filter by merchant or date, and find spend without receipts |
Reimbursements | List pending claims, check approval status, and see who submitted claims this month |
Cards | List company cards, check which are active or frozen, and see the cardholder and last four digits |
Members | List team members, check roles, and see which cards belong to them |
Companies | List the companies you belong to and your role in each |
Before you start
Pemo MCP is a public connector in Claude. In ChatGPT, Gemini and other assistants, you add it as a custom connector using the Pemo MCP server URL: https://mcp.pemo.io/mcp.
There is nothing to request from Pemo and no credentials to get from Support. You need your own Pemo login, and what you see follows your Pemo role.
Connect Pemo in Claude
Open Customize > Connectors.
Search for Pemo and select it.
Select Connect.
At accounts.pemo.io, sign in with your Pemo login.
Review the read-only permissions and select Approve.
Return to Claude. Pemo shows as connected.
To use Pemo in a chat, select +, then Connectors, then turn on Pemo.
Connect Pemo in ChatGPT, Gemini and other assistants
In your assistant, open its connector or app settings and choose to add a custom connector. In ChatGPT, open Settings > Plugins and add a custom connector there. Custom connectors need ChatGPT Developer mode, a ChatGPT setting, not a Pemo requirement.
Enter the name Pemo and the server URL
https://mcp.pemo.io/mcp.If asked for an authentication method, choose OAuth.
Save the connector, then select connect or sign in.
At accounts.pemo.io, sign in with your Pemo login and select Approve.
Turn Pemo on in a chat.
Who can see what
Your Pemo role determines what your AI assistant can access. A Super Admin or Admin can query company-wide data. An Accountant (Internal or External) sees what their role permits. A Team Lead sees their team’s cards and spend. The MCP enforces these boundaries for every query.
Can my AI assistant change Pemo data?
No. Pemo MCP is read-only. It can retrieve data, but it cannot approve transactions, issue cards, change spending limits, or modify your account.
Why is the connector returning no data?
The consent step may be incomplete. Disconnect and reconnect Pemo in your assistant's connector settings (in Claude: Customize > Connectors), then complete the approval at accounts.pemo.io.
Does it work with other AI assistants?
Yes. Any assistant that supports MCP connectors. Outside Claude, add it as a custom connector with https://mcp.pemo.io/mcp.
What data is unavailable?
Full card numbers, CVVs, and PINs are never exposed. Cards show only their last four digits.
⚠️ AI assistants can make mistakes. Always verify numbers (balances, transaction counts, approval statuses) directly in Pemo before acting on them.
Get access
There is no access request. Connect Pemo yourself using the steps above. For questions, contact [email protected] or use the in-app chat.
Ready-made analyses to ask for
Once connected, ask your assistant for any of these in plain language:
Monthly spend briefing: last month's exact total, the top eight categories and a domestic versus international split.
Month-over-month trend: a six-month chart, the monthly % change, and this month's pace against the trailing three-month average.
Spend explorer: the last 30 days ranked by category, merchant and employee, flagging duplicate subscriptions and outlier spenders.
Compliance and export readiness: a receipt chase list, an export-readiness breakdown and the % of spend ready to export.
Reimbursement backlog: the total owed, who is owed most, and how long claims have waited.
Idle card audit: active cards unused in the last 30 days, with their cardholders.
Card and access health: card statuses, member roles, inactive members with access, and KYC not approved.
Declined transaction triage: failure reasons by frequency, the cardholders with most declines, and next actions.
Vendor deep-dive: one merchant's spend trend, who pays it, and possible duplicate payments. Use the merchant's name as it appears on statements.
Usage notes
Interactive dashboards are available only in Claude. In other assistants, ask for the same breakdown as a table. A finished dashboard doesn't fetch live data.
These analyses can include cardholder names, emails, KYC and receipt details. Keep them to Finance, Admins and Accountants, and redact names before sharing outside the company.
A page of results is capped at 100 rows. For exact totals, the assistant goes through every page; after roughly 40 calls it pauses and asks whether to continue or narrow the filter.
Exploratory views start with one page for speed, which may skew results for high-volume companies. Ask for the exact total to include every page.
Refunds, purchase reversals and wallet top-ups appear in lists but are excluded from totals.
Next step
You've reached the end of the journey. Still have a question? See Answers to your Pemo questions.
