mcp.getcargo.io/mcp is live and serves thirteen platform tools plus
whatever a workspace published with defineMcpServer. Nothing in the
bundle covered it, and cargo/SKILL.md asserted "There is no first-party
'Cargo MCP server'" - true when written, wrong now, and the one claim an
agent would act on.
- cargo-mcp/SKILL.md (1.0.0): connect, the discover to price to execute
to poll spine, and the routing table for MCP tool vs cargo-ai.
- cargo/SKILL.md (1.22.0): the MCP section becomes a three-way
disambiguation. Hosted server, workspace server served over stdio by
cargo-ai mcp, and an MCP client attached to a Cargo agent are three
things sharing a name and sharing no answers.
- evals/routing.jsonl: "How do I use Cargo from ChatGPT?" now expects
cargo-mcp; three cases added for the new surface.
- Counts, catalogs, plugin manifests, SKILL_DIRS, llms.txt, metadata.
skills-lint, routing-eval, sync-trigger-slugs and the cargo-gtm script
fixtures all pass.
Co-authored-by: Cargo FSD <fsd@getcargo.io>
Co-authored-by: Auree Aubert <16732193+aureeaubert@users.noreply.github.com>
Co-authored-by: replicas-connector[bot] <replicas-connector[bot]@users.noreply.github.com>
`mailboxManagement` landed in the CLI (cargo#5493, plus warm-up stats in
cargo#5646) and nothing in the bundle covered it. It is the first domain
that makes Cargo own the inbox, so the gap was not one more capability
skill — it was a skill whose absence let an agent send mail with no idea
what it cost or what governed it.
- New `cargo-mailbox-management` (the fifteenth capability skill): six
command groups, the send that is deliberately not in them, and four
references — the ramp arithmetic and fleet sizing, the `sendEmail`
action, response shapes, troubleshooting — plus eight worked recipes.
- The two facts an agent gets wrong without it. A mailbox is a recurring
monthly credit charge (100-160 per mailbox per month), not a per-record
one, and `mailbox remove` is the only way to stop it. And volume is a
ramp, not a setting: 5/day to 40/day over 45 days from `warmupStartedAt`,
pinned at 5/day forever if warm-up never started, reset to day 0 by
`stop-warmup`, and `dailySendLimit` can only tighten it.
- `cargo-gtm`'s acceptable use said the pack never sends. That paragraph
is the substance of the plugin-directory remedy, and mailboxManagement
made it false. Section 1 now says what is true, section 6 names the ramp
and calls spreading one campaign across extra mailboxes what it is, and
section 7 cross-references the new skill.
- `cargo-cdk` gained `defineMailbox` and `defineDomain` in the same release
and had documented neither. Both are now in the builder table with the
create-only, monthly-fee and whole-zone rules that bite.
- Known gap, filed rather than papered over: `mailbox create --domain-uuid`
is required and no command lists sending domains.
Counts move 17 to 18 across the router, README, AGENTS, CONTRIBUTING and
the manifests. Seven new routing cases, two of them hard-tier negatives
pinning the boundary the word "email" blurs. Core tier 93/93; lint,
metadata, llms.txt, trigger slugs, cookbooks and hooks all clean.
Claude-Session: https://claude.ai/code/session_01TF1ZRweJqqnPeGbVmUeGkY
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
"Email finding" is the phrasing that drew the OpenAI spam rejection on
cargo-gtm, and it sat unchanged in the three channel plugin descriptions
and the root manifest blurb -- the copy a reviewer or a user reads before
anything else. It also misdescribes the product: the CLI queries licensed
data providers and verifies what comes back, which is the part that makes
the difference to whoever is deciding whether this is a scraper.
Channel descriptions now say "contact enrichment and verification from
licensed data providers" and name lead scoring, replacing "enrichment,
email finding". The root manifest picks up the blurb merged in #91, so
all five manifests finally describe the same product.
No version bump: marketplace copy only, no skill content, and the OpenAI
archive does not contain these files -- verified by diffing an archive
built with and without this change (identical, only zip mtimes differ).
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
owner.url / author.url in the three marketplace and plugin manifests were the
last places linking the brand at getcargo.io. README.md and the docs link
already use getcargo.ai.
app.getcargo.io and api.getcargo.io are left as-is on purpose: neither has a
.ai equivalent in DNS, and they are live hosts the skills depend on.
Co-authored-by: Auree Aubert <16732193+aureeaubert@users.noreply.github.com>
Co-authored-by: replicas-connector[bot] <replicas-connector[bot]@users.noreply.github.com>
The repo already installs cleanly through every channel (skills.sh, Claude
Code, Codex, Cursor), but it cannot be *listed* in the curated directories.
Three concrete review blockers, none of which need an MCP server:
- No LICENSE. Cursor requires every listed plugin to be open source; a public
repo with no license file is legally all-rights-reserved.
- No logo. Cursor's submission checklist requires one committed to the repo
and referenced by relative path.
- No root plugin.json. Cursor's checklist requires Agent Plugins to conform to
the published schemas; the portable manifest is also what ChatGPT, Copilot,
VS Code and Kiro read.
Validated against the published schema: both required fields present, only the
ten permitted top-level fields used, additionalProperties respected. The skill
linter passes with 0 errors.
Co-authored-by: Auree Aubert <16732193+aureeaubert@users.noreply.github.com>
Co-authored-by: replicas-connector[bot] <replicas-connector[bot]@users.noreply.github.com>
replicas-connector[bot]