Skip to content

v0.8.0

Choose a tag to compare

@keysersoft keysersoft released this 14 Sep 14:57
7b8020e

This release is about what the project says about itself. No behaviour changes to the gateway, one copy fix that mattered, and a new install path.

The numbers and the licence now agree

The adapter count appeared as nine different numbers across the repo, the website and the directories, and the README banner had SOURCE-AVAILABLE 路 36+ CONNECTORS baked into the pixels four months after both stopped being true.

scripts/adapter-count.mjs --check now runs in CI and fails the build if README.md, glama.json, server.json, CITATION.cff, package.json, the issue-template config or the publish workflow quote a count that disagrees with the catalog, or if "BSL", "source-available" or "non-commercial" reappears outside the files that legitimately describe the pre-AGPL history.

Real numbers, generated: 188 adapters, 26 of which need no API key, 1,814 tools.

Install without cloning

mkdir anythingmcp && cd anythingmcp
curl -fsSLo docker-compose.yml \
  https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Pulls the published image, generates its own secrets, binds to loopback. Measured at 31 s to pull and 24 s to a login page. It also pins platform: linux/amd64, because the published image has no arm64 manifest and the plain command simply failed on Apple Silicon.

./setup.sh is still the path for anything reachable from a network: it does the domain, the certificates through Caddy and the MCP auth mode.

Fixed: the first-run wizard described a licensing model we do not have

On a self-hosted instance the licence step told every admin that commercial use requires a key, and offered to "purchase a license to unlock all features". Nothing in the backend gates on license_key, and AGPL-3.0 permits commercial use. The copy now says what is true, and the step is skippable rather than skippable-only-after-an-error.

Also

  • New banner, generated from docs/assets/banner.html by scripts/generate-banner.mjs, so the claims live in editable text instead of a PNG. Same source produces the GitHub social preview.
  • README reordered around the first screen, with an honest comparison table against ContextForge, Docker MCP Gateway, MetaMCP and Composio, and KOCH Freiburg GmbH named as the production reference.
  • Response mapping's failure mode is documented correctly: it fails open by default (fallbackToRaw: true) and returns the raw upstream response when a mapping breaks. For fields that must never travel, set "fallbackToRaw": false. The README previously called this "fails safe".
  • /mcp/demo can optionally serve the read-only tools of one operator-designated server via MCP_DEMO_SERVER_ID, failing closed to the static product tools when unset or misconfigured. It is unset by default and we are not running it.
  • server.json reports the real version. It had been pinned at a hardcoded 1.0.0 that never existed, which is what the MCP registry was showing.
  • Every roadmap item is now an issue under label:roadmap, six of them marked good first issue.

Full diff: v0.7.5...v0.8.0