MANIFEST.md and the checked-in community catalog; the live, machine-readable roster for your session is always pidgeon://version.
Community tools (CLI mode)
WithPIDGEON_MODE=cli — no account, no Bridge — the server registers exactly these eleven tools: the ones the free CLI’s command catalog can service end to end. Nothing else appears; a Pro tool never materializes from a client-side label.
generate_message in CLI mode is single-patient and volume-capped, with graceful degradation as you approach the cap — never a hard failure that breaks an agent loop.Free tools added in Bridge mode
WithPIDGEON_MODE=bridge and a running desktop app, the Bridge advertises the full free tier — the eleven community tools plus these two (their substrate runs in the Bridge, so the CLI alone can’t service them):
NCPDP validation through
validate_message depends on the license-gated ncpdp-script package (NCPDP membership required). See Message Generation.Pro tools
These nine are server-advertised only after authentication, for a resolved subscription tier. They require a Pidgeon account with an active subscription — the Agentic Seat ($49/mo per developer or agent seat), or usage-metered credits.How the split is enforced
The community set is a checked-in, fail-closed allowlist — registration by reflection or filesystem discovery is forbidden for the public composition. In Bridge mode the server registers exactly what the Bridge advertises for your tier; when a tier changes, the advertisement refreshes and newly entitled tools unlock. There is no way to surface a tool the active composition doesn’t include.Next steps
- MCP Server overview — install, transport modes, prompts, and resources
- Your Pidgeon account — plan and entitlements
