What can you do with this server?

Daedalus MCP is a local Model Context Protocol server that scans your workspace, detects projects and their tech stacks, and creates/runs specialized engineering agent pipelines for planning, code review, and architectural analysis. Core Capabilities: * Initialize Engineering Agents (daedalus_init): Scans the workspace to detect projects and technologies (language, framework, build tool, etc.), creates reusable agent templates, and generates per-project agents.config.yaml and agents/ directories. Supports options like force, refreshProjectKnowledge, refreshTemplates, and maxDepth. * List Detected Projects (daedalus_listProjects): Lists all projects found during the last init scan. * List Project Groups (daedalus_listGroups): Lists auto-generated groups such as all, java-all, angular-all, java21-spring-boot-all, etc., for targeting multiple related projects at once. * Run Agent Pipelines (daedalus_run): Executes a named pipeline (e.g., plan or review) over a group or explicit list of projects, returning a per-agent/per-project report. * plan pipeline: plan → rules → performance → architecture * review pipeline: code-review → rules → performance → architecture * Slash-Style Command Parser (daedalus): Parses commands like /daedalus init, /daedalus listProjects, /daedalus plan --group:java-all "task", or /daedalus review --project [a,b] "task" into structured tool calls. * Legacy Aliases (agent_init, agent): Backward-compatible aliases for daedalus_init and daedalus. Example Use Cases: * Scan a monorepo and auto-generate engineering agent configurations for each sub-project. * Run a planning or review pipeline across all Java/Spring Boot services simultaneously. * Generate and reuse technology-specific agent templates (e.g., java21-spring-boot-plan, typescript-angular-plan).

How do I use Daedalus MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Daedalus MCP plan --group:all 'add healthcheck'" 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.

Daedalus MCP

by juyagu1

Overview Schema Related Servers Score Discussions

TypeScript

Local

Daedalus MCP

Daedalus MCP is a local Model Context Protocol (MCP) server for creating and running specialized engineering agents per project or workspace.

It is designed for workspaces that may contain:

a single backend service;
several related microservices;
a frontend + BFF + backend setup;
a monorepo or folder with multiple related projects.

Daedalus scans the current workspace, detects the projects and their technologies, creates reusable agent templates, generates project-specific rules/knowledge, and lets you run sequential agent pipelines such as planning, rules validation, performance review, and architecture review.

Main idea

Given a workspace like:

workspace/
  catalog/
  data-mirror/
  vendors-bff/
  admin-ui/

Daedalus can detect stacks such as Java/Spring Boot or Angular and create:

workspace/
  .engineering-agents/
    workspace.agents.yaml

  catalog/
    agents.config.yaml
    agents/
      plan/
      rules/
      performance/
      architecture/

  admin-ui/
    agents.config.yaml
    agents/
      plan/
      rules/
      performance/
      architecture/

Reusable templates live inside this MCP project:

templates/
  java21-spring-boot-plan/
  typescript-angular-plan/
  project-rules-validator/
  performance-jvm/
  performance-web-node/
  architecture-microservice/
  architecture-frontend/

Daedalus does not overwrite existing files by default.

Related MCP server: portuni

Available MCP prompts / slash commands

Daedalus also registers MCP prompts named daedalus and daedalus-init. In clients that expose MCP prompts as slash commands, you can use:

/daedalus init
/daedalus listProjects
/daedalus plan --group:java-all "agregar healthcheck estándar"
/daedalus review --group:java-all "revisar el diff actual"

If the client says the slash command does not exist, use natural language or the daedalus tool directly, for example: “Use Daedalus and run /daedalus init”. Slash command availability is controlled by the host client, not by the MCP server alone.

Available MCP tools

`daedalus_init`

Scans the current workspace and initializes agents.

Equivalent slash-style command:

/daedalus init

What it does:

Detects the current workspace from MCP roots or cwd.
Finds projects inside the workspace.
Detects language, framework, build tool, package manager and architecture.
Creates missing reusable templates.
Creates agents.config.yaml and agents/ inside each detected project.
Creates workspace groups like all, java-all, angular-all, etc.

Options:

{
  workspacePath?: string,
  force?: boolean,
  refreshProjectKnowledge?: boolean,
  refreshTemplates?: boolean,
  maxDepth?: number
}

`daedalus_listProjects`

Lists projects detected by the last init.

Slash-style command:

/daedalus listProjects

`daedalus_listGroups`

