expert-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXPERT_URL | Yes | URL of the expert-service instance | |
| EXPERT_API_KEY | Yes | API key for authentication | |
| EXPERT_PROJECT | Yes | Default project name |
Capabilities
Features and capabilities supported by this server
| 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 |
|---|---|
| deep_searchA | Search beliefs and source documents with IDF-ranked results. No LLM call, sub-second response. This is the recommended search tool. It runs dual-path retrieval across the belief network and source document chunks, returning pre-ranked context ready for synthesis. Use this instead of calling search + list_beliefs + get_entry separately. Args: query: The question or search terms project: Project name or UUID (uses default if empty) |
| askA | Ask a question and get an LLM-synthesized answer grounded in the knowledge base. Uses the server's LLM to synthesize an answer from beliefs and source documents. Slower than deep_search but returns a ready-to-use answer. Args: question: The question to ask project: Project name or UUID (uses default if empty) |
| searchB | Full-text search across beliefs, entries, and source documents. Returns matching beliefs (with IN/OUT truth values), entry titles, and source chunk snippets. Args: query: Search terms project: Project name or UUID (uses default if empty) |
| explain_beliefA | Explain why a belief is IN or OUT by tracing its justification chain. Shows what supports this belief, what assumptions it rests on, and what would change if it were retracted. Args: node_id: The belief ID to explain project: Project name or UUID (uses default if empty) |
| what_ifA | Simulate retracting or asserting a belief without modifying the database. Shows the cascade: which beliefs would go OUT (retract) or come back IN (assert). Use this to understand the impact of changing a belief. Args: node_id: The belief ID to simulate action: "retract" or "assert" project: Project name or UUID (uses default if empty) |
| get_beliefA | Get full details for a specific belief including justifications and dependents. Args: node_id: The belief ID project: Project name or UUID (uses default if empty) |
| list_beliefsB | List beliefs in the knowledge base. Args: status: Filter by truth value -- "IN", "OUT", or empty for all project: Project name or UUID (uses default if empty) |
| list_projectsA | List all available expert knowledge bases with belief, entry, and source counts. |
| list_entriesB | List analysis entries (reports, findings, assessments). Args: topic: Filter by topic slug, or empty for all entries project: Project name or UUID (uses default if empty) |
| get_entryA | Read the full content of an analysis entry. Args: entry_id: The entry ID project: Project name or UUID (uses default if empty) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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/benthomasson/expert-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server