How to Connect OpenAI Codex to Conveliq with MCP

Connecting Codex to Conveliq with MCP turns a coding agent into a workspace-aware sales operations assistant. It can inspect contacts, summarize WhatsApp conversations, review orders and bookings, maintain business knowledge, and help tune your sales agent. You decide which actions it may take and can disconnect it at any time.

MCP stands for Model Context Protocol. It gives an AI client a standard way to discover and call tools exposed by another product. Conveliq uses the MCP OAuth 2.1 authorization flow, so Codex receives a workspace-scoped token after you sign in and approve access. You do not copy a Conveliq API key into Codex.

What you need before setup

You need an active Conveliq workspace and a current Codex app, CLI, or IDE extension. The Conveliq Streamable HTTP endpoint is https://app.conveliq.com/api/mcp. There is no local bridge to install and no client environment variable to create.

Configure the remote MCP server

Open ~/.codex/config.toml, or a trusted project's .codex/config.toml when the connection should be project-scoped. Add [mcp_servers.conveliq], set url to https://app.conveliq.com/api/mcp, set auth to "oauth", and keep default_tools_approval_mode set to "writes".

Restart Codex after saving the configuration. Open MCP servers in the Codex app or IDE and choose Authenticate. In the CLI, run codex mcp login conveliq. Codex discovers Conveliq protected-resource and authorization-server metadata automatically.

Your browser opens the normal Conveliq login. After sign-in, the consent screen names the active workspace and shows the requested read and write permissions. Choose Authorize only when the workspace and client name are correct.

Codex completes authorization-code exchange with PKCE, stores the resulting credentials, and refreshes them when needed. Your Conveliq password never goes to Codex, and a token issued for the MCP endpoint cannot be used as a general Conveliq session.

Run a read-only verification first

Start with: "Use Conveliq to show my workspace overview. Read only and do not change data." A successful result identifies the organization and summarizes connected channels, contacts, messages, escalations, orders, and bookings.

Next, ask Codex to list five recent conversations and summarize them. Follow with a contact lookup. Reading first confirms that Codex is operating on the intended workspace before you approve a tool that changes data.

Useful daily workflows

A sales manager can ask, "Show qualified leads that have not received a useful reply today, then prepare a prioritized call list." A support lead can ask for unresolved escalations. A founder can compare new orders, bookings, and hot leads in one briefing.

Codex can maintain the knowledge base. Give it an approved service name, description, price range, and FAQ, then ask it to create the entry and read it back. For broader CRM habits, see our WhatsApp CRM guide for online stores.

Write actions need more care. Conveliq labels contact updates, message sending, agent configuration changes, and knowledge creation as write tools. Keep write approvals enabled, draft customer replies before sending, and verify recipient, tone, prices, and promises.

For advanced agent configuration, ask Codex to read the current settings and propose a small diff. A focused request such as "add a rule to escalate qualified enterprise buyers without changing the existing tone" is easier to review and safer to reverse than a broad rewrite.

Common connection mistakes

A 401 response normally means authentication has not completed or a stored token has expired or been revoked. Run codex mcp login conveliq again. If the server does not appear after editing config.toml, restart the Codex host and verify the endpoint URL.

Opening the MCP URL in a normal browser returns a method message because protocol calls use HTTP POST. The OAuth discovery URLs are separate and are fetched automatically by the client.

If a write tool asks for more access, review the scope prompt before reauthorizing. If data is empty, confirm that the selected Conveliq workspace owns an active channel and has received customer messages.

MCP complements automation rather than replacing it. Conveliq continues answering customers and scoring leads. Codex helps an owner investigate, review, and operate the system through explicit tools. Compare that model in our WhatsApp automation tools guide.

To disconnect, remove the Conveliq entry or clear its OAuth authentication in Codex. Conveliq access tokens are short-lived and refresh tokens rotate, while the OAuth revocation endpoint lets a client invalidate stored credentials.

The complete tool list, ChatGPT web setup, Claude guide, and example prompts are on the Conveliq MCP page. Begin with the read-only overview and let Conveliq keep customer-facing changes visible for approval.