📝Cargo exposes workspace tools, agents, data models, and connector actions as 📝Model Context Protocol (MCP) servers — making the full GTM automation layer callable from any MCP client (Claude Code, Claude Desktop, Cursor, etc.).
Cargo's MCP works bidirectionally. As a server, it exposes a workspace's tools, agents, and data to external AI clients. As a client, it connects external MCP servers into Cargo agents via the connect-mcp-client API endpoint. What gets exposed falls into two categories: actions (tools, agents, and connector integrations like HubSpot or Salesforce) and resources (data models with optional filtering and files stored in the workspace).
Setup paths include a skills-based CLI (@cargo-ai/cli via skills.sh), direct API-driven MCP server creation, and remote SSE connections using mcp-remote for clients that can't set custom Authorization headers natively. The CLI provides commands across runtime execution, schema management, connectors, agents, measurement, costs, and admin.
Cargo is a core component of the 📝One Inc GTM engineering stack, providing the automation and enrichment layer that feeds into prospecting and outreach workflows.