Connect once, then ask your assistant for a rate. Every Allowances API endpoint is a tool.
https://mcp.allowancesapi.com/mcp
Streamable HTTP. Send your key in the X-API-Key header
on every request.
One command for Claude Code, one config block for Claude Desktop. The Cursor link installs
the server with a YOUR_KEY placeholder to replace in Cursor's MCP settings.
Travel budgets
"What is the GSA per diem for San Diego in March 2027?"
Overseas proposals
"Give me the DSSR COLA and hardship rates for Nairobi, Kenya."
Expense checks
"Calculate the mileage reimbursement for a 240-mile drive on 2026-10-01."
/v1/ endpoint is exposed as an MCP
tool: per diem lookups, DSSR allowances, the GSA mileage and trip calculators,
metadata and your usage.Replace YOUR_KEY with your API key. Each
snippet is complete; nothing else is required.
One command registers the server for the current project. Add --scope user to make it available everywhere.
claude mcp add --transport http allowances https://mcp.allowancesapi.com/mcp \
--header "X-API-Key: YOUR_KEY"
Commit a .mcp.json at the repository root and keep the key in an environment variable.
{
"mcpServers": {
"allowances": {
"type": "http",
"url": "https://mcp.allowancesapi.com/mcp",
"headers": { "X-API-Key": "${ALLOWANCES_API_KEY}" }
}
}
}
Use the Connect in Cursor button above, or add this to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
{
"mcpServers": {
"allowances": {
"url": "https://mcp.allowancesapi.com/mcp",
"headers": { "X-API-Key": "YOUR_KEY" }
}
}
}
Add this to .vscode/mcp.json in your workspace. VS Code prompts for the key on first use and never writes it to the file.
{
"inputs": [
{ "type": "promptString", "id": "allowances-key", "description": "Allowances API key", "password": true }
],
"servers": {
"allowances": {
"type": "http",
"url": "https://mcp.allowancesapi.com/mcp",
"headers": { "X-API-Key": "${input:allowances-key}" }
}
}
}
Claude Desktop cannot send custom headers to remote servers, so it connects through the mcp-remote bridge (needs Node.js). Open Settings, Developer, Edit Config and add this, then restart the app.
{
"mcpServers": {
"allowances": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.allowancesapi.com/mcp", "--header", "X-API-Key:${ALLOWANCES_API_KEY}"],
"env": { "ALLOWANCES_API_KEY": "YOUR_KEY" }
}
}
}
Register the URL, then add the header to ~/.codex/config.toml. env_http_headers reads the key from an environment variable instead.
codex mcp add allowances --url https://mcp.allowancesapi.com/mcp
# ~/.codex/config.toml
[mcp_servers.allowances]
url = "https://mcp.allowancesapi.com/mcp"
http_headers = { "X-API-Key" = "YOUR_KEY" }
Lists the available tools. Without the header the server answers 401.
curl https://mcp.allowancesapi.com/mcp \
-H "X-API-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
The MCP tools mirror the REST endpoints and are documented next to them. The
API reference lists them in its
MCP section, with the input schema of every tool, and the
OpenAPI document publishes the full
catalogue in its x-mcp extension, so agents can discover
the server from the schema alone.
Data sourced from official public per diem and allowances tables. Not affiliated with any government agency.
Claude, Cursor, Visual Studio Code, GitHub Copilot and Codex are trademarks of their respective owners.