ekispert-api -docs

This MCP server exposes the駅すぱあと API through the MCP protocol, enabling any compatible AI agent (for example, within Visual Studio Code, Claude Desktop, or other MCP-compatible tools) to call the API via natural language prompts. The server authenticates requests using your ekispert API access key and streams responses over HTTP in accordance with the MCP standard, making it straightforward to integrate travel search, fare calculations, and route planning into AI workflows. The configuration examples show how to wire the server with popular tools, including using npx to fetch the latest mcp-remote wrapper and pass the API access key in headers. When connected, you can issue prompts like asking for the cheapest IC fare between two stations and receive structured results.

Prerequisites:

• Node.js and npm (or pnpm) installed on your machine
• An ekispert API access key (or a placeholder for testing)
• Optional: a MCP client/tool (VS Code MCP extension, Claude/Claude Desktop, etc.)

Step-by-step:

1. Prepare your environment variable for the access key (recommended):
   • On Unix-like systems: export EKISPERT_API_ACCESS_KEY=your_key_here
   • On Windows (PowerShell): $env:EKISPERT_API_ACCESS_KEY='your_key_here'
2. Run the MCP server client via npx (as shown in the README examples):
   • For dynamic usage with an MCP-enabled tool, you can run: npx -y mcp-remote@latest https://api-mcp.ekispert.jp/mcp --header ekispert-api-access-key:${EKISPERT_API_ACCESS_KEY}
   • If you want to embed the key via environment variable (recommended): ekispert-api-access-key: ${EKISPERT_API_ACCESS_KEY}
3. If you prefer a persistent configuration using Claude Desktop, create a claude_desktop_config.json with the sample provided in the README, ensuring the header uses your environment variable (EKISPERT_API_ACCESS_KEY).
4. Validate connectivity by connecting an MCP client to the URL and sending a simple request for station routing or fare information.

Notes:

• The exact command may vary depending on the MCP client you use; the essential pieces are the server URL and the access-key header.
• Keep your access key secure and use environment variables rather than embedding keys directly in configuration files.

Tips and caveats:

• Ensure the header name matches the ekispert API requirement: ekispert-api-access-key.
• Use environment variables to protect sensitive keys (EKISPERT_API_ACCESS_KEY) rather than hard-coding them.
• The server examples assume a streamable HTTP communication pattern consistent with MCP; some clients may require additional headers or query options depending on the tool.
• If you plan to distribute configurations, prefer npx-based invocation or a wrapper script to avoid exposing keys in files.
• Keep an eye on the 2026/07/01 timing mentioned in the docs, as access key issuance and policies may change; adjust configurations accordingly when updates are released.