pricing — expense tracker receipts mileage MCP Resource
pricing
is one of 2 resources on the
expense tracker receipts mileage
MCP server. Connect the server and your client can attach it as context.
by client
How to attach pricing from your client
- Claude Code expense tracker receipts mileage Resource/pricing run in your project directory
- Claude Desktop expense tracker receipts mileage Resource/pricing ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor expense tracker receipts mileage Resource/pricing ~/.cursor/mcp.json
- VS Code expense tracker receipts mileage Resource/pricing .vscode/mcp.json
- Zed expense tracker receipts mileage Resource/pricing ~/.config/zed/settings.json
- Windsurf expense tracker receipts mileage Resource/pricing ~/.codeium/windsurf/mcp_config.json
- Cline expense tracker receipts mileage Resource/pricing ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI expense tracker receipts mileage Resource/pricing ~/.gemini/settings.json
- Grok expense tracker receipts mileage Resource/pricing .mcp.json (in your project root)
- ChatGPT expense tracker receipts mileage Resource/pricing Settings → Connectors → Advanced → Developer mode
- Claude.ai expense tracker receipts mileage Resource/pricing Settings → Connectors → Add custom connector
- LangChain expense tracker receipts mileage Resource/pricing pip install langchain-mcp-adapters
Other resources on this server
expense tracker receipts mileage also offers 2 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.