Enables Google ADK agents to interact with Drupal sites using OAuth credentials and scope-aware tool access.
Also known as Omedia/drupalmcp-ts
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Sep 22, 2026
- License
- Apache-2.0
What is drupalmcp-ts MCP?
drupalmcp-ts enables Google ADK agents to interact with Drupal sites using OAuth credentials and scope-aware tool access.
Summary generated from the project's README
About drupalmcp-ts MCP server
Building Google ADK agents that can manage Drupal websites is the primary function of this TypeScript client. It connects an agent to a Drupal site running the drupal/mcp module, allowing the model to interact with site tools through the Model Context Protocol. Developers use the @drupalmcp/adk package to integrate these capabilities into an LlmAgent using models like gemini-flash-latest.
Setup requires specific environment variables including a Google API key, the Drupal base URL, a client ID, and a client secret. The system relies on a scope-aware security model where credentials determine specific permissions. For example, an agent using an agent-draft credential can read and write content but will be blocked by the server if it attempts to use the mcp:publish scope. This ensures that agents can only perform actions explicitly permitted by the Drupal site's configuration.
What you can do with it
- 1Automating content draftingAn agent can be configured to write and edit content on a Drupal site using a specific draft credential.
- 2Enforcing publishing restrictionsYou can prevent an AI agent from publishing content by providing a credential that lacks the necessary scope.
- 3Integrating Drupal tools with GeminiDevelopers can add Drupal-specific tools to a Google ADK agent using the drupalTools function.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
DRUPAL_BASE_URLDRUPAL_CLIENT_IDDRUPAL_CLIENT_SECRETGOOGLE_API_KEY
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableomedia/drupalmcp-ts is public and reachablegithub.com/omedia/drupalmcp-ts ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-22github.com/omedia/drupalmcp-ts ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubdrupalmcp-ts
Build a Google ADK agent that works on a Drupal site.
The site side is the Drupal module
drupal/mcp, which publishes a site's
tools over the Model Context Protocol and decides what each credential may
do. This repository is the client side, in TypeScript: the same libraries
will follow for Python, Go and Java.
| Package | What it is |
|---|---|
@drupalmcp/adk |
Drupal tools and credentials for a Google ADK agent |
Python, Go and Java packages will follow the same shape under the same name.
Quick start
npm install @drupalmcp/adk @google/adk @google/adk-devtools
// agents/my-site/agent.ts
import { LlmAgent } from '@google/adk';
import { DrupalOAuth, drupalTools } from '@drupalmcp/adk';
export const rootAgent = new LlmAgent({
name: 'site_editor',
model: 'gemini-flash-latest',
instruction: 'Help with the Drupal site. Never say something is published unless a tool said so.',
tools: [drupalTools({ auth: DrupalOAuth.fromEnv() })],
});
npx adk web agents
Four environment variables, three of which the Drupal site prints when you
run drush mcp:setup:
GOOGLE_API_KEY=... # https://aistudio.google.com/apikey
DRUPAL_BASE_URL=https://example.com
DRUPAL_CLIENT_ID=agent-draft
DRUPAL_CLIENT_SECRET=...
What the credential decides
A Drupal site running drupal/mcp publishes its tools under three scopes,
and hands out one credential per job. agent-draft may read and write;
agent-publish may publish. An agent holding the draft credential can write
as much as it likes and still cannot publish, because the server refuses the
call. That refusal reaches the model as a sentence it can act on:
The site refused: this credential does not hold the mcp:publish scope. Say so plainly and do not try again; a different credential is needed.
See the security model.
Requirements
Node 24.13 or later, and a Drupal site running drupal/mcp 2.0 or later.
Working on it
npm install
npm run check # lint, build, test
npm --workspace @drupalmcp/adk run test:live # needs a real site, see below
The live tests talk to a Drupal site and are skipped unless DRUPALMCP_LIVE=1
and the site variables are set. They mint a token, list the tools, read the
site and confirm the publish tool is refused.
Apache-2.0.
drupalmcp-ts MCP questions
How does the security model handle restricted actions?
The server uses scope-aware refusals; if a credential lacks a specific scope, the server refuses the call and provides a message the model can act upon.
Which environment variables are required for setup?
You need GOOGLE_API_KEY, DRUPAL_BASE_URL, DRUPAL_CLIENT_ID, and DRUPAL_CLIENT_SECRET.