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

Description and use

Using MCP, Claude completed a full sales and marketing workflow—creating a landing page, form, checkout, course, CRM record, and follow‑up emails—without wiring multiple tools.

Problem

Integrate a large business stack into a single conversational agent without wiring many separate tools.

Outcome

The MCP server reduces context load by exposing only relevant operations, handles permissions via OAuth 2.1 PKCE, and removes sensitive operations from the AI surface, enabling a single agent to complete complex workflows.

Workflow

• 1. Connect Claude to MCP via "claude mcp add --transport http axl https://app.axl.tech/mcp" and sign‑in with OAuth.
• 2. Agent searches the live operation catalog and selects needed operations.
• 3. Agent executes operations (e.g., create landing page, form, checkout, course, CRM record, follow‑up emails).
• 4. Agent returns review links to the user before publishing.
• 5. User approves and publishes the content.

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

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

Source

Claude Code connects with one command: claude mcp add --transport http axl https://app.axl.tech/mcp

Source

That one request crosses several parts of a normal business stack. The page needs a form. The form needs a contact record. The checkout needs a product. A successful payment needs to give the buyer course access. The follow‑up emails need to know what that person bought.

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