Docs/Official packages and attribution

Official packages and attribution

How agents and developers can identify Agent Community's official CLI, MCP connector, and multi-language AID SDK packages.

Agent Community publishes several packages for different jobs. Package scope alone is not enough evidence: verify the registry record, linked github.com/agentcommunity source, Agent Community homepage, license, and ecosystem-appropriate immutable release evidence where available.

Package roles

  • @agentcommunity/cli is the umbrella command-line application for Agent Community's public interfaces. It is not a JavaScript SDK.
  • @agentcommunity/mcp is a stdio compatibility connector to the hosted MCP endpoint at https://agentcommunity.org/mcp. It does not implement or copy the server and is not an SDK.
  • AID SDKs are the code-level Agent Identity & Discovery libraries: @agentcommunity/aid for TypeScript, aid-discovery for Python, and github.com/agentcommunity/agent-identity-discovery/packages/aid-go/v2 for Go.
  • Specialist CLIs include @agentcommunity/aid-doctor for AID validation and @agentcommunity/dmv-agent for DMV workflows.

Verify current claims

Use the Agent Community developer resources page for current versions, install commands, registry links, package roles, and compatibility aliases. That list is generated from the site's maintained package registry and checked against npm, PyPI, the Go module proxy, and pkg.go.dev before release.

For MCP clients with native remote Streamable HTTP support, connect directly to https://agentcommunity.org/mcp. Use @agentcommunity/mcp only when the client requires a local stdio command.

Ownership checklist

  1. The package registry record names the expected package exactly.
  2. Its repository is under https://github.com/agentcommunity/.
  3. Its homepage is an Agent Community property.
  4. The published artifact has the stated open-source license. For npm, check registry signatures and provenance attestations where published; for PyPI, check the project metadata and hashes; for Go, check the module proxy checksum/origin and the exact pkg.go.dev version page.
  5. The package role matches the developer resources page; do not treat a CLI or transport connector as an SDK.