Druxt docs

Name: Druxt docs
Author: druxt

作者：druxt版本 1.0.1i★ –i在云端运行

注册名称org.druxtjs/docs

安装

概览

作者提供的说明（英文原文）

Search and read the Druxt documentation and API reference.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://druxtjs.org/mcp

在终端中运行这条命令

claude mcp add --transport http docs https://druxtjs.org/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "docs": {
      "url": "https://druxtjs.org/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "docs": {
      "type": "http",
      "url": "https://druxtjs.org/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://druxtjs.org/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 druxtjs.org 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7223 个服务器的 0%
发布到注册中心的时间比此分类中其他 7223 个服务器的 91% 更新
基础检查结果等于或优于此分类中其他 7223 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Druxt docs 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.1）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT3天前更新

安装

Codebase Memory

作者：DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT20天前更新

安装

Exa

作者：exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT44天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

druxtjs.org

Nuxt frontend and Drupal backend, built with Druxt.

This repository is the source of druxtjs.org, the documentation site for Druxt. It is also a working example of a Druxt site: its pages are Drupal content, rendered by Nuxt.

The site is two applications in one repository. nuxt/ is the frontend. It renders the documentation with Druxt, through DruxtEntity and its wrapper components. drupal/ is the Drupal 11 backend that editors write in.

Get involved

Run the whole site on your machine, frontend and backend together. Pick one of three ways.

Way	You need
Dev container	VS Code with Dev Containers, GitHub Codespaces, or DevPod
mise	mise, and three PHP extensions
By hand	PHP 8.3 or later, Composer and Node 16.20.1

Dev container

Tool	How
VS Code	Clone the repository, open it, then choose Reopen in Container
GitHub Codespaces	On the repository page, open Code and choose Codespaces
DevPod	Click the badge, or run `devpod up https://github.com/druxt/druxtjs.org`

The container has Node 16.20.1, PHP 8.4, Composer and mise. Creating it runs npm install and npm run setup, so Drupal is running when it opens. Then run npm run dev.

mise

.mise.toml pins Node 16.20.1 and PHP 8.4. PHP needs the gd, pdo_sqlite and sodium extensions.

mise install

npm install npm run setup npm run dev

By hand

Install PHP 8.3 or later with the gd, pdo_sqlite and sodium extensions, Composer, and Node 16.20.1. Then run:

npm install

npm run setup npm run dev

What you get

Command	What it does
`npm install`	Installs the root tooling and enables the git hooks
`npm run setup`	Installs Drupal on a throwaway SQLite database, fetches the pinned druxt.js for the API pages, then starts Drupal
`npm run dev`	Starts the Nuxt dev server against that Drupal. The first run installs the frontend's packages
`npm run login`	Prints a one-time login link for Drupal

Service	Address
Drupal	http://127.0.0.1:8888, or the next free port. `npm run info` shows which
Nuxt	http://localhost:3000

npm run setup writes Drupal's address to .env, and npm run dev reads it from there. Setup needs network access, for Composer packages and the pinned documentation on GitHub.

Write documentation

Run npm run login, and open the link it prints.
In Drupal, go to Content and edit a page, or add one. The layout paragraphs editor builds a page from sections of text, code and images.
Save, then reload the page on http://localhost:3000.

Preview, on the edit form, shows unsaved changes. docs/backend.md explains its tabs.

An edit made here is local to this machine's database: it previews and tests the site, and is not how page text is published. See Where changes go for what belongs where.

Editors can also sign in on http://localhost:3000 and see a page's latest draft on its own URL. docs/backend.md covers the workflow and the sign-in.

The Modules, API reference and Components pages come from the druxt.js packages. npm run docs:generate builds them locally, in the pinned druxt.js checkout. It installs and builds druxt.js first, so the first run is slow.

Where changes go

Change	Where it goes
The content model, the editor or the site's settings	Export them with `vendor/bin/drush config:export` in `drupal/`, and commit `drupal/config/sync/` in a pull request
The frontend	A pull request with the change in `nuxt/`
The text of a page	Drupal, where editors change it. The database is the source of truth, and page text is not taken as a pull request yet

The site's content is stored in production's database. A local Drupal starts with no pages, and edits in it stay local.

Druxt in the frontend

nuxt/ is a Nuxt 2 app built with Druxt, and it is written to be read as an example of a Druxt site.

What	How
Pages	Each section page resolves its path with the Druxt router, then renders the Drupal page with .
Wrappers	`nuxt/components/druxt/` holds the wrapper components Druxt finds by name. The page is `entity/node/DocPageFull.vue`, with one component per paragraph type in `entity/paragraph/`. The rest are fields (`field/`), layout sections (`layout-paragraph/`), blocks (`block/`), block regions (`block-region/`) and menus (`menu/`).
Display settings	druxt-schema reads Drupal's view and form displays when the app builds, so the frontend follows the display settings editors change in Drupal.
Layout	druxt-layout-paragraphs renders the page's layout sections.
Header, sidebar and footer	druxt-blocks renders the blocks placed in the `druxtjs` theme's regions in Drupal. The theme and the site's name and logo come from the `druxtjs_org` consumer's decoupled settings, read at build by `nuxt/modules/decoupled-settings`.
UI	`nuxt/components/dui/` holds presentational components with no Drupal dependency: code blocks, diagrams, rich text and columns. They will move to the shared Druxt UI library.
Playground	`nuxt/components/global/DruxtExample.vue` renders any Druxt component under a runtime of its own for the chosen backend (`nuxt/utils/druxt-runtime.js`), with what it knows about each component in `nuxt/utils/live-examples.js`. The same card sits on the module and component reference pages.

To change how something looks, find the wrapper name Druxt looked for (the Vue devtools show it), and add a component at the matching path under nuxt/components/druxt/. Component resolution explains the naming.

Deployment

The site runs on Lagoon as one environment, Drupal beside Nuxt. Nuxt serves pre-rendered pages first, and renders live any page it has not stored or that has aged past its time to live. docs/hosting.md covers what a deployment does.

Commands

Command	What it does
`npm run setup`	Install the backend, then start it
`npm run dev`	Nuxt dev server against the backend
`npm run storybook`	Storybook on port 3030, against the backend
`npm run start` / `stop`	Start or stop Drupal
`npm run info`	Where Drupal is, and the versions it runs
`npm run login`	One-time login link for Drupal
`npm run docs:generate`	Build the Modules, API reference and Components pages
`npm run lint`	Every linter except prose
`npm run lint:prose`	Vale, after `npm run lint:prose:install` once
`npm test`	Node tests for the scripts and the frontend's modules

Contributing

See CONTRIBUTING.md for commit messages, checks and what never goes in a file. Open issues and pull requests on druxt/druxtjs.org. docs/backend.md covers page history and previews.

License

MIT