moe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | AWS region for Bedrock (must support Cohere Embed v4, Rerank 3.5, and Claude, e.g., us-west-2) | |
| QDRANT_URL | Yes | Qdrant Cloud cluster URL (e.g., https://xyz.us-west-1-0.aws.cloud.qdrant.io) | |
| QDRANT_API_KEY | Yes | Qdrant Cloud API key | |
| AWS_ACCESS_KEY_ID | Yes | AWS access key ID for Bedrock access | |
| AWS_SECRET_ACCESS_KEY | Yes | AWS secret access key for Bedrock access |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_expertsA | Ask the mixture of domain experts a question. The server routes the question to the most relevant expert knowledge base(s), runs hybrid retrieval + reranking, and returns the best-supported passages. EACH passage includes a citation (title, author, location). You MUST cite these sources in your answer using their bracket numbers, and answer only from them. Args: question: The natural-language question. top_k: Max passages to return (default 8). experts: Optional list of expert names to force; omit to auto-route. synthesize: If true, the server also returns a grounded, cited answer string. |
| list_expertsA | List the available domain experts and how much each one knows. |
| get_sourceB | Fetch metadata about a cited source (to expand or verify a citation). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| experts_resource | Browsable list of experts. |
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: asking questions, fetching source metadata, and listing experts. There is no functional overlap among the three.
All tool names follow a consistent verb_noun pattern (ask_experts, get_source, list_experts), making them predictable and easy to understand.
Three tools is well-scoped for the server's domain of expert QA. Each tool is necessary and there are no extraneous or missing core functions.
The set covers the main workflow: querying experts, verifying sources, and discovering available experts. A minor gap is the lack of a tool to get detailed expert profiles, but it's not essential for typical use.