Arcar Mcp
Wire your coding agent to arcar.org services over MCP without hand-rolling API glue.
Overview
io.github.arcar-org/arcar-mcp is a MCP server for the Build phase that connects coding agents to arcar.org via a hosted SSE remote.
What is this MCP server?
- Remote SSE MCP endpoint at nave.q2bot.com/mcp/arcar-org
- Server schema version 1.0.4 on the 2025-12-11 MCP registry format
- stdio-free hosted remote suitable for Claude Desktop and HTTP-capable clients
- Purpose-built for arcar.org integration scenarios described in the registry
- Published server version 1.0.4
- Single SSE remote: https://nave.q2bot.com/mcp/arcar-org
What problem does it solve?
Your agent cannot reach arcar.org unless you duplicate integration code in every repo and prompt.
Who is it for?
Builders already on arcar.org who want a quick MCP hook for agent-driven automation.
Skip if: Teams that need self-hosted stdio, offline use, or documented tool lists before trusting the server.
What do I get? / Deliverables
After you register the SSE remote, the agent can invoke arcar.org-oriented MCP tools from one stable endpoint.
- Registered SSE MCP connection to arcar.org integrations
- Agent-callable MCP tools backed by the remote server
Recommended MCP Servers
Journey fit
How it compares
MCP integration bridge to arcar.org, not a reusable Claude skill with invokeWhen rituals.
Common Questions / FAQ
Who is io.github.arcar-org/arcar-mcp for?
Solo and small-team builders using arcar.org who want their Claude Code, Cursor, or Codex agent to call org integrations through MCP instead of custom scripts.
When should I use io.github.arcar-org/arcar-mcp?
During Build when you are wiring agent-tooling or backend integrations and arcar.org is part of your stack.
How do I add io.github.arcar-org/arcar-mcp to my agent?
Add the remote MCP server URL https://nave.q2bot.com/mcp/arcar-org with type sse in your client’s MCP config, then restart the session and verify tools load.