Office hours: Build your self-driving GTM engine·Oct 29, 9:00am PT, onlineRegister→
Cargo
  • PrimitivesData ModelsYour companies, contacts and deals, merged from every sourceContextWhat your team knows, as files every agent readsTerritoriesWho sells where, defined onceMailboxesMailboxes in your reps' names, warmed up and kept under limitsToolsThe actions your agents, plays and reps callAgentsAI that researches, decides and writes, reading your contextPlaysWorkflows that run on a trigger or a schedule, with retriesAppsInternal apps for your reps, hosted on Cargo
    Add-onsChrome ExtensionSell faster, right in your browserButtonTrigger AI agents inside your CRMFormTurn any tool into an embeddable formSlackTag Cargo in Slack. It does the GTM workGitHubPlan on every pull request, deploy on merge
    MoreProjectsDefine your entire GTM in codeCLIUse Cargo from your terminalMCPUse Cargo from Claude and ChatGPTDeveloper resourcesCargo API docs, OpenAPI spec, auth docs, webhooks, MCP serverAPI ReferenceExplore the Cargo APIDocumentationLearn how to use CargoIntegrationsConnected to your entire GTM stack
  • VeriffHow Veriff replaced MuleSoft with Cargo under NetSuite, Stripe and SalesforceAugmentHow Augment Code routes developer sign-ups to reps in under an hourWeights & BiasesHow Weights & Biases ships a new purchase signal in 2 days on CargoSee all
  • Pricing
  • Cookbooks
  • Blog
Sign in
Blog

Run Go-to-Market from Codex, Cursor or OpenCode

16 Oct5min read
AurelienAurelien

Codex, Cursor and OpenCode run go-to-market work with Cargo the same way: install the cargo-ai CLI, sign in with cargo-ai login --email, install the Cargo skills for your agent, and ask for the job. Only three things change from one agent to the next: the flag on the skills installer, whether a plugin is available, and where the MCP server is configured. This page gives one setup and a table for the differences.

The shared part #

shellscript
npm install -g @cargo-ai/cli
cargo-ai login --email you@company.com                 # sends a code, then exits
cargo-ai login --email you@company.com --code 123456
cargo-ai whoami                                        # must name a user and a workspace

Sign-in runs in the terminal, with no browser, and creates the account on first use. A new account starts with 100 free credits and no card. The CLI recognises when Codex, Cursor or OpenCode launched it and never opens an interactive prompt there, so an agent session cannot hang on a picker.

Or paste one line into the agent and let it do all of this:

text
Install Cargo by following https://api.getcargo.io/INSTALL.md

What differs per agent #

CodexCursorOpenCode
Skills install--agent codex--agent cursor--agent opencode
Global skills directory~/.agents/skills~/.cursor/skills~/.config/opencode/skills
Cargo pluginYesYesNo, skills only
MCP config~/.codex/config.toml~/.cursor/mcp.json or .cursor/mcp.json~/.config/opencode/opencode.json or opencode.json

The skill files themselves are identical everywhere: plain SKILL.md folders, the same ones Claude Code uses.

Install the skills #

One command, with your agent’s flag:

shellscript
npx skills add getcargohq/cargo-skills --agent codex -g -y      # Codex
npx skills add getcargohq/cargo-skills --agent cursor -g -y     # Cursor
npx skills add getcargohq/cargo-skills --agent opencode -g -y   # OpenCode

Drop -g to install into the current project (.agents/skills) instead of your home directory. For one job rather than the whole platform, install a job-named skill such as find-work-email: npx skills add getcargohq/gtm-skills/find-work-email.

The plugin, on Codex and Cursor. Both agents can also install Cargo as a plugin, which carries the same skills plus an approval hook: read-only cargo-ai calls run without a prompt, while sign-in, token minting, deploys and deletions still ask. On Codex, run codex plugin marketplace add getcargohq/cargo-skills, then install “cargo” from the Plugins menu. On Cursor, open Customize in the sidebar, add the getcargohq/cargo-skills marketplace and install Cargo. Use the plugin or skills add, not both, or every skill registers twice. OpenCode has no Cargo plugin, so the skills are the whole install there.

Connect the MCP server (optional) #

The skills drive the CLI, which covers everything. The MCP server lets the agent search, price and run actions and read data models as tool calls. cargo-ai mcp serves it over stdio with the credentials you signed in with, so no token goes in the config file.

Codex:

shellscript
codex mcp add cargo -- cargo-ai mcp

which writes this to ~/.codex/config.toml:

toml
[mcp_servers.cargo]
command = "cargo-ai"
args = ["mcp"]

Cursor, in ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

json
{
  "mcpServers": {
    "cargo": {
      "command": "cargo-ai",
      "args": ["mcp"]
    }
  }
}

Cursor can also connect to the hosted server over HTTP and sign in with OAuth: use "url": "https://mcp.getcargo.io/mcp" in place of command and args.

OpenCode, in opencode.json at the project root or ~/.config/opencode/opencode.json:

