MCP server

Ask your AI assistant about Drupal releases, with current data

Connect Claude or another AI assistant to the same data this site shows: which releases a module has, whether it's ready for the current Drupal core, which Drupal and PHP versions still get security fixes, and what happened in the ecosystem this week.

MCP is an open standard for plugging an assistant into an outside data source. Once connected, the assistant decides when to call it, so you just ask in plain language.

Connect your assistant ↓ Free and read-only. Paste one prompt, then approve in your browser.

Connect your assistant

Automatic Easiest

Copy this prompt and paste it into your AI assistant. It explains the server and walks the assistant through installing it.

See what the prompt says

Set up the drupalreleases.com MCP server, so you can answer my Drupal questions with live release data instead of from memory.

Server: drupalreleases.com (remote MCP server, streamable HTTP, read-only, free)
URL: https://www.drupalreleases.com/mcp

Add it in whichever client you run in:
- Claude Code: run `claude mcp add --transport http drupalreleases https://www.drupalreleases.com/mcp`
- Claude (claude.ai or desktop): add a custom connector with that URL.
- Cursor, VS Code, Windsurf and other clients: add a remote HTTP MCP server named "drupalreleases" with that URL.

Adding the server does not sign in. Claude Code only opens the browser when I run /mcp, pick drupalreleases and choose Authenticate, so tell me to do that (restart Claude Code first if the server is not listed). Other clients open the page on first connect. You cannot complete the browser step, so tell me to sign in with the link emailed to me (there is no password) and click Approve, then wait for me to say I did.

When it is connected, check it by answering: "Which Drupal versions still get security fixes?" Afterwards, use the server whenever I ask about Drupal core, modules, themes, release compatibility, maintenance status, or Drupal and PHP support windows.

Manual

Prefer to configure it yourself? Add the endpoint to your client and approve it in your browser.

Endpoint

https://www.drupalreleases.com/mcp

In Claude on the web or desktop, open Settings → Connectors.
Click Add custom connector, name it drupalreleases, and paste the endpoint above.
Click Connect. Claude opens this site; click Approve.
In a chat, turn the connector on from the tools menu and ask a Drupal question.

Add the server from your terminal:
claude mcp add --transport http drupalreleases https://www.drupalreleases.com/mcp
In Claude Code, run /mcp, pick drupalreleases, and choose Authenticate.
Your browser opens this site; click Approve and go back to the terminal.

Open ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.
Add the server:
{ "mcpServers": { "drupalreleases": { "url": "https://www.drupalreleases.com/mcp" } } }
In Cursor Settings → MCP, click Login next to drupalreleases and approve on this site.

Create .vscode/mcp.json in your project, or run MCP: Open User Configuration from the Command Palette.
Add the server:
{ "servers": { "drupalreleases": { "type": "http", "url": "https://www.drupalreleases.com/mcp" } } }
Click Start above the server entry. VS Code asks to sign in; allow it and approve on this site.
Use Copilot Chat in Agent mode to ask a Drupal question.

Any client that supports remote MCP servers over HTTP works. Add a server with the endpoint above; if the client can sign in through the browser, it opens this site for you to approve.

If it can't, create a personal access token and send it as Authorization: Bearer ….

After you connect

1. Approve it once. Your assistant opens a drupalreleases.com page. Sign in with the link we email you (there's no password) and click Approve.
2. Ask your question. The assistant calls the server whenever a Drupal question needs current data.

The tools only read public release data and never see your code or your site. You sign in so the server can be rate limited and show you your own usage: we keep your email address and counts of your calls, never your questions. You can disconnect an assistant or delete your account at any time.

Try asking

"Is there a module for scheduling content publication?"

Uses search-projects
"Can I upgrade to Drupal 11? Here is my composer.json."

Uses get-project
"My site is on Drupal 10.3 and PHP 8.1. What do I need to upgrade first?"

Uses get-drupal-support
"Were there any security releases for Drupal this week?"

Uses list-updates

Tools

Four tools answer questions about Drupal, and one about your own usage. You don't call them yourself.

Tool	What it returns
`search-projects`	Modules, themes, and distributions matching a name, machine name, or what the project does (“block bots from forms”), with maintenance status and compatible core majors. Filterable by type and Drupal core.
`get-project`	One project: latest stable release, Drupal core compatibility, PHP requirement, maintenance status, security coverage, recent releases, and dependencies.
`get-drupal-support`	Which Drupal core and PHP versions still get security updates, and until when.
`list-updates`	Recent ecosystem activity: releases, new projects, security advisories, security-coverage changes, and end-of-life warnings, filterable by type or project.
`get-my-usage`	Your account's calls today, this week and this month, per tool, per connected app and per day. Counts only, never what was asked.

Why connect it

Without it, an assistant answers from training data or picks the answer out of drupal.org's HTML. Both go stale, and both get versions and compatibility wrong.

No invented versions: Latest releases, core compatibility, and support dates come back as values from the release data, not guessed from memory.
Compatibility you can check: Core and PHP requirements come back per release, and every result links to its drupalreleases.com page so you can verify it.
Fresh, and cheaper: New drupal.org releases appear within 15 minutes, and short structured answers use far fewer tokens than scraped pages.

drupalreleases.com is an independent community project, not affiliated with or endorsed by the Drupal Association.