API, CLI and MCP
The same actions are available three ways: the REST API directly, the CLI, and the MCP server for Claude and other agents. This is the map between them.
Why the names differ#
They are not three spellings of one scheme — each surface follows the convention its callers expect. An agent picks a tool by reading its name, so MCP tools are verb-first and self-describing (get_credit_balance). A CLI groups subcommands under a noun so related work sits together (cornect export create, … status, … download). REST addresses resources by path (GET /credits).
Renaming any of them to match the others would break published agent configurations and shipped scripts to buy consistency a table provides for free. So: the table.
The map#
| Action | REST | MCP tool | CLI |
|---|---|---|---|
| Search companies | POST /companies/search | search_companies | cornect search |
| Count matches exactly | POST /companies/counts | count_companies | cornect count |
| Get one company | GET /companies/{company_id} | get_company | cornect company get |
| List a company's job postings REST only for now — a CLI command and an MCP tool are planned. | GET /companies/{company_id}/job-postings | — | — |
| Check credit balance | GET /credits | get_credit_balance | cornect credits |
| Price an export before paying | POST /exports/preview | preview_export | cornect export preview |
| Create an export | POST /exports | create_export | cornect export create |
| Check export status | GET /exports/{export_id} | get_export_status | cornect export status |
| Get a download link | POST /exports/{export_id}/download | download_export | cornect export download |
| Find new leads | GET /leads | find_new_leads | cornect leads list |
| Get one company's recent signals GET /leads with domain and per_company=false. | GET /leads | get_company_signals | cornect leads company |
| Count new leads by kind | GET /leads/summary | get_leads_summary | cornect leads summary |
| Count new leads for the narrowing filters The MCP tool and the CLI command ask for every facet with the summary. | GET /leads/facets | get_leads_summary | cornect leads summary |
| List signals your monitors delivered | GET /signals | list_signals | cornect signals list |
| Count delivered signals | GET /signals/summary | get_signals_summary | cornect signals summary |
| Export signals as CSV A CSV file is for a person or a script, not an agent: no MCP tool. | GET /signals/export | — | cornect signals export |
| List monitors | GET /monitors | list_monitors | cornect monitors list |
| Create a monitor | POST /monitors | create_monitor | cornect monitors create |
| Get one monitor | GET /monitors/{monitor_id} | get_monitor | cornect monitors get |
| Update, pause or resume a monitor | PATCH /monitors/{monitor_id} | update_monitor | cornect monitors update |
| Delete a monitor | DELETE /monitors/{monitor_id} | delete_monitor | cornect monitors delete |
| Add a company to a monitor | POST /monitors/{monitor_id}/domains | add_company_to_monitor | cornect monitors add |
| Remove a company from a monitor | DELETE /monitors/{monitor_id}/domains/{domain} | remove_company_from_monitor | cornect monitors remove |
| List a monitor's runs | GET /monitors/{monitor_id}/runs | list_monitor_runs | cornect monitors runs |
| Get one run, check by check | GET /monitors/{monitor_id}/runs/{run_id} | get_monitor_run | cornect monitors run |
Not every action exists everywhere. Where a cell is empty the action is reachable through the REST API and the others have not caught up — shown rather than omitted, so a gap is something you can see instead of something you discover.
Which one to use#
REST when you are building software against Cornect. CLI for scripts, CI and one-off work from a terminal — every command speaks JSON and CSV. MCP when you want Claude to do the work for you. All three authenticate with the same cornect_ token and spend credits identically: searching, counting, Find New Leads and reading signals are free; exports charge per new company, and monitors charge per company and signal type on each daily run.