json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cargo": {
      "type": "local",
      "command": ["cargo-ai", "mcp"],
      "enabled": true
    }
  }
}

The tools the server exposes are listed in the MCP server docs; the Cargo MCP server page covers the hosted endpoint and curated servers.

Run a first job #

Ask in plain words, for example “Find the work email for Jane Doe at acme.com”. The agent loads the work-email skill and runs prospeo.findEmail through the CLI, at 0.5 credits per record, returning the address or an empty value when nothing resolves. Across Cargo, work-email lookups ran 1,850,404 times and 63.6% of runs returned an address (Cargo platform data, 90 days to Oct 16 2026), so sample 10 to 20 records before a full list.

The full walkthrough of that job, with the exact command and what comes back, is in run go-to-market from Claude Code; every step after sign-in is the same in these three agents. When the job should run on its own, have the agent declare it as code with cargo-ai project init, as described in run go-to-market with coding agents.

Frequently asked questions #

No. The skills are the same SKILL.md files for every agent. Only the install flag changes: npx skills add getcargohq/cargo-skills --agent codex, --agent cursor or --agent opencode, which puts them in the directory that agent reads.

Run codex mcp add cargo -- cargo-ai mcp after signing in with the CLI. It adds an [mcp_servers.cargo] entry to ~/.codex/config.toml that starts cargo-ai mcp, which uses the CLI’s own credentials.

Add a cargo entry under mcpServers in ~/.cursor/mcp.json with "command": "cargo-ai" and "args": ["mcp"], or point it at https://mcp.getcargo.io/mcp with "url" and sign in with OAuth.

Add a cargo entry under mcp in opencode.json with "type": "local", "command": ["cargo-ai", "mcp"] and "enabled": true.

No. Codex, Cursor and Claude Code have a Cargo plugin that adds an approval hook on top of the skills. On OpenCode, install the skills with npx skills add getcargohq/cargo-skills --agent opencode -g -y; they work the same, and cargo-ai commands go through OpenCode’s own permission prompts.

~/run-it-on-cargo/

Build this workflow instead of reading about it.

Cargo is the GTM infrastructure your coding agent builds on: enrichment, scoring, routing and outreach, defined in code and run in production.

Start building
AurelienAurelienOct 16, 2026
On this page
  • The shared part
  • What differs per agent
  • Install the skills
  • Connect the MCP server (optional)
  • Run a first job
  • Frequently asked questions

Stay Informed with our
weekly Newsletter

Related articlesSee all articles
GTM Engineering
CI/CD for Go-to-Market: What It Means and How to Set It Up

CI/CD for GTM means every change to enrichment, scoring, routing and sequences ships as a pull request that is planned, checked, approved, deployed on merge, logged and reversible. What each software CI/CD step becomes for go-to-market, and how to set it up on Cargo.

AurelienAurelien·Nov 3, 2026
GTM Engineering
Require Approval Before a High-Impact Go-to-Market Change Goes Live

How Cargo holds a go-to-market pull request that would send or spend more than set limits until a reviewer adds the cargo:approve-impact label: the thresholds, what counts as high impact, who should approve, and what the gate does not catch.

AurelienAurelien·Nov 3, 2026
GTM Engineering
Test a Go-to-Market Change Before It Reaches Production

How to test a change to enrichment, scoring, routing or outreach before it runs on every lead: check the project offline, dry run an action, read the plan on the pull request, ship the play switched off and pilot it on 50 records, evaluate agents, and use a second workspace as staging.

AurelienAurelien·Nov 3, 2026

Build the self-driving GTM engine

Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.

Start building
Cargo
Backed byY CombinatorSOC 2 Type IICertified
LinkedinX

Product

Data ModelsContextTerritoriesMailboxesToolsAI AgentsPlaysAppsIntegrationsPricing

Add-ons

Chrome extensionButtonFormSlackGitHub

Build

DocsDeveloper resourcesCargo API docsCargo OpenAPI specCargo auth docsCargo webhooksCargo MCP serverProjectsClaude CodeCodexCursorAll coding agents

Resources

ReportsBlogCustomer storiesCookbooksEnrichmentRoutingSignalsScoringCRM hygieneAd audiencesGTM skillsGTM EngineeringGlossaryCompareCargo x ClayCargo x WorkatoCargo x n8nCargo x DeeplineCargo x DefaultCargo x LeanDataCargo x UnifyCargo x ValleyCargo x Gojiberry

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

SecurityTerms of servicePrivacy PolicyRefundsDPASupport
© 2026 Cargo
 ////////    ///////    ////////     ////////    ///////
///         ///   ///   ///   ///   ///         ///   ///
///         ///   ///   ///   ///   ///         ///   ///
///         /////////   ////////    ///  ////   ///   ///
///         ///   ///   /// ///     ///   ///   ///   ///
///         ///   ///   ///  ///    ///   ///   ///   ///
 ////////   ///   ///   ///   ///    ///////     ///////

$ npm install -g @cargo-ai/cli