Bring Corporate Expenses
to CrewAI
Learn how to connect SAP Concur to CrewAI 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 CrewAI?
When paired with CrewAI, SAP Concur becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call SAP Concur tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
SAP Concur in CrewAI
SAP Concur and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect SAP Concur to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.