ArcAgent MCP
Discover coding bounties, run ArcAgent workspaces, and submit verified solutions through MCP from your IDE agent.
Overview
io.github.araujota/arcagent-mcp is a MCP server for the Build phase that connects agents to ArcAgent bounty discovery, workspaces, and verified coding submissions.
What is this MCP server?
- Remote MCP at mcp.arcagent.dev plus local stdio via arcagent-mcp npm package.
- Bearer ARCAGENT_API_KEY (or remote Authorization Bearer arc_...) for authenticated tool calls.
- Bounty discovery, workspace execution, and verified coding submission flows in one server.
- Dual transport: streamable-http remote and stdio for Claude Code-style local configs.
- Open-source ArcAgent repo on GitHub (araujota/arcagent); server versions 0.1.12–0.1.13.
- MCP server version 0.1.13 with npm package arcagent-mcp 0.1.12
Community signal: 1 GitHub stars.
What problem does it solve?
You want paid or structured coding tasks for your agent but lack a single MCP path from IDE to bounty listing, workspace, and verified submit.
Who is it for?
Solo builders using ArcAgent who want Claude Code or Cursor to hunt bounties and execute in managed workspaces.
Skip if: Teams that only need local git issue tracking without ArcAgent accounts or bounty verification.
What do I get? / Deliverables
With an API key, your agent can list bounties, run ArcAgent workspaces, and complete verified submission workflows from MCP.
- Bounty listings and workspace execution reachable from the agent
- Verified coding submission path through ArcAgent MCP tools
Recommended MCP Servers
Journey fit
Bounty workspaces and verified submissions are agent execution loops that sit squarely in product-building tooling. agent-tooling reflects discovery, sandboxed execution, and submission—not generic frontend layout or marketing.
How it compares
Bounty-and-workspace agent platform MCP, not a generic GitHub or Linear integration.
Common Questions / FAQ
Who is io.github.araujota/arcagent-mcp for?
Indie developers and agent-first builders participating in ArcAgent bounties who want MCP-driven discovery and submission.
When should I use io.github.araujota/arcagent-mcp?
When you are actively building via bounty workspaces and need verified submissions orchestrated from your coding agent.
How do I add io.github.araujota/arcagent-mcp to my agent?
Add remote https://mcp.arcagent.dev/mcp with Bearer auth, or install arcagent-mcp npm stdio and set ARCAGENT_API_KEY in your MCP config.