cogny cliemail & crofirst 15 calls free
symplify scriptable from Bash.
List custom properties, journeys, snippets and webhooks, look up contacts and their subscription status, and kick off async statistics exports — from the shell over the Symplify MCP. No REST client to wire up.
- 1. sign up, free for the first calls (uses your git email)
npx @cogny/cli init --agent claude-code - 2. see every Symplify tool
cogny tools list - 3. call any tool from bash, no MCP wiring
cogny tools call mcp__Symplify__start_statistics_export --input '{…}'
Today you open Symplify to check a contact’s subscription status or read per-message stats screen by screen. With the CLI you look up a contact and start a statistics export as JSON, then poll the batch from a script. Connect Symplify once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.
Start SoloSign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Symplify tool over JSON-RPC. The first 15 calls are free.
npx @cogny/cli init --agent claude-code
real Symplify tools.
Tool names as the Symplify MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.
- mcp__Symplify__start_statistics_export
Start an async per-message statistics export; returns a batchId.
cogny tools call mcp__Symplify__start_statistics_export \ --input '{"export_type":"OPENS","period":"LAST_WEEK"}'
example response
{ "batchId": "b-7f3a91", "status": "PENDING" } - mcp__Symplify__get_contact
Fetch a contact by list id and external original id.
cogny tools call mcp__Symplify__get_contact \ --input '{"list_id":4021,"original_id":"crm-88142"}'
example response
{ "originalId": "crm-88142", "email": "ada@example.com", "properties": { "firstName": "Ada", "country": "SE" }, "subscribed": true } - mcp__Symplify__list_journeys
List all journeys (triggered/transactional flows).
cogny tools call mcp__Symplify__list_journeys \ --input '{}'
example response
{ "journeys": [ { "id": 311, "name": "Welcome flow", "status": "ACTIVE" }, { "id": 327, "name": "Abandoned cart", "status": "ACTIVE" } ] }
the rest of the surface.
A sample of the other Symplify tools. Run cogny tools list --json for every tool and its input schema.
- mcp__Symplify__list_properties
- mcp__Symplify__get_property
- mcp__Symplify__get_contact_subscription_status
- mcp__Symplify__list_contact_messages
- mcp__Symplify__list_snippets
- mcp__Symplify__list_webhooks
- mcp__Symplify__get_batch_status
- mcp__Symplify__get_batch_result
calls from a script. verdicts from cogny.
Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.
- worked
Moved the number. Every measured win has a share card.
- partial
Some of it did.
- didn't work
On the record anyway, so it isn't proposed again.
- inconclusive
Not enough data to call.
questions.
- Is this an official Symplify CLI?
- No — it is the Cogny CLI calling the Symplify MCP over the cogny-mcp-proxy. You connect Symplify once in Cogny, and then every tool is callable from Bash with your Cogny key.
- How do statistics exports work?
- They are async. `start_statistics_export` returns a batchId; poll it with `get_batch_status` until status is FINISHED, then fetch rows with `get_batch_result`. The window is capped at two weeks — for a full month, use the Symplify → BigQuery sync.
- Why is there no list-all-contacts tool?
- The Symplify API has no list-all-contacts endpoint, so the MCP fetches contacts per list id + originalId via `get_contact`. For bulk contact analysis, run statistics exports or use the BigQuery sync.
Building an agent? The full tool map for every server is one fetch: /cli/llms.txt