Lists generated project groups.

Slash-style command:

/daedalus listGroups

Examples of groups:

all
java-all
java21-spring-boot-all
spring-boot-all
angular-all
typescript-all

`daedalus_run`

Runs an agent pipeline over a group or selected projects.

Slash-style examples:

/daedalus plan --group:java-all "agregar healthcheck estándar"

/daedalus plan --group:angular-all "agregar healthcheck estándar"

/daedalus plan --group:all "agregar healthcheck estándar"

/daedalus plan --project [catalog,data-mirror,vendors-bff] "agregar healthcheck estándar"

The report includes the response from every agent for every selected project.

Default plan pipeline:

plan -> rules -> performance -> architecture

`daedalus_review`

Runs the code-review pipeline over a group or selected projects. It reviews code, diffs, files or change descriptions using language/framework best practices and project-specific rules.

Slash-style examples:

/daedalus review --group:java-all "revisar el diff actual"

/daedalus review --project [catalog,data-mirror] "revisar cambios de healthcheck"

Default review pipeline:

code-review -> rules -> performance -> architecture

`daedalus`

Convenience parser for slash-style commands.

Input example:

{
  "command": "/daedalus plan --group:java-all \"agregar healthcheck estándar\""
}

Legacy aliases agent and agent_init are also available, but /daedalus is preferred.

Installation from local checkout

1. Clone the repository

git clone https://github.com/daedalus/daedalus-mcp.git
cd daedalus-mcp

Replace the URL with the real repository URL if different.

2. Install dependencies

npm install

3. Build

npm run build

4. Link the local binary

npm link

This exposes:

daedalus-mcp

Verify:

which daedalus-mcp

If your MCP client does not inherit your shell PATH, use the absolute path returned by which daedalus-mcp.

Add to Codex

Edit:

~/.codex/config.toml

Add:

[mcp_servers.daedalus]
command = "daedalus-mcp"
startup_timeout_sec = 60

If Codex cannot find daedalus-mcp, use the absolute path:

[mcp_servers.daedalus]
command = "/absolute/path/to/daedalus-mcp"
startup_timeout_sec = 60

Restart Codex.

Claude Code slash command `/daedalus`

Claude Code slash commands are client-side prompt files. If /daedalus is not recognized even though the MCP server is running, create this user-level command:

mkdir -p ~/.claude/commands
cat > ~/.claude/commands/daedalus.md <<'EOF'
---
description: Run Daedalus MCP commands
allowed-tools: mcp__daedalus__daedalus, mcp__daedalus__daedalus_init, mcp__daedalus__daedalus_listProjects, mcp__daedalus__daedalus_listGroups, mcp__daedalus__daedalus_run
---

Use the Daedalus MCP server. Run the MCP tool `daedalus` with:

```json
{ "command": "/daedalus $ARGUMENTS" }

If $ARGUMENTS is empty, use /daedalus init. Summarize the MCP result for the user. EOF


Restart Claude Code after creating or changing this file. Then use:

```txt
/daedalus init
/daedalus listProjects
/daedalus plan --group:java-all "agregar healthcheck estándar"
/daedalus review --group:java-all "revisar el diff actual"

Add to Claude Desktop

Edit:

~/Library/Application Support/Claude/claude_desktop_config.json

Add the server inside mcpServers:

{
  "mcpServers": {
    "daedalus": {
      "command": "daedalus-mcp"
    }
  }
}

If Claude cannot find daedalus-mcp, use the absolute path:

{
  "mcpServers": {
    "daedalus": {
      "command": "/absolute/path/to/daedalus-mcp"
    }
  }
}

Restart Claude Desktop.

Prompt to install from another Codex/Claude chat

Once this project is published, you can open a new Codex or Claude chat and say something like:

Install the Daedalus MCP from https://github.com/daedalus/daedalus-mcp.
Clone it, run npm install, npm run build, npm link, and add it as an MCP server named daedalus using the daedalus-mcp command. Then restart or tell me to restart the client.

For Codex specifically:

Install the MCP server from https://github.com/daedalus/daedalus-mcp and add this to ~/.codex/config.toml:

[mcp_servers.daedalus]
command = "daedalus-mcp"
startup_timeout_sec = 60

For Claude Desktop specifically:

Install the MCP server from https://github.com/daedalus/daedalus-mcp and add it to ~/Library/Application Support/Claude/claude_desktop_config.json under mcpServers as:

