Coupa
Coupa provides a comprehensive business spend management platform with procurement, invoicing, and expense capabilities.
Verdict
Common use cases
- Check PO approval status during vendor calls
- Pull quarterly spend by category for budget reviews
- Verify invoice details before payment runs
- List overdue supplier invoices for collections
- Compare contract terms across active agreements
Integration
- Vendor
- Coupa
- Category
- finance
- Auth
- OAUTH2
- Composio slug
coupa
Tools
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations page. 2. Find Coupa in the Finance category and click Connect. 3. You'll redirect to Coupa's OAuth consent screen—log in with your Coupa admin or power-user credentials. 4. Grant read access to purchase orders, invoices, suppliers, and spend reports (Coupa will list the exact scopes). 5. Coupa redirects you back to Switchy with a green confirmation banner. 6. Open any Space, type '@Coupa show open POs over $10k' and send—if the MCP replies with a list, the connection works. 7. Invite teammates who need procurement visibility to the Space; they inherit access without separate auth.
What teammates see: by default, memories from Coupa are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Open PO Summary
@Coupa show me all open purchase orders pending approval, sorted by total value descending.Open in a Space →
Supplier Invoice Check
@Coupa pull all unpaid invoices from Acme Corp submitted in the last 30 days.Open in a Space →
Spend by Department
@Coupa give me Q1 spend totals grouped by department, including uncommitted PO amounts.Open in a Space →
Contract Expiry Alert
@Coupa list all supplier contracts expiring in the next 90 days with annual value over $50k.Open in a Space →
Requisition Bottleneck
@Coupa show requisitions that have been pending approval for more than 5 business days.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Coupa show me all purchase requisitions submitted in the last 7 days that are still pending approval, grouped by department
Based on the last week's activity, 14 requisitions are pending approval across three departments. Engineering has 8 requisitions totaling $47,200 (mostly software licenses and cloud infrastructure). Marketing has 4 requisitions for $12,800 (event sponsorships and creative services). Operations has 2 requisitions for $6,300 (office supplies and maintenance contracts). The oldest pending item is a $15,000 AWS credit request from Engineering, submitted 6 days ago and currently with the VP of Finance.
This read-heavy example demonstrates procurement visibility across organizational boundaries. Requires OAuth scopes for requisition read access and department metadata. Response accuracy depends on your Coupa instance's approval workflow configuration and whether requisitions are tagged with cost centers.
@Coupa create a new supplier record for Acme Cloud Services with payment terms Net 30, primary contact sarah@acmecs.com, and tag it for the Engineering department
Supplier record created successfully. Acme Cloud Services is now in your Coupa supplier directory with ID SUP-8847. Payment terms set to Net 30. Primary contact Sarah Chen (sarah@acmecs.com) added. The supplier is tagged for Engineering department access and will appear in their vendor selection dropdown when creating requisitions. Note that the supplier is currently in 'Pending Verification' status and will need approval from Procurement before purchase orders can be issued.
This write example shows supplier onboarding automation, which typically requires elevated OAuth permissions beyond read-only access. Be aware that creating supplier records may trigger approval workflows in your Coupa instance, and the new supplier won't be immediately usable for POs until procurement completes verification steps.
@Coupa analyze our top 10 vendors by spend this quarter and flag any where we're approaching contract renewal dates in the next 60 days
Your top 10 vendors represent $1.2M in spend this quarter (68% of total procurement). Three vendors have contracts expiring within 60 days: AWS ($340K quarterly spend, contract expires April 15), Salesforce ($89K, expires May 2), and DataDog ($34K, expires April 28). AWS spend is up 22% quarter-over-quarter, suggesting you may want to negotiate volume discounts during renewal. Salesforce spend is flat, and DataDog spend decreased 8% as you migrated some workloads. The remaining 7 vendors have contracts extending beyond Q3.
This synthesis example combines spend analytics with contract lifecycle data to surface renewal risks. Requires OAuth access to both invoice/payment history and contract management modules. The AI's spend trend analysis is only as current as your last Coupa sync, and contract dates must be accurately maintained in the system to avoid missing renewal windows.
Use-case deep-dives
When Coupa MCP speeds up purchase order workflows
A 10-person startup runs all vendor purchases through Coupa but approval chains still ping-pong in Slack. The Coupa MCP lets your AI assistant surface pending POs, check budget line status, and flag blocked requisitions without opening the Coupa UI. Your ops lead asks "what's holding up the AWS contract?" and gets the answer in 8 seconds instead of hunting through email threads. This works when your approval volume is under 50 requests a week and you're already on Coupa—if you're still using spreadsheets or your finance team is one person, the OAuth setup overhead isn't worth it yet. The buying call: if Coupa is already your system of record and you're tired of context-switching to check request status, this MCP turns procurement questions into chat queries.
How the Coupa MCP handles distributed expense lookups
A 25-person remote team closes books on the 5th of each month, and the finance lead spends 4 hours chasing down which department owns which invoice. The Coupa MCP lets your AI workspace pull spend summaries by cost center, flag unmatched receipts, and answer "who approved this $8k charge?" without exporting CSVs. Your controller asks the assistant to list all open invoices over $2k, gets a structured response, and moves on. This scenario breaks down if your Coupa instance has custom fields the MCP can't read yet, or if you need to write back approvals—right now it's read-only until the vendor publishes tool definitions. The call: if month-end reconciliation eats more than 3 hours and you trust OAuth delegation, this MCP cuts that time in half.
When Coupa MCP supports vendor risk review workflows
A 40-person SaaS company onboards 15 new vendors a quarter, and the compliance lead needs to verify each one passed insurance and W-9 checks before the first invoice posts. The Coupa MCP lets your AI assistant pull vendor profiles, check document upload dates, and flag missing compliance artifacts in a single query. Your compliance officer asks "which new vendors this quarter are missing certificates?" and gets a list with submission timestamps. This use-case assumes your Coupa workflows already enforce the document requirements—if your vendor data lives in multiple systems or you haven't standardized the onboarding checklist, the MCP can't synthesize what isn't there. The threshold: if you onboard more than 10 vendors a quarter and compliance review is manual, this MCP turns a spreadsheet audit into a conversational lookup.
Frequently asked
What does the Coupa MCP do in Switchy?
The Coupa MCP connects your Switchy workspace to Coupa's spend management platform. Your team can query procurement data, check purchase order status, and pull supplier information without leaving the AI chat interface. It's useful for finance teams who need quick answers about company spending without logging into Coupa's web portal every time.
Do I need admin access to connect Coupa via OAuth?
You'll need a Coupa account with API access enabled, which typically requires admin or finance-role permissions in your Coupa instance. The OAuth flow requests read access to procurement and supplier data. Check with your Coupa administrator if you're unsure whether your account has the necessary API privileges before attempting to connect.
Can the Coupa MCP create or approve purchase orders?
Not yet. The current integration focuses on read-only queries — checking PO status, supplier details, and spend analytics. If you need to create requisitions or approve invoices, you'll still need to use Coupa's native interface. The MCP is designed for information retrieval, not transaction workflows that require audit trails and approval chains.
How does querying Coupa through Switchy compare to using Coupa's API directly?
Switchy removes the need to write code or construct API calls. Instead of building scripts to fetch purchase order data, your team asks questions in plain English and the MCP handles the API requests. You lose fine-grained control over pagination and filtering, but you gain speed for ad-hoc queries that don't justify custom development.
Who on the finance team should connect the Coupa integration?
Whoever owns procurement reporting or regularly fields spend-related questions from other departments. This is usually a finance analyst or procurement manager who already has Coupa access and understands your company's supplier structure. One connection serves the entire Switchy workspace, so choose someone who can troubleshoot OAuth issues if the token expires.