4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
GSA Per Diem Rates MCP Server

Bring Per Diem
to CrewAI

Learn how to connect GSA Per Diem Rates to CrewAI and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Conus LodgingGet Mie BreakdownGet Rates By CityGet Rates By StateGet Rates By ZipGet Zip Mapping

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
GSA Per Diem Rates

What is the GSA Per Diem Rates MCP Server?

Connect to the GSA Per Diem Rates server to instantly retrieve federal travel reimbursement data. This tool allows AI agents to query the official U.S. General Services Administration database for accurate lodging and meal rates.

What you can do

  • City & State Lookups — Get precise rates for specific destinations like 'Fairfax, VA' for any fiscal year.
  • ZIP Code Queries — Quickly find rates using a 5-digit ZIP code to ensure location accuracy.
  • M&IE Breakdowns — Access detailed Meals and Incidental Expenses (M&IE) data, including breakfast, lunch, and dinner allocations.
  • Statewide Data — Retrieve all county and city rates within a specific state for broader travel planning.
  • CONUS Lodging — Fetch standard continental United States lodging rates for general budgeting.

How it works

  1. Subscribe to this server
  2. Enter your GSA API Key
  3. Ask about travel rates for any US location

Who is this for?

  • Finance & Accounting Teams — Automate the verification of travel expense reports against federal standards.
  • Government Contractors — Ensure compliance with federal travel regulations during project bidding and billing.
  • Travel Coordinators — Quickly calculate travel budgets for employees across different US regions.

Built-in capabilities (6)

get_conus_lodging

Get CONUS lodging rates for a specific year

get_mie_breakdown

Get M&IE breakdown rates for a specific year

get_rates_by_city

Get per diem rates for a specific city and state

get_rates_by_state

Get per diem rates for all counties and cities in a state

get_rates_by_zip

Get per diem rates for a specific ZIP code

get_zip_mapping

Useful for high volume requests. Get ZIP code to DID mapping for a specific year

Why CrewAI?

When paired with CrewAI, GSA Per Diem Rates becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GSA Per Diem Rates 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 mcps parameter 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

See it in action

GSA Per Diem Rates in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

GSA Per Diem Rates and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect GSA Per Diem Rates 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for GSA Per Diem Rates in CrewAI

The GSA Per Diem Rates 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 6 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.

GSA Per Diem Rates
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures GSA Per Diem Rates for CrewAI

Every tool call from CrewAI to the GSA Per Diem Rates MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I find the per diem rates for a specific city like Los Angeles?

You can use the get_rates_by_city tool. Just provide the city name (Los Angeles), the state abbreviation (CA), and the fiscal year you are interested in.

02

Is it possible to get a breakdown of meal costs for the day?

Yes! Use the get_mie_breakdown tool for a specific fiscal year. It returns the breakdown for Meals and Incidental Expenses (M&IE), showing allocations for breakfast, lunch, dinner, and incidentals.

03

Can I look up rates using just a ZIP code?

Absolutely. The get_rates_by_zip tool allows you to input a 5-digit ZIP code and a fiscal year to retrieve the applicable per diem rates for that specific location.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

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.

Explore More MCP Servers

View all →