ArxDeck
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)

IntegrationPurpose
Cursor CloudAsync repo-backed agents on tickets and in chat
Claude ManagedAsync managed sessions on Anthropic infrastructure
OpenRouterProject chat and lightweight sync automations
MCPArxDeck MCP server for agents and chat during runs
GitHubRepository link, docs browse, PRs on tickets, collaborator management
Managed deploymentsPublish — deploy supported web apps to managed hosting
Content modulesInstall global workflow, agent, and knowledge bundles
Inbound webhooksReceive external HTTP events into webhook tasks
Feedback ingest APIExternal bug and feature submissions into project feedback
Content managementHeadless collections and entries for static sites
AuthenticationApp-user login and provisioning for static clients

Briefly supported (no v1 setup guide here)

The product also supports a local Windows desktop agent. Configure it from dashboard agent settings and the desktop client. No dedicated public setup guide is available.