Skip to content

Release Notes

Read these before every upgrade. Each release lists the issues that went into it; the linked issues on GitLab have the detail. Anything you must do when upgrading is listed first, under Upgrade notes.

Releases follow semantic versioning: a change in the first number means something may break.

1.0.0 (unreleased)

The first release.

  • Read-only AI access to CiviCRM, inside CiviCRM. The two built-in tools (Built-in tools), OAuth 2.1 sign-in with your normal CMS login, and a call log of every tool call.
  • Claude and ChatGPT can both connect, and an administrator can turn either off (#5).
  • The official PHP MCP SDK runs the protocol (#12).
  • Admin screens: a setup checklist, settings and the call log, all in the CiviCRM menu (#3).
  • Permission profiles decide who may connect and which tools and records each person gets (#14).
  • CiviCRM's own security is the ceiling: nothing shows anyone more than CiviCRM does (#20).
  • CiviCRM Standalone is supported alongside WordPress, and a deactivated Standalone user is cut off at once (#18).
  • A throwaway test site and shared evaluations for checking changes (#15), and smaller fixes (#19).

Upgrade notes (from a pre-release only)

A new install needs none of this.

  • Run cv updb before serving calls. Until it has run, every tool call is refused.
  • Everyone on the old allowlist moves into one profile, allowlist-upgraded, with all tools and all entities, so nobody gains or loses access.
  • ChatGPT is on by default. If your organisation has not approved it, turn it off under Supported AI clients (Setup).
  • Civi\Mcp\Scoped\* is removed. Update any extension that uses it before you upgrade, or every MCP request fails.