Toshl MCP
Author: Fedele Mantuano
MCP server that connects Codex, ChatGPT Desktop, Claude Desktop, and other local MCP clients to the Toshl Finance API. Transport: stdio. Auth: Toshl Personal Token via HTTP Basic Auth.
Tools
| Tool | Description |
|---|---|
get_accounts |
List accounts with balances |
get_entries |
List transactions with date range, category, tag filters |
get_categories |
List expense/income categories |
get_tags |
List tags |
get_budgets |
List budgets with current spending status |
get_summary |
Toshl summary totals and averages for a date range |
get_accounts
Returns all Toshl accounts, including archived accounts. Each result includes the account name, current and initial balances, currency, type, and status.
get_entries
Returns transactions between the required inclusive from_date and to_date
arguments, both in YYYY-MM-DD format. The optional category argument filters
by category ID, while tags accepts comma-separated tag IDs.
Each entry includes its amount, currency, date, description, account, category, and tags.
get_categories
Returns expense and income categories. Use the optional type argument with
expense or income to return only that category type; omit it to return both.
Each category includes its ID, name, type, and deletion status.
get_tags
Returns all user-defined Toshl tags. Each tag includes its ID, name, and whether it applies to expenses or income.
get_budgets
Returns all budgets with their limits and current spending status. Each budget includes its ID, name, limit, amount spent, currency, and inclusive start and end dates.
get_summary
Returns expense and income aggregates from Toshl's summary endpoint. The
from_date and to_date arguments use YYYY-MM-DD and are both inclusive.
Use the optional currency argument to request a specific output currency;
when omitted, Toshl uses the user's main currency.
The result contains from_date, to_date, total_expenses, total_income,
net, avg_daily_expense, period_days, and entry_count. entry_count
combines Toshl's expense and income counts, and the daily average uses the
inclusive number of days in the range.
Requirements
- Python 3.11 or newer
- uv
- Toshl Personal Token — generate at Toshl → Profile → Apps & tokens
Installation
The examples below use macOS paths. Install the package once, then configure each client that should use it.
1. Install uv (if not already installed):
curl -LsSf https://astral.sh/uv/install.sh | sh
2. Install the package into a dedicated virtualenv:
With uv:
uv venv ~/.toshl-mcp
uv pip install --python ~/.toshl-mcp/bin/python toshl-mcp
Or with pip:
python3 -m venv ~/.toshl-mcp
~/.toshl-mcp/bin/pip install toshl-mcp
Codex CLI and IDE
Add the following to ~/.codex/config.toml, keeping your existing settings:
[mcp_servers.toshl]
command = "/Users/<your-username>/.toshl-mcp/bin/toshl-mcp"
[mcp_servers.toshl.env]
TOSHL_TOKEN = "<your-toshl-personal-token>"
Replace <your-username> with your macOS username (run whoami to confirm)
and the token placeholder with your Toshl Personal Token. Keep this
configuration in your user directory; it contains your token.
Alternatively, register the same server with the CLI:
codex mcp add toshl \
--env TOSHL_TOKEN="<your-toshl-personal-token>" \
-- "$HOME/.toshl-mcp/bin/toshl-mcp"
Choose either the TOML configuration or the CLI command. Both configure the same server. Codex CLI and the IDE extension share this configuration. Start a new CLI session or restart the IDE extension after configuring it.
Verify registration:
codex mcp list
Then use /mcp in Codex CLI to check that toshl is connected. Registration
alone does not verify that the server starts or that the token is valid.
See the official Codex MCP documentation.
ChatGPT Desktop
For local Codex sessions in ChatGPT Desktop, use the same
~/.codex/config.toml configuration shown above. Desktop, Codex CLI, and the
IDE extension share MCP configuration on the same Codex host, so configuring
toshl once is sufficient.
To add the server through the Desktop interface instead:
- Open Settings → MCP servers → Add server.
- Enter
toshlas the name and select STDIO. - Set the command to
/Users/<your-username>/.toshl-mcp/bin/toshl-mcp. - Save the server.
- Ensure the
[mcp_servers.toshl.env]table in~/.codex/config.tomlcontainsTOSHL_TOKEN, as shown above. - Save the TOML file and select Restart in the MCP settings.
Use /mcp in the composer to check that the server is connected. This setup
provides the local MCP server in the Codex host; ChatGPT web and hosted
Chat/Work conversations use their own plugin connections.
See the official Desktop MCP documentation.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"toshl": {
"command": "/Users/<your-username>/.toshl-mcp/bin/toshl-mcp",
"env": {
"TOSHL_TOKEN": "<your-toshl-personal-token>"
}
}
}
}
Replace <your-username> with your macOS username (run whoami to confirm).
Replace the token placeholder with your Toshl Personal Token, then restart
Claude Desktop.
Verify the connection
After restarting your client, ask it to use Toshl's get_categories tool.
A successful tool response verifies both the MCP connection and Toshl
authentication. The server exposes all six tools listed above.
If the server fails to start, check the absolute executable path and that
TOSHL_TOKEN is set in the client configuration. The server reads environment
variables; installing the package does not configure a token automatically.
Updating
Upgrade in place — use the same tool you installed with.
With uv:
uv pip install --python ~/.toshl-mcp/bin/python --upgrade toshl-mcp
Or with pip:
~/.toshl-mcp/bin/pip install --upgrade toshl-mcp
Then restart the MCP server in each client that uses it: start a new Codex CLI session, restart the IDE extension, select Restart in ChatGPT Desktop's MCP settings, or restart Claude Desktop. A running server process keeps the old version until it is restarted.
Check the installed version:
~/.toshl-mcp/bin/python -c "import toshl_mcp; print(toshl_mcp.__version__)"
Compare it against the latest release on PyPI.
Client configuration does not need to change — the path to the executable stays the same across upgrades.
Note:
uv venvdoes not installpipinto the virtualenv, so~/.toshl-mcp/bin/pipexists only if you used the pip install path.
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
TOSHL_TOKEN |
Yes | — | Toshl Personal Token |
LOG_LEVEL |
No | WARNING |
Logging level (DEBUG, INFO, WARNING, ERROR) |
Development
Agent instructions
CLAUDE.md is the source of the repository instructions.
AGENTS.md is a relative symbolic link to CLAUDE.md, so Claude Code and
Codex read the same instructions. Edit CLAUDE.md to update both.
Setup
1. Install uv (if not already installed):
curl -LsSf https://astral.sh/uv/install.sh | sh
2. Install all dependencies:
uv sync --all-groups
3. Install pre-commit hooks:
make pre-commit
Make commands
make install # install dependencies
make lint # check code
make lint-fix # check and auto-fix
make format # format code
make test # run tests
make test-cov # run tests with coverage report
make pre-commit # run all pre-commit hooks
make dev # start MCP inspector (requires .env)
make clean # remove build artifacts and caches
Note:
make pre-commitchecks all tracked files, including unstaged changes.
Testing with MCP Inspector
The MCP Inspector lets you call tools interactively in a browser.
1. Create a .env file in the project root:
TOSHL_TOKEN=your-personal-token-here
2. Start the inspector:
make dev
3. Open http://localhost:6274 in your browser.
4. Connect — click Connect in the top bar.
5. Test tools:
- Click Tools in the left sidebar
- Click List Tools to see all six tools
- Select a tool (e.g.
get_accounts), fill in any parameters, click Run
Metadata
Release files for toshl-mcp 1.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| toshl_mcp-1.1.2.tar.gz | 92.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| toshl_mcp-1.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 106.6 kB
Release files / toshl_mcp-1.1.2.tar.gz
| Download URL | toshl_mcp-1.1.2.tar.gz |
|---|---|
| Size | 92.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa96385fdbea921d0add756ff0735018453c8393217ee24862c11bfef198bf66
|
|
BLAKE2b-256 checksum How to use checksums |
c01ed72531616069664a4dd03ddf32d5f7c8119e29d7a1ca5c6e678ad2ccaefe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / toshl_mcp-1.1.2-py3-none-any.whl
| Download URL | toshl_mcp-1.1.2-py3-none-any.whl |
|---|---|
| Size | 14.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5599d0d563dc89e83cba9b6a3407bd0146fd5802280152e585dde47c7fd785d
|
|
BLAKE2b-256 checksum How to use checksums |
45a1e433ee89bba8c8e166dd42a87f5137c7bbdd010f692e77976a28185d70a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for toshl-mcp 1.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.