Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Practice library for coding agents: skill search/invoke, seed patches, scout, reflect, ADR writer
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
DOJO_SKILLS_PATH, DOJO_ADR_PATH你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"dojogenesis": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DOJO_SKILLS_PATH",
"-e",
"DOJO_ADR_PATH",
"ghcr.io/dojogenesis/mcp:3.2.1"
],
"env": {
"DOJO_SKILLS_PATH": "your-value",
"DOJO_ADR_PATH": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add dojogenesis --env DOJO_SKILLS_PATH=your-value --env DOJO_ADR_PATH=your-value -- docker run -i --rm -e DOJO_SKILLS_PATH -e DOJO_ADR_PATH ghcr.io/dojogenesis/mcp:3.2.1运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"dojogenesis": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DOJO_SKILLS_PATH",
"-e",
"DOJO_ADR_PATH",
"ghcr.io/dojogenesis/mcp:3.2.1"
],
"env": {
"DOJO_SKILLS_PATH": "your-value",
"DOJO_ADR_PATH": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"dojogenesis": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DOJO_SKILLS_PATH",
"-e",
"DOJO_ADR_PATH",
"ghcr.io/dojogenesis/mcp:3.2.1"
],
"env": {
"DOJO_SKILLS_PATH": "your-value",
"DOJO_ADR_PATH": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
DOJO_SKILLS_PATH envDOJO_ADR_PATH env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 DojoGenesis 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(3.2.1)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The methodology layer for Claude Code. It encodes 99 first-party working methods across 10 behavioral plugins as active cognitive scaffolds: instead of giving Claude more data, it gives Claude structured *methods* for software development decisions.
We have not yet measured whether these scaffolds improve Claude's decisions, so this README makes no claim that they do.
Add to your project's .claude/settings.json:
{
"mcpServers": { "dojo": { "command": "/path/to/dojo-mcp-server", "env": { "DOJO_SKILLS_PATH": "/path/to/CoworkPluginsByDojoGenesis", "DOJO_ADR_PATH": "./decisions" } } } }
Or using Docker:
{
"mcpServers": { "dojo": { "command": "docker", "args": ["run", "-i", "--rm", "ghcr.io/dojogenesis/mcp-server:latest"] } } }
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": { "dojo": { "command": "/path/to/dojo-mcp-server", "env": { "DOJO_SKILLS_PATH": "/path/to/CoworkPluginsByDojoGenesis", "DOJO_ADR_PATH": "./decisions" } } } }
| Group | Tools |
|---|---|
| Methodology | dojo_scout, dojo_invoke_skill, dojo_search_skills, dojo_list_skills, dojo_apply_seed, dojo_reflect |
| Decisions | dojo_log_decision (writes ADR markdown to DOJO_ADR_PATH) |
| Gateway memory | dojo_memory_list, dojo_memory_store, dojo_memory_search (gateway session memory) |
| Memory Hub | dojo_search_memory, dojo_get_memory, dojo_recent_memories — read-only Postgres mirror of the institutional memory (DOJO_MEMORY_DB_URL) |
| Unified fetch | dojo_fetch — one tool to search AND fetch across memory hub + skills + ADRs + seeds (typed ids: memory:slug, skill:name, adr:file.md, seed:name) |
| Seeds | dojo_seed_list, dojo_seed_create, dojo_seed_search |
| Agents² | dojo_agent_list, dojo_agent_dispatch², dojo_agent_chat² |
| Dispatch² | dojo_dispatch² — prompt → LLM through the gateway |
| Project | dojo_project_status, dojo_project_track, dojo_project_decision |
| Disposition | dojo_disposition_list, dojo_disposition_set |
| Craft | dojo_converge, dojo_health |
² Dispatch-class — spends LLM provider budget through the gateway. In HTTP mode these require a dispatch-enabled API key and are rate limited per key; dojo_scout's LLM path degrades to its offline scaffold for non-dispatch keys.
Skills are complete, battle-tested methodology workflows loaded from SKILL.md files at startup. When DOJO_SKILLS_PATH is set, all 99 first-party CoworkPlugins skills are available. Without it, 43 key skills across 8 plugins are embedded in the binary via go:embed.
Bundled plugins and skills:
| Plugin | Skills |
|---|---|
agent-orchestration | agent-teaching, decision-propagation, handoff-protocol, workflow-router, workspace-navigation |
continuous-learning | debugging, project-exploration, research-modes, research-synthesis, retrospective, web-research-external |
skill-forge | mcp-cloudflare-builder, mcp-server-builder, process-extraction, skill-audit, skill-creation, skill-maintenance |
specification-driven-development | context-ingestion, frontend-from-backend, implementation-prompt, parallel-tracks, pre-implementation-checklist, release-specification |
strategic-thinking | iterative-scouting, multi-surface-strategy, product-positioning, strategic-scout |
system-health | documentation-audit, health-audit, semantic-clusters, status-writing |
wisdom-garden | compression-ritual, memory-garden, seed-extraction, seed-library |
Seeds are reusable thinking patterns drawn from across the Dojo ecosystem.
Dojo Genesis (Core)
| Seed | Description |
|---|---|
three_tiered_governance | Three-tiered governance framework: Strategic, Tactical, Operational. |
harness_trace | Nested JSON trace log for complete agent session traceability. |
context_iceberg | 4-tier context management system (hot/warm/cold/pruned). |
agent_connect | Routing-first agent architecture with a single supervisor. |
go_live_bundles | Lightweight deployment packages pairing artifacts with approval evidence. |
cost_guard | Budget for the full 5-10x context iceberg multiplier. |
safety_switch | Users must remain in control -- no autopilot on sensitive operations. |
implicit_perspective_extraction | Extract implicit perspectives from user queries without enumeration. |
mode_based_complexity_gating | Route to local or cloud models based on mode complexity. |
shared_infrastructure | Build once, reuse everywhere -- central implementations. |
AROMA & Serenity Valley
| Seed | Description |
|---|---|
sanctuary_architecture | Design digital spaces for being, not just doing. |
pace_of_understanding | Move slow to move fast; learn without extraction. |
lineage_transmission | Honor sources, trace influence, celebrate collaboration. |
graceful_failure | Permission to not know, change your mind, and ask for help. |
local_first_liberation | Local-first architecture for agent autonomy and user sovereignty. |
the_onsen_pattern | Rest as critical practice for sustainable performance. |
collaborative_calibration | Norms for peer-to-peer learning and explicit teaching. |
transparent_intelligence | Reveal internal state, admit uncertainty, make learning visible. |
inter_acceptance | Accept yourself through the compassionate eyes of another. |
radical_freedom | Agency and the power to choose your response within constraints. |
Documentation resources accessible via MCP resource URIs:
dojo://resources/{name} -- 8 documentation resources (AROMA philosophy, EIT principles, etc.)dojo://seeds/{name} -- 20 seed patchesdojo://skills/{plugin}/{name} -- All loaded skills| Env Var | Default | Description |
|---|---|---|
DOJO_SKILLS_PATH | (bundled fallback) | Path to CoworkPlugins root directory containing plugins/ |
DOJO_ADR_PATH | ./decisions | Directory where dojo_log_decision writes ADR files |
DOJO_GATEWAY_URL | http://localhost:7340 | Dojo AgenticGateway base URL |
DOJO_GATEWAY_TOKEN | (unset) | Bearer token for the gateway, if it requires one |
DOJO_MEMORY_DB_URL | (unset → hub tools disabled) | Postgres DSN for the Memory Hub (URL or keyword form; use the SELECT-only role) |
DOJO_HTTP_ADDR | (unset → stdio) | Opt into HTTP mode, e.g. :8091 |
DOJO_MCP_API_KEYS | (unset) | HTTP mode only: comma-separated label:key pairs (individually revocable) |
DOJO_DISPATCH_ALLOWED_LABELS | (unset → none) | Key labels allowed to run dispatch-class tools |
DOJO_DISPATCH_RATE_PER_MIN | 6 | Per-label rate limit for dispatch-class tools |
The server works out of the box with zero configuration (bundled skills, default ADR path, stdio).
Setting DOJO_HTTP_ADDR serves MCP streamable-HTTP instead of stdio:
POST/GET /mcp — the MCP endpoint, Bearer-key required (Authorization: Bearer ). Keyless or wrong-key requests get 401./mcp/k/ — same endpoint for clients that cannot send custom headers; the key is redacted in logs.GET /health — unauthenticated liveness (status + version only).The server refuses to start in HTTP mode without a valid, non-empty DOJO_MCP_API_KEYS. Every tool call is logged as tool_call tool=… key= dur_ms=… outcome=… — labels only, never key material, never payloads.
DOJO_HTTP_ADDR=:8091 \
DOJO_MCP_API_KEYS="win:$(openssl rand -hex 32)" \ ./dojo-mcp-server
curl -s localhost:8091/health curl -s -X POST localhost:8091/mcp \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
Client wiring (Claude Code): claude mcp add --transport http dojo-remote https:// /mcp --header "Authorization: Bearer ".
Deployment notes: ingress is expected to be a Cloudflare tunnel (no host ports); pin the container image by digest so auto-pull never surprise-deploys a new public surface. Image publishing: .github/workflows/docker-publish.yml → ghcr.io/dojogenesis/mcp (supersedes the old manually-pushed mcpbydojogenesis image).
git clone https://github.com/DojoGenesis/mcp.git
cd mcp
go build -o dojo-mcp-server ./cmd/server
./dojo-mcp-server
go test -race -v ./...
Requires Go 1.23 or later.
# Build the image
docker build -t dojo-mcp-server .
docker run -i --rm dojo-mcp-server
docker run -i --rm -v /path/to/CoworkPlugins:/skills -e DOJO_SKILLS_PATH=/skills dojo-mcp-server
mcp-server/
cmd/server/main.go Server entry point, env vars internal/ dojo/ handler.go 7 MCP tool handlers scaffolds.go Scout and reflect methodology templates skills/ loader.go Filesystem SKILL.md loader search.go Keyword + trigger search bundled.go go:embed fallback (15 key skills) bundled/ Embedded SKILL.md files decisions/ writer.go ADR file writer wisdom/ base.go Wisdom base, search, helpers seeds.go 20 seed patches resources.go 8 documentation resources Dockerfile Multi-stage container build .github/workflows/ci.yml CI pipeline .goreleaser.yml Cross-platform release config
Dojo Genesis is built on three core principles:
MIT License -- see LICENSE for details.
Copyright (c) 2026 Dojo Genesis
Contributions are welcome. Please see github.com/DojoGenesis for organization-level guidelines.