Bring Corporate Expenses
to Cursor
Learn how to connect SAP Concur to Cursor and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the SAP Concur MCP Server?
Connect your AI assistant to SAP Concur, the leading platform for expense management, travel, and invoice automation.
What you can do
- Expense Tracking — List and inspect individual expenses including amounts, categories, and receipt metadata.
- Report Status — Check approval status of any expense report.
- User Profiles — Retrieve employee profile data including cost center and department.
How it works
1. Add the SAP Concur integration.
2. Register an app in the SAP Concur Developer Portal and provide the Client ID, Client Secret, and Refresh Token.
3. Query expense data via natural language commands.
Who is this for?
- Finance Teams — Pull expense summaries without logging into the dashboard.
- Travel Managers — Verify travel policy compliance in real time.
- Employees — Check approval status of their own reports from chat.
Built-in capabilities (9)
Retrieve detailed information about a specific expense
Retrieve detailed information about a specific expense report
Calculate basic totals for a list of recent expense reports
Retrieve the profile details of the currently authenticated Concur user
Retrieve a list of expense attendees (for business meals, etc.)
Retrieve a list of your expense reports from Concur
Retrieve a list of valid expense types configured in your organization
Retrieve a list of your expenses from Concur
Quickly list all expenses that have not yet been assigned to a report
Why Cursor?
Cursor's Agent mode turns SAP Concur into an in-editor superpower. Ask Cursor to generate code using live data from SAP Concur and it fetches, processes, and writes. all in a single agentic loop. 9 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
SAP Concur in Cursor
SAP Concur and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect SAP Concur to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for SAP Concur in Cursor
The SAP Concur MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
SAP Concur for Cursor
Every tool call from Cursor to the SAP Concur MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I get my Concur Client ID and Secret?
Register a new application in the SAP Concur Developer Portal. Once approved, you'll receive a Client ID and Client Secret.
What is the Refresh Token used for?
SAP Concur uses OAuth 2.0. The Refresh Token automatically generates short-lived access tokens without requiring manual login each time.
Can I submit an expense report via this integration?
The current version focuses on reading and listing data. Submit and approve capabilities may be added in future updates.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.