Roadmap¶
This page names the big pieces of work and the order we expect them in. It changes rarely. Three other places hold the rest:
- The vision: Adding AI to CiviCRM, a community discussion of how CiviCRM can add AI, and where this extension fits.
- This extension's scope: Where civicrm_mcp fits for the longer view, and Scope for what it does today.
- Current priorities and work in progress: the
Development board. Its
priority:now,priority:nextandpriority:laterlabels match the three stages below.
We want your view
The order, what is missing, and what isn't worth doing are all open to discussion. Comment on
an issue, open a new one, or join
the ~ai channel on chat.civicrm.org.
Once releases begin, we release monthly, a few days after the maintainers' call (see CONTRIBUTING.md). Each release ships what was agreed on the call; the rest moves to the next one. Delivery depends on volunteer time, so the dates below are aims, not promises.
Now: release 1.0 (aim: November 2026)¶
What works today is an alpha with a read-only core you can extend in code: see Built-in tools, Adding your own tools and Scope.
1.0 (#1) is the first stable
release, and the first step in combining this extension with MJW Consulting's mcpserver
(#10). It aims to include:
- the protocol on the official PHP MCP SDK;
- permission profiles: who may connect, and which tools and entities each person gets;
- admin screens: settings, profiles, a setup checklist and the call log, all in the CiviCRM menu, so a site needs no command line;
- WordPress and CiviCRM Standalone;
- evaluations that check each change keeps the AI's answers right;
- testing with restricted users, a demo site with made-up data, the documentation published, and a listing in the extension directory.
Sign-in stays as it is for 1.0.
Next: finish combining, better answers¶
- Shared sign-in: sign-in moves onto oauthserver, a general OAuth 2.1 server for CiviCRM. Each AI connection signs in again once, and the minimum CiviCRM version rises to 6.19.
- Better tools: answers that are more often right first time, measured by the evaluations.
- Drupal, and AI apps that run on a person's own computer (such as Claude Code), which sign in differently from web-based clients.
- Under discussion: choosing SearchKit displays to publish as tools, with an approval step.
Later¶
- Write tools: opt-in per site, and always previewed before anything is saved.
- More CMSs and AI clients: Backdrop; other web-based AI clients, approved by an administrator without a code change; and each person able to see and revoke their own AI connections.
- One set of tools for AI inside CiviCRM too: assistants and buttons inside CiviCRM using the same tools, permissions and call log as outside AI clients (see the vision).
Where the code comes from¶
civicrm_mcp started by bringing together work from three organisations:
- An MCP server built for MAS (Management Advisory Services of Ontario). Its generic core is the code here today.
mcpserverandoauthserverfrom MJW Consulting: an MCP server on the official PHP MCP SDK, and a general OAuth 2.1 server for CiviCRM. They are being combined into this extension now (#10).- AI work at JMA Consulting, including its ai-connection assistant, which builds SearchKit searches by conversation.
Their maintainers now maintain civicrm_mcp together. Tools specific to one organisation stay in that organisation's own extension and register through the tool registry (Adding your own tools).