We gave Claude and Codex a sales and marketing system through MCP

Description and use

Claude and Codex can now complete full sales and marketing workflows using a remote MCP server that exposes a dynamic set of AXL tools, integrating pages, CRM, payments, and courses without manually wiring dozens of apps.

Problem

Integrate a large, multi‑app business stack into a single conversational agent without wiring dozens of tools into the prompt.

Outcome

Claude and Codex can now finish end‑to‑end sales and marketing workflows—building pages, capturing leads, processing payments, enrolling buyers, and setting up follow‑up—without manual wiring of individual tools.

Workflow

• 1. Agent connects to MCP via "claude mcp add --transport http axl https://app.axl.tech/mcp" and signs in through OAuth.
• 2. Agent receives a limited tool set and searches the live operation catalog.
• 3. Agent executes operations (e.g., create landing page, add form, set up checkout, enroll buyer in course).
• 4. Agent prepares review links and returns them to the user for approval.
• 5. Agent completes any remaining steps such as file uploads using pre‑signed URLs.

Evidence

Most MCP demos connect an agent to one narrow tool. We wanted Claude and Codex to finish a whole customer workflow without wiring five apps together.

Source

We built a remote MCP server so an agent can work across that system from the chat its user already has open.

Source

The endpoint is: https://app.axl.tech/mcp

Source

The browser opens for sign‑in. You choose the AXL account, approve the connection and return to the agent. There is no API key to paste into chat.

Source

AXL keeps those events on the same customer record, so the agent doesn't have to match IDs across a page builder, CRM, checkout, course platform and email tool.

Source

We also remove 21 sensitive operations from the AI surface. The agent cannot use MCP to mint tokens, change administrator permissions or perform billing writes.

Source