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 project 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.
getcargo · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add getcargohq/cargo-skills --skill cargo-mcp技能说明
name: cargo-mcp
description: "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 project 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."
version: "1.1.1"
compatibility: Requires the hosted Cargo MCP server at https://mcp.getcargo.io/mcp — OAuth (discovered from the 401 challenge) or a workspace-scoped API token as a bearer. The CLI is needed only for the jobs this skill routes away
homepage: https://github.com/getcargohq/cargo-skills
metadata:
author: getcargo
openclaw:
requires:
bins:
- cargo-ai
install:
- kind: node
package: "@cargo-ai/cli@latest"
bins:
- cargo-ai
homepage: https://github.com/getcargohq/cargo-skills
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, thencargo-ai mcpover stdio) and attaching somebody else's server to a Cargo agent (release update-draft --mcp-clients) are bothcargo-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 (search_actions is the MCP half) |
| Read records off a model | either |
| One SELECT over models (aggregates, joins), 50 rows max | either (query_models is the MCP half) |
| Full SQL result sets, exports | CLI (cargo-storage) |
| Build or edit a multi-step workflow, tool, or play | CLI (cargo-orchestration) |
| GTM as Code: project plan and deploy | CLI (cargo-project) |
| 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. Seventeen tools cover discovering an action, running it, watching it finish, reading data back, and reading the workspace context. 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:
npm install -g @cargo-ai/cli
cargo-ai login --email you@company.com # emailed code, no browser; creates the account on first use
cargo-ai whoami # confirm the workspace before anything that spends
Connect
The endpoint is https://mcp.getcargo.io/mcp, Streamable HTTP. An
unauthenticated request returns 401 with a WWW-Authenticate challenge
carrying resource_metadata, so an OAuth-capable client discovers the
authorization server, registers, and prompts the user with no configuration
beyond the URL. A 401 on first connect is the handshake, not a fault.
claude mcp add --transport http cargo https://mcp.getcargo.io/mcp
Any client taking a JSON block (Claude Desktop, Cursor, a project .mcp.json):
{
"mcpServers": {
"cargo": {
"type": "http",
"url": "https://mcp.getcargo.io/mcp"
}
}
}
For CI, a headless agent, or a client with no OAuth, pass a workspace-scoped API token from Settings > API instead. Read it from the environment; never inline the value:
{
"mcpServers": {
"cargo": {
"type": "http",
"url": "https://mcp.getcargo.io/mcp",
"headers": { "Authorization": "Bearer ${CARGO_API_TOKEN}" }
}
}
}
This endpoint serves the platform tools only. A curated server a workspace
published with defineMcpServer is a different endpoint, at its own
/v1/ai/mcpServers/<uuid>/mcp URL. Every token sees the same platform tools
here; the token's permissions decide which calls succeed and which actions
search_actions returns.
The spine
whoami → which workspace am I in, how many credits
search_actions → find the action, and read its cost
get_action_schema → what inputs it takes
autocomplete_action → resolve a field needing a picked id (HubSpot object type, Slack channel)
execute_action │ one record
execute_action_batch │ many records
get_run / get_batch → poll while outcome is "executing"
For data: list_models → describe_model → query_models. For the workspace
context (read only): map_context, search_context, browse_context,
read_context. Alongside,
list_runs lists recent ad-hoc runs, and get_usage breaks the last 7 days of
credit spend down by integration.
**Open eve
阅读完整来源 ↗