🗺️ Roadmap — what AnythingMCP is shipping next #147
Replies: 43 comments
🚀 v0.1.23 — silence MCP duplicate-registration warnings is outPublished 2026-05-10 — see the full release notes. Silences The internal See #152 for details. Update with |
🚀 v0.1.24 — OpenAPI 3.1, healthcheck UX, SSRF allowlist, re-import preserve, MCP coercion is outPublished 2026-05-12 — see the full release notes. Six customer-driven fixes from the FastAPI / koch-filesystem-bridge integration: Connector import / parsing
Tool runtime
Test / debug UX
Security / on-prem
DB migrations (both additive, nullable, no backfill)
Update with |
🚀 v0.1.25 — Sorare adapter, LOGIN_TOKEN auth, GraphQL schema-slicing for every connector is outPublished 2026-05-18 — see the full release notes. First release that ships a full GraphQL story end-to-end. The Sorare Fantasy Football adapter lands, the new `LOGIN_TOKEN` AuthType lets adapters describe any bcrypt-style sign-in handshake declaratively, and every GraphQL connector — catalog or user-created — now gets a server-side schema-slicing proxy baked in so agents can drive APIs whose introspection is disabled or whose SDL is too large for the context window. New: Sorare Fantasy Football adapter (18 tools)Built-in adapter for Sorare's GraphQL API. Bcrypt-salted login, JWT cached for ~30 days, automatic re-issue 24 h before expiry and on any 401. Featured on the homepage with `priority: 100`. Tools (live-audited against api.sorare.com with real credentials, 17/19 happy-path pass, the two remaining are deliberate NOT_FOUND probes against fake IDs):
Five multilingual MDX guides for the marketing site (en/de/it × ChatGPT/Claude/OpenClaw/generic MCP) plus five SEO-targeted Markdown guides under `docs/guides/` so GitHub Search surfaces `sorare-to-mcp`, `connect-sorare-to-claude`, `connect-sorare-to-chatgpt`, `connect-sorare-to-openclaw`, `connect-sorare-to-cloud`. New: `LOGIN_TOKEN` AuthTypeA declarative spec for APIs that POST credentials → receive a long-lived bearer, optionally with client-side bcrypt against a salt fetched from the upstream. Adapter authors describe the entire flow in JSON; no per-provider code. The shared `LoginTokenService` handles salt fetch → bcrypt → `signIn` → token cache (in-memory + AES-256-GCM-encrypted DB row in the new `connector_auth_cache` table) → proactive refresh ≥ 24 h before expiry → forced re-login on 401, all behind a per-key mutex. Wired into both the REST and GraphQL engines (`injectAuth` + 401-retry path). Field-by-field reference: `docs/connectors/login-token-auth.md`. New: GraphQL schema-slicing proxy — every GraphQL connector, automaticallyUpdate with |
🚀 v0.1.26 — License activation handoff is outPublished 2026-05-19 — see the full release notes. HighlightsEnd-to-end license auto-activation between the cloud instance and
Companion PRs
Update with |
🚀 v0.1.27 — Tenant-scoped license lookup is outPublished 2026-05-19 — see the full release notes. HighlightsSecurity/billing fix: cross-tenant license entitlement leak in cloud mode. Pre-fix, an org with zero licenses could see another org's key as "License verified successfully" because
Self-hosted single-tenant behavior is unchanged — the Companion PR
Update with |
🚀 v0.1.28 — LicenseWall covers cloud no-license + MCP runtime check is org-scoped is outPublished 2026-05-19 — see the full release notes. Follow-ups to v0.1.27 — see #221. LicenseWall now blocks the cloud UI when an org has no license (was silently allowed through after the per-org isolation fix). dynamic-mcp-tools now passes organizationId through to checkLicenseActive so MCP tool calls work in cloud. Update with |
🚀 API Auth Update is outPublished 2026-05-20 — see the full release notes. What's Changed
New Contributors
Full Changelog: v0.1.28...v0.1.29 Update with |
🚀 v0.1.30 — DATEV + SAP + Playtomic + GA4 (9 PRs) is outPublished 2026-05-23 — see the full release notes. What's Changed
New Contributors
Full Changelog: v0.1.29...v0.1.30 Update with |
🚀 v0.1.31 — Etsy OAuth2 + Deutsche Bahn rewrite + 7 reverse-engineered SaaS adapters is outPublished 2026-05-28 — see the full release notes. Adapters
Fixes
DiffUpdate with |
🚀 v0.1.32 — Proxy / Web-Unblocker + Onboarding + Help Scout OAuth2 is outPublished 2026-05-31 — see the full release notes. ✨ HighlightsProxy / Web-Unblocker (#280, #281, #282)Route a tool's outbound request through a proxy or web-unblocker (e.g. Zyte API proxy mode) to reach anti-bot / geo / rate-limited APIs. Fixes the Deutsche Bahn connector that 403'd on Akamai-protected endpoints.
Onboarding (#272, #273, #276)
Connectors
Fixes
DiffUpdate with |
🚀 v0.1.33 is outPublished 2026-06-10 — see the full release notes. Fixes
Connectors
NotesNo breaking changes. Tenant isolation remains fail-closed and was verified against production data. Update with |
🚀 v0.1.34 is outPublished 2026-06-11 — see the full release notes. Maintenance release: a server-stability fix plus self-hosting and packaging improvements. Fixed
Self-hosting
Packaging / license
Upgradedocker compose pull && docker compose up -dNo configuration changes required. Update with |
🚀 v0.2.0 — Knowledge Graph, AI skills, analytics & security hardening is outPublished 2026-06-28 — see the full release notes. v0.2.0 — Knowledge Graph, AI skills, usage analytics & security hardeningA "smart, AI-empowered gateway" release. All AI features are opt-in and inert by default.
Update with |
🚀 v0.2.2 is outPublished 2026-06-28 — see the full release notes. v0.2.2Knowledge Graph + AI skills + usage analytics + security hardening, with the Features (since 0.1.x):
Stability fixes (0.2.1 → 0.2.2):
All migrations are additive and auto-applied on container start. Update with |
🚀 v0.2.3 is outPublished 2026-06-29 — see the full release notes. Fixes
Full changelog: v0.2.2...v0.2.3 Update with |
🚀 v0.4.3 — MCP Bridge base URL paths is outPublished 2026-08-27 — see the full release notes. Fixed: MCP Bridge connectors ignored the path in the base URLAn MCP Bridge connector whose base URL carried a path was always called at Reported in #501 against Snowflake's managed MCP servers, which live at
The base URL is now the endpoint. Paste the complete URL of the remote MCP server, path included. A bare host with no path still defaults to
A per-tool Behaviour changeIf you had left an unrelated path in an MCP connector's base URL and relied on it being discarded, set the base URL back to the bare host. The backend logs a one-off warning naming the old and new address for any connector whose resolved URL changes. Fixed: OAuth discovery for MCP servers hosted under a pathUpdate with |
🚀 v0.4.4 — Destatis GENESIS connector repaired is outPublished 2026-08-27 — see the full release notes. Fixed: the Destatis GENESIS connector has been broken since June 2025Destatis permanently switched off GET requests carrying credentials in the URL on 30 June 2025. The connector was still configured that way, so all four of its tools returned the GENESIS HTML web interface instead of JSON. It now uses POST with credentials in HTTP header fields, form-urlencoded bodies, and the current API token support. GENESIS issues a personal 32-character API token that identifies you without a password. One field, Existing installs must be re-installed, not re-synced. Catalogue re-sync updates tool definitions, instructions and config, but never a connector's authentication type or base URL. A re-synced old Destatis connector would end up with POST tools still sending credentials as URL parameters, and would report itself up to date. Remove it and install it again from the store. Corrections found by running it against a real account
Platform changes that came out of it
UpgradingNo migration and no configuration change. Self-hosted: Update with |
🚀 v0.5.0 — SCIM provisioning from Microsoft Entra ID is outPublished 2026-09-09 — see the full release notes. New: SCIM 2.0 provisioning from Microsoft Entra IDRole sync has always run at sign-in. That is enough to widen or narrow what someone may do, and useless for taking access away: a person who has stopped signing in never triggers it, and the MCP API key sitting in their This release adds that channel. Entra pushes joiners, movers and leavers over SCIM 2.0, and the change lands without a sign-in. Self-hosted only. Every SCIM route answers 404 on AnythingMCP Cloud, for the same reason SSO does: a shared deployment would let any tenant point a workspace at an arbitrary directory and provision accounts from it. UsersCreate, update, deactivate, reactivate and delete. Deactivation is one step and it is thorough:
The last admin of a workspace is protected here as everywhere else: the attempt is refused, audited as Groups, and roles that move on their ownProvisioned groups appear under Role mappings with a Once SCIM describes a user, the Update with |
🚀 v0.6.0 — Connection grants, and a cross-tenant fix is outPublished 2026-09-12 — see the full release notes.
|
| caller | scope |
|---|---|
/mcp/:serverId, or an API key pinned to a server |
that server's connectors |
any JWT on the shared /mcp |
the caller's organization |
| instance-level static credential (single-tenant self-hosted) | unscoped |
Not a data-read leak — the caller gets that connector's API response, not the other tenant's rows. Worse in one respect: with a write tool it acts as them against their own upstream system. It required a tool-name collision, which is trivial to arrange; 610 tool names were shared across more than one organization on our instance, one by 76.
Connection grants — choose what each AI client can reach
The shared /mcp endpoint now serves what you granted, and only that.
- A picker during authorization, shown only when there is genuinely a choice. One server, or a client that already named one, is granted silently — most people will never see it.
- A Connections page in Settings: change or revoke what a connected client reaches, taking effect on its next request. This matters because clients reuse cached tokens (Claude: 1-day access, 30-day refresh), so disconnecting and reconnecting does not reliably re-open the choice.
- Grants only ever narrow. Membership is re-validated against the database on every request, so a grant naming a workspace you have since left concedes nothing.
Tokens issued before this release are unaffected: no grant means the previous behaviour.
Update with docker compose pull && docker compose up -d (self-hosted) or wait for the Cloud rollout (~24h after this comment).
⭐ Star · 👀 Watch → Releases · 💡 Vote on the next adapter
🚀 v0.6.1 is outPublished 2026-09-12 — see the full release notes. Patch release: prerequisites for the Claude connectors directory listing, plus catalog fixes found while testing every open-data connector end to end. OAuth / MCP
Connectors
Catalog
Frontend
Update with |
🚀 v0.6.2 is outPublished 2026-09-12 — see the full release notes. Hotfix. MCP
Update with |
🚀 v0.7.0 is outPublished 2026-09-13 — see the full release notes. Connectors
Since 0.6.2
Update with |
🚀 v0.7.1 is outPublished 2026-09-13 — see the full release notes. Patch release.
Update with |
🚀 v0.7.2 is outPublished 2026-09-13 — see the full release notes. Patch release: minimal OpenID Connect for the MCP authorization server. Update with |
🚀 v0.7.3 is outPublished 2026-09-13 — see the full release notes. Patch release: the cloud frontend no longer redirects Update with |
🚀 v0.7.4 is outPublished 2026-09-14 — see the full release notes. Patch release.
Update with |
🚀 v0.7.5 is outPublished 2026-09-14 — see the full release notes. Patch release focused on session revocation and role enforcement on self-hosted instances. Cloud behaviour is unchanged.
Upgrade note for self-hosted: if you revoked sessions for members in the last 30 days, their AI clients will be asked to sign in again once after this update. Update with |
🚀 v0.8.0 is outPublished 2026-09-14 — see the full release notes. 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 agreeThe adapter count appeared as nine different numbers across the repo, the website and the directories, and the README banner had
Real numbers, generated: 188 adapters, 26 of which need no API key, 1,814 tools. Install without cloningmkdir 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 -dPulls 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
Fixed: the first-run wizard described a licensing model we do not haveUpdate with |
🚀 v0.8.1 is outPublished 2026-09-14 — see the full release notes. v0.8.0 does not boot. Use this instead. If you pulled What was broken
The container restarted in a loop, but the frontend in the same container started normally, so The version is now resolved by walking up from Also fixed: a failed migration no longer starts the backend anyway
It now stops at the migration step, where the error still describes the actual problem. Docker's restart policy retries, which is also the right behaviour when the database is simply not accepting connections yet. Both shipped compose files gate on a healthy Postgres, so this was only reachable when running the image by hand. Why CI did not catch the first oneThe That check found both of the issues above, plus two gaps in its own setup, within three runs. Full diff: v0.8.0...v0.8.1 Update with |
🚀 v0.9.0 — Deutsche Bahn on open data, import-time probe, honest keyless count is outPublished 2026-09-15 — see the full release notes. Deutsche Bahn works again, on open dataThe Deutsche Bahn adapter no longer scrapes bahn.de through db-rest (Deutsche Bahn blocks datacenter IPs; the cloud had not completed a call since 30 August). It now talks to a MOTIS routing engine loaded with the open gtfs.de train timetable (every ICE, IC, EC, regional train and S-Bahn, CC BY 4.0) and a GTFS-RT feed for live delays, platform changes and cancellations.
Installed connectors on the cloud are migrated; self-hosters re-sync the connector from the catalog and enter a The "no API key" number is now checked
Activation
AlsoUpdate with |
Uh oh!
There was an error while loading. Please reload this page.
🗺️ AnythingMCP — public roadmap
This thread tracks where AnythingMCP is heading. The full document lives in ROADMAP.md — this discussion is where you can comment, push back, and propose changes.
Now (in active development)
Next
Want to influence priorities?
⭐ Star and 👀 Watch the repo to be notified when items ship.
All reactions