moe-mcp
This server exposes a mixture of domain experts system that lets you query curated knowledge bases and retrieve cited answers. It provides three core capabilities:
ask_experts: Submit a natural-language question, which is automatically routed to the most relevant expert(s). The server runs hybrid retrieval and reranking, returning the best-supported passages with citations (title, author, location). You can control how many passages are returned, force routing to specific expert(s) by name, or request a synthesized, grounded, cited answer in addition to raw passages.list_experts: Retrieve the full roster of available domain experts along with information about their knowledge scope and how much knowledge each expert has.get_source: Fetch detailed metadata about a specific cited source by its ID, allowing you to expand on or verify any citation returned from a query.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@moe-mcpWhat are the symptoms of aortic stenosis?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
moe — a team of domain experts, as agent skills
moe packages a mixture of domain experts as installable skills + subagents for your
coding agent (Claude Code, Codex, Pi, …). Each expert owns a curated knowledge folder built
from your materials (books, articles, docs); it answers by searching that folder (grep/read)
and citing it — no RAG, no vector DB, no embeddings. A router skill picks the right
expert(s) for a question and synthesizes a cited answer.
Install
dist/ is committed, so you never need Python to use the experts. Install with npx — with no
flags it auto-detects your installed agent(s) (~/.claude, ~/.codex, .agents/.pi) and
scope:
npx github:tiennt235/moe install # or: npx skills add tiennt235/moe
# then, inside your agent:
/moe ask "which valve is on the left side of the heart?"Related MCP server: pramana-mcp
How it works
Expert = subagent.
experts/<name>/EXPERT.md(optional guidance) +experts/<name>/knowledge/(built markdown +INDEX.md). The expert reads the index, greps the files, and citessource · section · page.Router = skill. Reads the roster (
experts.yaml) and picks the matching expert(s) by reasoning over their descriptions — no embeddings. Then delegates and synthesizes.Retrieval = agentic file search. Coding agents are already great at grep/read; that is the retrieval engine. Citations come from each knowledge file's front-matter + headings.
Install targets & delegation
Host | Installs to | Delegation |
Claude Code |
| native subagents (Agent tool) |
Codex |
| native subagents; paste the snippet into |
Pi / generic |
| inline expert-mode (no subagent primitive) |
npx github:tiennt235/moe install --providers=claude,codex,agents --scope=project # or --scope=globalClaude Code can also install via plugin marketplace (plugin/plugin.json), and any
Agent-Skills host via npx skills add tiennt235/moe.
Portability
The repo is the shareable expert team — dist/ and knowledge/ are committed. Anyone gets
your experts with npx github:tiennt235/moe install (or npx skills add tiennt235/moe). No
database, snapshot, or re-embedding.
Layout
experts.yaml roster (drives routing)
experts/<name>/ EXPERT.md · materials/ · knowledge/ (built)
skill/moe/ router skill source (SKILL.md + commands)
templates/ shared expert-behavior template
src/moe/ Python builder (extract → knowledge → dist)
bin/moe.mjs Node umbrella CLI (install/build/scaffold/list)
dist/{claude-code,codex,agents,dev}/ committed per-host builds
plugin/plugin.json Claude Code marketplace manifestContributing
Building experts is the authoring path, which needs Python (the material extractor). Clone the repo, then add experts one of two ways.
Add an expert by hand
uv run moe list # show the roster
uv run moe scaffold neurology -d "Clinical neurology…" # new expert
# drop material into experts/neurology/materials/, then:
uv run moe build && npx github:tiennt235/moe installAdd materials as path: (local) or url: entries under an expert in experts.yaml. Supported
formats: PDF (+OCR), EPUB, MOBI (via Calibre), HTML, Markdown/text. (uv run moe also works as
python -m moe or pip install -e . && moe.)
Or let the expert-builder do it
moe ships a meta-expert that builds other experts for you, so you rarely edit
experts.yaml by hand.
It is dev-only: it runs the Python authoring path, so it never ships to end users and lives
only in the dev build.
Onboard it once, from a clone of this repo:
uv run moe build # builds knowledge + dist/ (incl. the dev build)
npx github:tiennt235/moe install --dev # deploys the dev build into this repo's .claude/Then, inside your coding agent, delegate to the moe-expert-builder subagent (or just ask, and
the router routes to it). It works in two modes:
Guided ingest — give it a topic and materials (file paths or URLs); it ingests exactly those. Example: "build a neurology expert from these two PDFs and this article."
Auto-research — give it only a topic; it searches for authoritative, openly-licensed sources, proposes a shortlist for you to approve, then builds from the approved set. Example: "build a stoicism expert from public-domain sources."
Either way it scaffolds the expert, patches experts.yaml, runs uv run moe build, verifies
the knowledge and its citations, and reports.
Deploy the result to end users with npx github:tiennt235/moe install.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tiennt235/moe'
If you have feedback or need assistance with the MCP directory API, please join our Discord server