Integrations
Integrations
Prerequisites and overview of ArxDeck integrations documented in v1.
Integrations overview
ArxDeck connects to external tools through organization credentials, per-project settings, and HTTP APIs. This section covers integrations with dedicated public documentation in v1.
Prerequisites
Most integrations require:
- Project admin access on the target project
- For provider API keys — organization admin access to Organization → API keys (optional per-org overrides; otherwise the deployment uses platform-managed credentials). See Organizations.
- A clear GitHub repository link when agents or Publish need repo access
Agents never store raw secrets in agent JSON — credentials resolve from organization or platform configuration at run time.
Documented integrations (v1)
| Integration | Purpose |
|---|---|
| MCP | ArxDeck MCP server for agents and chat during runs |
| GitHub | Repository link, docs browse, PRs on tickets, collaborator management |
| Managed deployments | Publish — deploy supported web apps to managed hosting |
| Content modules | Install global workflow, agent, and knowledge bundles |
| Inbound webhooks | Receive external HTTP events into webhook tasks |
| Feedback ingest API | External bug and feature submissions into project feedback |
Briefly supported (no v1 setup guide here)
The product also supports orchestration via Cursor Cloud, Claude Managed Agents, OpenRouter chat, and a local Windows desktop agent. Configure these from dashboard agent settings and provider consoles. See Agents overview.
Related
- Organizations
- ArxDeck Helper — guided setup for workflows, agents, and module-backed resources
- FAQ — supported vs deferred capabilities