Bernstein - Multi-agent orchestration
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| bernstein_health | Liveness check - always succeeds if the MCP server is running. Use this to verify the Bernstein MCP connection is still alive. Returns: JSON with status "ok". |
| bernstein_run | Start an orchestration run by posting a task to the Bernstein server. Args: goal: Description of what you want Bernstein to accomplish. role: Specialist role to assign (backend, frontend, qa, security, …). priority: 1=critical, 2=normal, 3=nice-to-have. scope: Task scope - small, medium, or large. complexity: Task complexity - low, medium, or high. estimated_minutes: Rough time estimate in minutes. Returns: JSON with the created task ID, title, and status. |
| bernstein_status | Return a summary of all task counts from the Bernstein server. Returns: JSON with total, open, claimed, done, failed counts plus a per-role breakdown. |
| bernstein_tasks | List tasks from the Bernstein server. Args: status: Optional filter - open, claimed, in_progress, done, failed, blocked, or cancelled. Returns: JSON array of task objects. |
| bernstein_cost | Return cost summary (total USD spent and per-role breakdown). Returns: JSON with total_cost_usd and per-role cost breakdown. |
| bernstein_stop | Request a graceful Bernstein shutdown by writing a SHUTDOWN signal. Writes Args: workdir: Project root directory (default: current directory). Returns: Confirmation message. |
| bernstein_approve | Approve a pending or blocked task, marking it complete. This is used for approval gates - when a task is awaiting human sign-off before proceeding. Args: task_id: ID of the task to approve. note: Optional approval note recorded as the result summary. Returns: JSON with the updated task status. |
| bernstein_create_subtask | Create a subtask linked to a parent task. Agents call this to decompose their current work into subtasks during execution. The parent task is automatically transitioned to WAITING_FOR_SUBTASKS status. Args: parent_task_id: ID of the parent task that this subtask belongs to. goal: Description of what the subtask should accomplish. role: Specialist role to assign (backend, frontend, qa, …). priority: 1=critical, 2=normal, 3=nice-to-have. scope: Task scope - small, medium, or large. complexity: Task complexity - low, medium, or high. estimated_minutes: Rough time estimate in minutes. Returns: JSON with the created subtask ID, parent_task_id, title, and status. |
| load_skill | Load a skill pack body (and optionally a reference or script). Agents receive only a compact skill index in their system prompt.
Call this tool to fetch the full Args:
name: Skill name (matches the index entry, e.g. Returns:
JSON with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| orchestrate_goal | Plan a Bernstein orchestration run for a single goal. |
| triage_failed_tasks | Triage the most recent failed tasks and propose next actions. |
| cost_recap | Summarise Bernstein cost by role for a stated window. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| bernstein_capability | Runtime capability card: transports, auth, tiers, meter, spec rev. |
| lineage_stats | Summary counts over the entire lineage log. |
Latest Blog Posts
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/sipyourdrink-ltd/bernstein'
If you have feedback or need assistance with the MCP directory API, please join our Discord server