# CONXA

CONXA turns recorded browser workflows into local MCP skills that Claude Desktop and other MCP-capable clients can execute through an installed runtime.

## Priority topics

- Claude automation: CONXA packages reviewed workflows as local MCP skills so Claude Desktop can invoke reliable browser workflow automation.
- Claude Desktop automation: the installed CONXA runtime registers as an MCP server and executes skills locally on the end user machine.
- MCP automation: the Model Context Protocol connects AI clients to prepared CONXA skills with input schemas, execution status, cancellation, package refresh, and permitted metadata reads.
- Local execution: browser sessions, target-application credentials, and runtime state stay on the customer machine; CONXA Cloud coordinates packages, installers, billing, updates, and telemetry.
- Safe use: automations should only be built and distributed for workflows, accounts, products, and data the user is authorized to operate.

## Canonical docs

- Docs index: https://www.conxa.in/docs
- Claude Automation With CONXA: https://www.conxa.in/docs/claude-automation
- Runtime And MCP Execution: https://www.conxa.in/docs/runtime
- Platform Overview: https://www.conxa.in/docs/platform
- Security: https://www.conxa.in/docs/security
- Acceptable Use: https://www.conxa.in/docs/acceptable-use

## All public docs

- Platform Overview: https://www.conxa.in/docs/platform - How Conxa turns recorded software workflows into local MCP skills that AI tools can execute reliably.
- Claude Automation With CONXA: https://www.conxa.in/docs/claude-automation - How Conxa packages browser workflow automation as local MCP skills that Claude Desktop can invoke safely.
- Build Studio: https://www.conxa.in/docs/build-studio - How builders record, edit, compile, test, and package workflows before publishing them to Conxa Cloud.
- Build Studio: Step-By-Step Guide: https://www.conxa.in/docs/build-studio-guide - A plain-language walkthrough of installing Build Studio, recording an automation, reviewing it, and publishing it to your team, plus troubleshooting and FAQ.
- Conxa Cloud: https://www.conxa.in/docs/cloud - What the cloud dashboard and backend coordinate for published skill packages, billing, teams, telemetry, and updates.
- Runtime And MCP Execution: https://www.conxa.in/docs/runtime - How the installed runtime exposes local browser workflow automation to Claude Desktop or another MCP client and executes skills locally.
- Security: https://www.conxa.in/docs/security - Security boundaries, local execution guarantees, auth handling, token storage, and practical operational limits.
- Privacy Policy: https://www.conxa.in/docs/privacy - How CONXA collects, uses, stores, shares, and protects information across the website, dashboard, Build Studio, cloud services, and runtime telemetry.
- Terms And Conditions: https://www.conxa.in/docs/terms - Terms for using CONXA websites, dashboard, Build Studio, cloud APIs, package hosting, installers, and runtime services, including the Build Studio software licence.
- Cookie Policy: https://www.conxa.in/docs/cookies - How CONXA uses essential cookies and similar technologies for authentication, checkout, security, and service operation.
- Billing And Refund Policy: https://www.conxa.in/docs/billing - Plans, visible meters, checkout behavior, cancellations, refunds, failed payments, and enterprise billing defaults.
- Acceptable Use Policy: https://www.conxa.in/docs/acceptable-use - Rules for safe, lawful, and authorized use of CONXA workflow recording, packaging, installers, runtime, and cloud services.
- Data Processing: https://www.conxa.in/docs/data-processing - Plain-language explanation of customer and CONXA data roles, subprocessors, local-only data, deletion requests, and enterprise DPA expectations.
- Support: https://www.conxa.in/docs/support - How to contact CONXA for product help, billing questions, security reports, privacy requests, and enterprise procurement.