MCP.so
ログイン

GSA Per Diem MCP

@1102tools

GSA Per Diem MCP について

MCP server for GSA Per Diem Rates: federal travel lodging and M&IE rates for all CONUS locations. Look up by city, state, or ZIP. Returns monthly lodging rates with seasonal variations, M&IE breakdowns, and first/last day rates at 75%. 6 tools.

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

1102tools

投稿者

James

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "gsa-perdiem": {
      "command": "uvx",
      "args": [
        "--refresh-package",
        "gsa-perdiem-mcp",
        "--from",
        "gsa-perdiem-mcp",
        "gsa-perdiem-mcp"
      ],
      "env": {
        "PERDIEM_API_KEY": "your-key-here"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is GSA Per Diem MCP?

A Model Context Protocol server that wraps the GSA Per Diem Rates API into deterministic tool calls. Designed for IGCE developers, travel coordinators, contract analysts, and federal program managers who need to price travel CLINs or estimate government employee TDY costs.

How to use GSA Per Diem MCP?

Install via uvx or pip install gsa-perdiem-mcp. Requires a free api.data.gov key set as the PERDIEM_API_KEY environment variable. Configure in any MCP‑compatible client (Claude Desktop, Codex, Gemini CLI, Copilot, etc.) using the provided JSON or TOML config.

Key features of GSA Per Diem MCP

  • Six tools covering all CONUS locations.
  • Lookup per diem by city, ZIP, or state.
  • Monthly lodging rate breakdowns with seasonal variation.
  • Full M&IE daily rate plus per‑meal breakdown.
  • Multi‑day trip cost estimator with first/last day adjustments.
  • Cross‑location comparison for up to multiple destinations.

Use cases of GSA Per Diem MCP

  • Build the travel CLIN portion of any IGCE.
  • Estimate contractor TDY costs for proposal evaluation.
  • Government employee TDY estimates for budget submissions.
  • Compare lodging rates across candidate conference or PMR sites.
  • Validate contractor invoiced travel costs against the FTR.

FAQ from GSA Per Diem MCP

What dependencies or runtime are required?

A free api.data.gov key (1,000 requests/hour) and an MCP‑compatible client (Claude Desktop, Codex, Gemini CLI, Copilot, etc.). The server runs via uvx or as a Python package.

Where does the data come from?

All rates are sourced from the official GSA Per Diem Rates API (api.data.gov). No local data storage; every call fetches live government data.

Are there any known rate limits or transport constraints?

The API enforces a 1,000 requests per hour limit. The server uses standard I/O (stdio) transport; no HTTP or WebSocket transport is mentioned.

How is authentication handled?

The API key is passed to the server via the PERDIEM_API_KEY environment variable. No other authentication method is described.

Does it handle edge cases like non‑listed locations or first/last travel days?

Yes. The server includes standard‑rate fallbacks for non‑listed locations, first/last day M&IE at 75% per FTR 301‑11.101, and monthly seasonal rate variations. It has been tested across multiple fiscal years.

コメント

「その他」の他のコンテンツ