Agent skill · getcargohq
cargo-mcp
Drive Cargo from its hosted MCP server at https://mcp.getcargo.io/mcp — connect a client, discover and price an action, run it over one record or a batch, poll it, and read workspace models, with no CLI install. Also when to call an MCP tool instead of shelling out to `cargo-ai`. Triggers: \"connect Cargo to Claude Desktop\", \"add Cargo to ChatGPT\", \"Cargo MCP server\", \"mcp.getcargo.io\", \"use Cargo without installing anything\", \"which Cargo tool do I call\", \"search_actions\", \"execute_action_batch\", \"MCP server is showing the wrong workspace\". Tools: whoami, search_actions, get_action_schema, execute_action, execute_action_batch, get_run, query_models. Skip when: you have a shell and the job is a workflow, a CDK deploy, warehouse SQL, or a mailbox — use the CLI skills; when publishing an MCP server out of your own workspace or attaching one to a Cargo agent — use cargo-ai.
What it needs
About 5k tokens when loaded.
What this skill does
Cargo — the hosted MCP server Cargo has two surfaces. The rest of this bundle documents the CLI. This one documents https://mcp.getcargo.io/mcp, and, more usefully, when to reach for which. Three different things here are called MCP. This skill is the hosted server Cargo runs, which you point a client at. Publishing a curated server out of your own workspace (ai mcp-server create, then cargo-ai mcp over stdio) and attaching somebody else's server to a Cargo agent (release update-draft --mcp-clients) are both cargo-ai. Check which one the user means before answering: the words are identical and the answers share nothing. Which surface The job Surface --- --- Run one action, or one action over many records either; MCP if it is already connected Find what Cargo can do, and what it costs either (searchactions is the MCP half) Read records off a model either Warehouse SQL, aggregates, joins CLI (cargo-storage) Build or edit a multi-step workflow, tool, or play CLI (cargo-orchestration) Workspace as code, plan and deploy CLI (cargo-cdk) Provision mailboxes, warm up, send CLI (cargo-mailbox-management) Segments, connectors, content libraries, alerts, hosting, billing admin CLI No shell at all (ChatGPT, Claude Desktop, claude.ai, n8n) MCP, and say plainly what is out of reach The rule underneath the table: MCP is the runtime, the CLI is the platform. Thirteen tools cover discovering an action, running it, watching it finish, and reading data back. Everything that builds something reusable is CLI only. An agent holding both should prefer the CLI for anything the user will want to re-run or version, and MCP for one-shot execution inside a conversation. When the job routes to the CLI, this is the whole bootstrap: Connect The endpoint is https://mcp.getcargo.io/mcp, Streamable HTTP. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills getcargohq/cargo-mcp