"daedalus": {
  "command": "daedalus-mcp"
}

Typical usage

After adding the MCP server and restarting the client, open a chat in the target workspace and run:

Use Daedalus and run /daedalus init

Then inspect what was detected:

Use Daedalus and run /daedalus listProjects

Use Daedalus and run /daedalus listGroups

Run a plan for all Java projects:

Use Daedalus and run /daedalus plan --group:java-all "agregar healthcheck estándar"

Run a code review for all Java projects:

Use Daedalus and run /daedalus review --group:java-all "revisar el diff actual"

Run a plan for specific projects:

Use Daedalus and run /daedalus plan --project [catalog,data-mirror,vendors-bff] "agregar healthcheck estándar"

Generated files

Workspace config

.engineering-agents/workspace.agents.yaml

Contains detected projects and groups.

Per-project config

agents.config.yaml

Contains project metadata, agents and pipelines.

Per-project agents

agents/
  plan/
    prompt.md
    agent.yaml
    knowledge/
      general/
      project/
  rules/
  performance/
  architecture/

Reusable templates

templates/

Templates are shared by technology/version/architecture and reused across projects.

Development

npm install
npm run build

Run directly:

npm start

Type-check:

npx tsc --noEmit

Notes

Daedalus uses MCP roots/list when available to identify the workspace opened in the client.
If roots are unavailable, it falls back to the process cwd.
workspacePath can be provided manually as an override.
Existing generated files are preserved by default. If a previous init generated stale project knowledge, rerun init with refreshProjectKnowledge: true to regenerate generated knowledge/general and knowledge/project files.
Pipeline execution uses MCP sampling when the host supports it. Some hosts return MCP error -32601: Method not found for sampling; in that case Daedalus now catches it and returns a handoff report with the prepared agent prompts/context so the host assistant can execute the reasoning in its final response.

Available Tools

7 tools

agentAgent command parser (legacy alias)D

Alias legacy de daedalus. Acepta /agent y /daedalus.

ParametersJSON Schema

Name	Required	Description	Default
`command`	Yes
`workspacePath`	No

TDQS

D1.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, and the description only states it is a legacy alias. There is no disclosure of side effects, permissions, or operational behavior (e.g., read-only vs. destructive).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While concise (two sentences), the description is under-specified and fails to provide essential information. It does not front-load a clear purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Considering the lack of output schema and parameter descriptions, the description is utterly incomplete. It omits details on return values, usage examples, and how to differentiate from siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning beyond the schema itself. Parameters 'command' and 'workspacePath' are not explained, leaving the agent without necessary context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is a legacy alias for daedalus that accepts /agent and /daedalus, but does not clearly define what the tool does (e.g., parse commands). The purpose is vague and lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this alias versus the primary daedalus tool or siblings like daedalus_init. The description does not mention any conditions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

agent_initInitialize Engineering Agents (legacy alias)D

Alias legacy de daedalus_init.

ParametersJSON Schema

Name	Required	Description	Default
`workspacePath`	No
`force`	No
`refreshProjectKnowledge`	No
`refreshTemplates`	No
`maxDepth`	No

TDQS

D1.1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description offers no behavioral information beyond being an alias. No mention of effects, permissions, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short but fails to convey useful information, so it's underspecified rather than concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, no output schema, and no annotations, the description is completely inadequate for an agent to correctly invoke this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not describe any of the 5 parameters or their roles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only states it's a legacy alias for daedalus_init, but does not explain what the tool does. It's essentially a tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus the siblings like agent, daedalus, or daedalus_run.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

daedalusAgent command parserB

Parser conveniente para comandos estilo /daedalus init, /daedalus listProjects, /daedalus plan --group:java-all "tarea" o /daedalus plan --project [a,b] "tarea". También acepta /agent por compatibilidad.

ParametersJSON Schema

Name	Required	Description	Default
`command`	Yes
`workspacePath`	No

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description lacks behavioral details such as side effects, error handling, or whether it executes commands or just parses them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and to the point, using examples to illustrate usage efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema or annotations, and low schema coverage, the description lacks information about return values, error behavior, and prerequisites, leaving gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning to the command parameter by showing example formats like `/daedalus init`, but does not describe the workspacePath parameter, which is undocumented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a parser for daedalus-style commands, providing examples that differentiate it from specific action tools like daedalus_init or daedalus_listProjects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for parsing daedalus commands or /agent commands, but does not explicitly state when not to use it or provide alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

