/ Directory / Playground / Wegent
● Community wecode-ai ⚡ Instant

Wegent

by wecode-ai · wecode-ai/Wegent

Define agent teams in YAML — Wegent runs them, manages shared memory, and routes work between specialists.

Wegent treats agent teams as a declarative artifact: write a YAML spec of roles, hand-offs, and shared memory; Wegent provides the runtime. Useful when you outgrow a single-agent prompt.

Why use it

Key features

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "wegent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wecode-ai/Wegent"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "wegent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wecode-ai/Wegent"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "wegent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wecode-ai/Wegent"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "wegent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wecode-ai/Wegent"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "wegent-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wecode-ai/Wegent"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "wegent-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/wecode-ai/Wegent"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add wegent-skill -- git clone https://github.com/wecode-ai/Wegent

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Wegent

Stand up a specialist team

👤 Claude Code users ⏱ ~15 min intermediate

When to use: One agent isn't enough; you want hand-off between specialists.

Flow
  1. Spec
    Write team.yml — roles + hand-offs.✓ Copied
    → Spec ready
  2. Run
    wegent run team.yml task.md.✓ Copied
    → Agents work in turn
  3. Inspect
    Check trace.✓ Copied
    → Documented run

Outcome: Multi-agent run without bespoke orchestrator code.

Combinations

Pair with other MCPs for X10 leverage

wegent-skill + harness-skill

Use Harness to design the team; Wegent to run it

Combine wegent-skill with harness-skill: Use Harness to design the team; Wegent to run it✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
run / inspect (see docs) Two flows 1 call

Cost & Limits

What this costs to run

API quota
Per provider
Tokens per call
N × normal
Monetary
Free OSS; LLM costs
Tip
Cap per-role token budgets

Security

Permissions, secrets, blast radius

Minimum scopes: multi-provider keys
Credential storage: Keys in env
Data egress: Configured providers

Troubleshooting

Common errors and fixes

Hand-off loops

Add explicit exit conditions per role

Alternatives

Wegent vs others

AlternativeWhen to use it insteadTradeoff
Hand-rolled orchestrationSingle-team needsNo declarative spec

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills