ivon CLI
Command-line access to the ivon Meta Ads connector — the same hosted MCP server that powers ivon's agents, wrapped in human-friendly commands.
Install
pip install ivon-cli # from PyPI (or pipx install ivon-cli)
pip install -e cli/ # from the repo root, for development
Login
ivon auth login # opens browser → Google sign-in on ivon.ai → done
ivon auth status # who am I + Facebook Ads connection state
ivon auth logout
Credentials are stored in ~/.ivon/credentials (0600). The token is your
long-lived ivon API token — regenerate it on https://ivon.ai/profile to
revoke all CLI / MCP access.
Meta Ads commands
ivon meta tools # list every MCP tool, grouped
ivon meta tools get_insights # one tool: params, defaults + example
ivon meta tools get_insights --json # same as JSON Schema (for agents)
ivon meta accounts # your ad accounts
ivon meta campaigns -a act_123 --status ACTIVE
ivon meta adsets -a act_123 -c <campaign_id>
ivon meta ads -a act_123
ivon meta insights act_123 -t last_7d --breakdown age
ivon meta call create_campaign -p account_id=act_123 -p name="Spring Sale" \
-p objective=OUTCOME_TRAFFIC -p status=PAUSED
ivon meta call <tool> -p key=value reaches any tool on the server —
values parse as JSON when possible (-p limit=25, -p targeting='{"geo_locations":{"countries":["US"]}}').
ivon meta tools reads a catalog snapshot bundled with the CLI, so discovery
is instant and works before login; --refresh re-fetches from the live
server. Refresh the bundled snapshot with scripts/snapshot_cli_tools.py
after changing the backend's tool surface.
MCP client setup
ivon mcp config # prints Claude Code / Claude Desktop config
ivon mcp config --show-token # same, with your real token embedded
Environment overrides
IVON_API_URL— point at a different backend (loopback allowed for dev; other hosts needIVON_ALLOW_CUSTOM_API=1).IVON_CONFIG_DIR— credentials directory (default~/.ivon).
Metadata
Release files for ivon-cli 0.2.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 | Actions |
|---|---|---|---|---|
| ivon_cli-0.2.2.tar.gz | 39.4 kB | Without provenance | Details for ivon_cli-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ivon_cli-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for ivon_cli-0.2.2-py3-none-any.whl |
Total release size: 81.9 kB
Release files / ivon_cli-0.2.2.tar.gz
| Download URL | ivon_cli-0.2.2.tar.gz |
|---|---|
| Size | 39.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
456239762433c463c35721a1c9f71df010e91ba0709a408e285c6913e54b9493
|
|
BLAKE2b-256 checksum How to use checksums |
2c2333c9ed61302f8a7ed25bc2532e8b1f0964ded42455377bcef1b21d29c8ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / ivon_cli-0.2.2-py3-none-any.whl
| Download URL | ivon_cli-0.2.2-py3-none-any.whl |
|---|---|
| Size | 42.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3765eee3568c4567fe84f4bf5e7159e3c08e534ed616dd7e1da8f33a28b5737f
|
|
BLAKE2b-256 checksum How to use checksums |
faef2bba2059786ccf10b904a84d6634158891eb0d0a431a25255865145ef708
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for ivon-cli 0.2.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.