daedalus_initInitialize Engineering AgentsB

Escanea el workspace actual, crea templates reutilizables si faltan y genera agents.config.yaml + agents/ por proyecto sin pisar archivos existentes.

ParametersJSON Schema

Name	Required	Description
`workspacePath`	No	Ruta opcional. Si se omite, usa el cwd/workspace actual del host MCP.
`force`	No	Pisa archivos de agentes/config de proyecto existentes.
`refreshProjectKnowledge`	No	Regenera knowledge/project aunque ya exista.
`refreshTemplates`	No	Regenera templates reutilizables aunque ya existan.
`maxDepth`	No	Profundidad máxima de escaneo de proyectos dentro del workspace.

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden. It states it does not overwrite existing files, providing safety info. However, it lacks details on side effects, required permissions, or behavior when parameters like force are used.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence front-loaded with the action verb. However, the language is Spanish while the title is English, which may slightly reduce clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main behavior but does not mention the return value or output format. Given the tool has 5 parameters and no output schema, this is a notable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already describes all parameters. The description does not add any additional meaning or context for the parameters beyond what is in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool scans workspace, creates templates, and generates config files per project without overwriting existing files. However, it does not explicitly differentiate itself from sibling tools like daedalus or daedalus_run.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description implies an initialization use case, but no explicit conditions, prerequisites, or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

daedalus_listGroupsList project groupsB

Lista grupos disponibles como all, java-all o angular-all generados por /daedalus init.

ParametersJSON Schema

Name	Required	Description	Default
`workspacePath`	No

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, and the description only states the tool lists groups. It does not disclose whether it modifies state, authentication needs, or other behavioral traits beyond the basic listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loading the purpose. However, it is in Spanish, which may reduce utility for some agents.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no output schema, the description covers basic purpose and examples but misses parameter context and usage details. Adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fails to explain the optional workspacePath parameter. No details on its purpose, format, or effect are provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists groups, provides concrete examples (all, java-all, angular-all), and specifies they are generated by /daedalus init. This clearly distinguishes from sibling daedalus_listProjects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage after running daedalus init, but no explicit guidance on when to use this tool vs alternatives like daedalus_listProjects. No exclusions or prerequisites mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

daedalus_listProjectsList scanned projectsB

Lista los proyectos detectados por /daedalus init en el workspace actual.

ParametersJSON Schema

Name	Required	Description	Default
`workspacePath`	No

TDQS

B3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only describes the action as listing projects, which implies a read-only operation, but does not mention whether authentication is needed, side effects, or dependencies on daedalus init having been run. The brevity leaves significant behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it omits necessary details about parameter, behavior, and output. Conciseness is positive, but under-specification harms usability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations, no output schema, and 0% schema description coverage, the description is severely incomplete. It does not explain return values, parameter usage, prerequisites, or error conditions. The tool's definition is inadequate for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter 'workspacePath' with 0% description coverage. The description does not explain what the parameter does, despite the description mentioning 'el workspace actual'. The parameter's meaning, format, and requirement are entirely unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists projects detected by daedalus init. The verb 'Lista' and resource 'proyectos detectados' are specific. It distinguishes from sibling tools like daedalus_listGroups (lists groups) and daedalus_run (runs projects).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies the context 'en el workspace actual', implying it operates on the current workspace. However, it does not explicitly state when not to use it or mention alternatives like daedalus_listGroups. Usage is clear but lacks exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

daedalus_runRun agent pipelineA

Ejecuta un pipeline como plan sobre un grupo o lista de proyectos y devuelve un reporte por agente/proyecto.

ParametersJSON Schema

