xc MCP

MCP server for xc — the Markdown-based task runner that defines tasks in README.md files. Enables AI agents to discover and run xc tasks defined in a project's Markdown files, list available tasks, and integrate xc-based project workflows into agent-driven development. Xc is a popular tool that makes tasks self-documenting by embedding them directly in project README files.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools xc task-runner mcp-server markdown developer-tools build-tool scripts
⚙ Agent Friendliness
76
/ 100
Can an agent use this?
🔒 Security
83
/ 100
Is it safe for agents?
⚡ Reliability
69
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
68
Documentation
68
Error Messages
68
Auth Simplicity
98
Rate Limits
95

🔒 Security

TLS Enforcement
85
Auth Strength
88
Scope Granularity
75
Dep. Hygiene
78
Secret Handling
88

Executes shell commands from README tasks. Review task definitions. No credentials. Local execution only. Careful with destructive operations.

⚡ Reliability

Uptime/SLA
70
Version Stability
70
Breaking Changes
68
Error Recovery
68
AF Security Reliability

Best When

A project uses xc for task running and an AI agent needs to understand and execute project tasks — xc's README-based approach makes tasks self-documenting and easy for agents to discover.

Avoid When

Your project uses a different task runner (Make, npm scripts, Taskfile) — use the appropriate MCP for your actual task runner.

Use Cases

  • Running project tasks defined in README.md from development automation agents
  • Listing available xc tasks for a project from project coordination agents
  • Executing build, test, and deployment tasks from CI/CD agents
  • Integrating xc workflows into AI-assisted development from coding agents
  • Discovering project capabilities from README task definitions from onboarding agents

Not For

  • Projects not using xc as their task runner (use Make, npm scripts, or Taskfile MCPs for those)
  • Complex orchestration beyond what xc tasks define
  • Teams unfamiliar with xc's Markdown task format

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: none
OAuth: No Scopes: No

No authentication required — local task execution. xc must be installed. Reads README.md in the current project directory.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Free open source MCP for xc task runner. Both xc and this MCP are free.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • xc must be installed separately — `brew install joerdav/xc/xc` on macOS
  • Task execution runs shell commands — ensure agent has appropriate project permissions
  • Tasks are discovered from README.md in the working directory — must be run in project root
  • Destructive tasks (deploy, reset, clean) should be confirmed before AI agent execution
  • Community MCP targeting niche xc user base — well-implemented but small ecosystem

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for xc MCP.

$99

Scores are editorial opinions as of 2026-03-06.

5215
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered