Download the PHP package phpclaw/phpclaw-drupal without Composer
On this page you can find all versions of the php package phpclaw/phpclaw-drupal. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phpclaw-drupal
This is a read-only mirror, auto-published from
phpclaw-monorepo. Please open issues and pull requests there, not here.
Talk to your Drupal site.
phpClaw is the AI layer for Drupal.
Running a site means digging through content, config, and the Drush toolbox to answer questions that should take five seconds. phpClaw replaces the digging with a conversation, backed by Drupal-aware tools.
Ask about content, users, blocks, or your cron status and get a real answer. No custom query, no admin-screen archaeology.
Same agent, five ways in: the admin chat, Drush, the REST API, the module's own admin routes, or your own PHP code via dependency injection.
Just ask
Drupal Admin
A chat panel inside Configuration → phpClaw AI Agent → Chat. Ask a question, the agent picks a tool, runs it against your site, and answers in the same panel.
Drush
The same agent from your terminal, scriptable and CI-friendly:
drush phpclaw:chat keeps one conversation open, streams each reply and prints each tool call; type
/help for its commands. Both commands take --conv-id=<id> and --continue.
REST API
Two routes on Drupal's own routing and authentication stack. Drupal authenticates the caller and checks the permission before phpClaw runs, and phpClaw issues no token of its own.
Both require use phpclaw chat. Conversations are stamped with the calling user's ID and scoped to
that user unless they also hold manage all phpclaw conversations.
Drupal core ships two authentication providers, cookie and basic_auth, and issues no per-user
API token. The routes accept whichever providers api_auth_providers lists, defaulting to
basic_auth and cookie. Add a contributed provider ID there if the site runs one.
Basic authentication sends the account password on every request, so serve these routes over HTTPS.
Drupal requires an X-CSRF-Token header only when a request carries a session cookie, so a
basic-auth caller needs none.
Admin routes
The admin screens keep their own routes under /admin/config/phpclaw/*, including chat send,
stream, load and delete, plus the administrator-only provider test-connection. Those run inside an
authenticated Drupal session with an X-CSRF-Token header and are not part of the REST surface.
Programmatic use
Resolved straight from Drupal's service container, where PhpClawServiceFactory is the factory behind phpclaw.agent:
Installation
composer require phpclaw/phpclaw-drupal. This also installsphpclaw/phpclaw-cloudandphpclaw/phpclaw-mcpas required dependencies (cloud guards/webhooks and the MCP server are both optional to use; no cloud account is needed to run the module locally).- Enable the module:
drush en phpclaw -y - Open Configuration → phpClaw AI Agent → Settings, pick a provider, and add your API key.
Full setup, configuration, and provider options are documented at phpclaw.ai/docs/adapters/drupal.
Key features
✅ Natural language: ask in plain English, no query syntax to learn
✅ 15 Drupal-native tools + 5 core utility tools: entities, config, database, log, modules, cron, menus, media, views, user roles, blocks, path aliases, cache, content moderation, webforms, plus shell, HTTP, code search, file read and project info in Drush, the MCP server and the phpclaw.agent service. The admin chat and REST API get the Drupal-native tools only. The log, menu, media, views, block, content-moderation and webform tools need their modules enabled; the log tool reads Drupal's watchdog table through dblog.
✅ Admin chat: inside the Drupal back-end, where your team already works
✅ Drush CLI: the same agent, scriptable and CI-friendly, plus an mcp-server command
✅ Multiple AI providers: Anthropic, OpenAI, Groq, Gemini, Mistral, DeepSeek, Ollama, and any custom OpenAI-compatible endpoint
✅ Admin routes: the same send and stream backend the Chat page uses, callable from admin-side code
✅ Conversation memory: context carries across a session
How it fits together
Documentation
This README gets you installed. Everything else (configuration, providers, memory, skills, Cloud, the full tool reference, admin routes, CLI, code examples, upgrading, troubleshooting) lives at:
phpclaw.ai/docs/adapters/drupal
Contributing
Contributions are welcome. See the contributing guide.
Security
Please review our security policy for reporting vulnerabilities.
License
MIT. See phpClaw project.
Drupal is a registered trademark of Dries Buytaert. phpClaw is an independent open-source project and is not affiliated with or endorsed by the Drupal Association.
All versions of phpclaw-drupal with dependencies
composer-runtime-api Version ^2.0
phpclaw/phpclaw Version ^0.1
phpclaw/phpclaw-cloud Version ^0.1
phpclaw/phpclaw-mcp Version ^0.1
drupal/core Version ^10.0|^11.0
psr/simple-cache Version ^3.0