Name	Required	Description	Default
`pipeline`	No	Nombre del pipeline, por ejemplo plan.	plan
`task`	Yes	Tarea/requerimiento a analizar.
`group`	No	Grupo, por ejemplo java-all, angular-all o all.
`projects`	No	Lista explícita de proyectos, equivalente a --project [a,b].
`workspacePath`	No

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose behavioral traits beyond the basic action. It does not mention side effects (e.g., whether the execution is idempotent, destructive, or requires specific permissions). For an execution tool that likely modifies state or consumes resources, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no unnecessary words. It is concise and front-loaded with the core action. However, it could be slightly more structured (e.g., separate purpose and parameters), but the brevity is acceptable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 parameters, 1 required, no output schema), the description is incomplete. It does not explain the return format of the report, any prerequisites, or how the pipeline interacts with the projects. The tool has several parameters, and the description should provide more context to ensure correct use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (80%), so the schema already describes most parameters. The description adds context about the overall purpose (executing a pipeline as a plan) and hints at the relationship between group/projects. However, it does not clarify workspacePath or the default pipeline value beyond what is in the schema. Therefore, it provides marginal added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool executes a pipeline on a group/list of projects and returns a report per agent/project. This distinguishes it from sibling tools like daedalus_listGroups and daedalus_listProjects that only list resources, and from daedalus/daedalus_init which are setup tools. The verb 'Ejecuta' (executes) and resource 'pipeline' are specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for running pipelines on groups or projects, which differentiates it from listing or initialization siblings. However, it does not explicitly state when not to use it or provide alternatives, such as whether to use daedalus_init first. The context is clear but lacks exclusionary guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.3/5.0

Disambiguation2/5

Multiple tools serve as aliases (agent vs daedalus, agent_init vs daedalus_init), causing ambiguity. An agent can't easily distinguish which parser to use for command interpretation.

Naming Consistency2/5

Names mix daedalus_ prefix (daedalus_init, daedalus_listGroups) with bare names (agent, agent_init) and inconsistent styles (agent vs daedalus). No uniform pattern.

Tool Count4/5

7 tools is appropriate for a project management assistant, covering initialization, listing, and execution. Not excessive or insufficient.

Completeness3/5

Core operations (init, list, run) are present, but missing update/delete actions for projects or groups. Coverage is adequate but not full CRUD.

Maintenance

ActivityStale

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

ArcAgent MCP
io.github.araujota
ArcAgent MCP server for bounty discovery, workspace execution, and verified coding submissions.
Autonomous Agents Code Execution Coding Agents
22
AgentMarketplace A
io.github.raditotev
MCP Server for an Agent Task Marketplace
Autonomous Agents Agent Orchestration
221
anotherai
dev.anotherai
MCP server for building and testing AI agents with multi-model experimentation and insights.
Agent Orchestration Autonomous Agents Testing & QA Tools
2
neverinfamous-memory-journal-mcp
ai.smithery
A MCP server built for developers enabling Git based project management with project and personal…
Version Control Developer Tools Project Management
320

Related MCP Servers

Code-Oracle
Code Analysis Security Developer Tools
Sri-Lohith-Mulugu
F
license
Not graded
quality
D
maintenance
MCP server for automated architectural mapping, security vulnerability detection, ML asset tracking, and code metrics in local repositories.
Updated 4 months ago (2026-04-21 10:35 UTC)
portuni
Knowledge & Memory Project Management
honzapav
A
license
Not graded
quality
A
maintenance
An MCP server that provides a shared graph of an organization's projects, processes, areas, and principles, enabling consistent context for tools and AI agents.
Updated 3 hours ago (2026-09-03 15:12 UTC)
2
Apache 2.0
Kontrol
File Systems Shell Access Code Execution
B-A-M-N
A
license
Not graded
quality
B
maintenance
A self-hosted MCP server that enables AI coding agents to read, edit, search, and run code in local projects with human review loops and policy controls.
Updated 2 days ago (2026-09-02 02:29 UTC)
MIT
ArchMemory MCP
Software Architecture Developer Tools
IWill29
A
license
Not graded
quality
C
maintenance
An MCP server that gives AI coding agents structured access to a project's architecture, rules, modules, and technical decisions.
Updated 2 months ago (2026-07-15 20:35 UTC)
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/juyagu1/daedalus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Daedalus MCP

Main idea

Available MCP prompts / slash commands

Available MCP tools

daedalus_init

daedalus_listProjects

daedalus_listGroups

daedalus_run

daedalus_review

daedalus

Installation from local checkout

1. Clone the repository

2. Install dependencies

3. Build

4. Link the local binary

Add to Codex

Claude Code slash command /daedalus

Add to Claude Desktop

Prompt to install from another Codex/Claude chat

Typical usage

Generated files

Workspace config

Per-project config

Per-project agents

Reusable templates

Development

Notes

Available Tools

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

`daedalus_init`

`daedalus_listProjects`

`daedalus_listGroups`

`daedalus_run`

`daedalus_review`

`daedalus`

Claude Code slash command `/daedalus`