CODAROQ MCP · GETTING STARTED

From installation to your first completed task

Install CodaRoq MCP on your own WordPress website, connect your AI client and give it a clear task. Start with a small operation, inspect the result, then expand the work you authorize.

Compare editions · Download MCP Core · My account · Support

1. Check the requirements

• Your own HTTPS WordPress website, WordPress 6.9+ and PHP 7.4+. Paid activation needs the OpenSSL PHP extension.
• Permission to install plugins and authorize the connection on that website.
• A compatible remote MCP client with OAuth support. AI-client subscriptions, model usage and hosting are separate from your CodaRoq plan.
• WooCommerce for Commerce tools. Enterprise mail, accounting and other adapters require their matching plugins and configuration.

This is a self-hosted connection. CodaRoq is not yet a public ChatGPT-directory installation. Check that your account allows custom MCP connections before buying for ChatGPT use.

2. Install the plugin

1. Download Core using the link above, or use the personal MCP link in your purchase email.
2. In your own WordPress administration, open Plugins → Add New → Upload Plugin, select the ZIP and install it.
3. Activate CodaRoq MCP. Open Settings → CodaRoq MCP and confirm the server is enabled.

Core, Commerce and Enterprise use the same plugin. If Core is already installed, upload the new ZIP and replace the existing CodaRoq MCP version; do not install two copies. Documents Free and Documents Pro are separate products and are not required to run MCP.

3. Activate Commerce or Enterprise

Core is free and needs no key. For a paid edition, choose the edition you purchased under Settings → CodaRoq MCP, enter its key from your email and select Activate / recheck license.

Each paid subscription activates one WordPress installation. Activating sends your key, edition, installation identifier and site URL to codaroq.com. The key is stored encrypted. Your WordPress password is not sent to your AI client.

4. Connect your AI client

Copy the exact MCP endpoint displayed in the plugin settings. It belongs to your website and usually looks like https://your-site.example/wp-json/codaroq-mcp/v1/mcp. Do not use codaroq.com’s endpoint for your own site.

ChatGPT

On the web, enable Developer mode under Settings → Security and login if available. Open Plugins, use the plus button to create a custom MCP connection, paste your endpoint and choose OAuth. Use CIMD where offered. Follow the WordPress sign-in and consent screen, then select the connection in your conversation. Workspace administrators may restrict this feature. Official instructions

Codex and other clients

Configure a remote MCP server using your endpoint and OAuth, then sign in. Codex CLI supports codex mcp login <server-name>. Follow your client’s current setup instructions; callback URLs and registration options depend on the client. Official Codex MCP guide

Leave Dynamic Client Registration disabled for supported OpenAI CIMD connections. Do not enable it just to suppress an unexplained error. For another client, contact support with the client name/version and the error message.

5. Approve the work you want to automate

OAuth permissions and your WordPress user’s permissions both apply. Reading content does not require publication or deletion permission. Grant writing and publication scopes when you want the client to perform those tasks. Refresh the client’s tool list after upgrading an edition or adding a module.

Try these prompts:

• Core: “Use my CodaRoq connection to show the site status and list the published pages.”
• Core: “Create a draft FAQ page from this text. Leave it as a draft and give me its link.”
• Commerce: “Find products without a featured image. Show me the affected products before changing anything.”
• Commerce: “For product 123, change only the description to this approved text and read it back after saving.” Replace 123 with your actual product ID.
• Enterprise: “Use the configured mail module to list the available inbox work cases.” This requires Mail Agent and its mailbox to be configured.

The MCP executes requests from your client. Scheduled, unattended recurring work also needs a scheduler in that client or your infrastructure. Client approval settings may require confirmations. The plugin does not independently run a background AI employee.

6. Enterprise integration support

Enterprise includes all currently available MCP module adapters plus priority support and direct coordination for further plugin integrations. Contact info@codaroq.com with your order number, plugin name/version, desired workflow and whether a staging site is available.

We assess the plugin’s available interfaces and agree the implementation scope directly. New plugins are not automatically compatible. Third-party licenses and services are separate. Never send passwords, license keys or API secrets in the request.

Downloads, renewals and moving a license

• Free downloads require no account. A personal paid download link also works without login, but expires after 36 hours. A fresh link is available in My account → Licenses while your license is active.
• The wp-admin/admin-post.php path is a download handler; it does not grant administration access.
• Commerce is CHF 500/year and Enterprise CHF 3’000/year. They renew annually until cancelled. Manage cancellation through My account → Subscriptions. Paid access continues through the current paid term; afterwards Core remains available.
• Before moving a paid license to another domain, use Release license from this site on the old site, then activate it on the new one.
• Plugin updates appear in the normal WordPress update screen. Review your backup and update procedure before applying them.

Translation Package: optional paid MCP workflow

CodaRoq Translation Package costs CHF 100 once for one website and works fully in WordPress without MCP. To use its MCP tools, install Translation and CodaRoq MCP 1.6.0+ on the same site and activate a Commerce or Enterprise subscription. The combined setup needs PHP 8.1+ and WordPress 6.9+.

1. Authorise only the required translation.read, translation.write, translation.approve, translation.publish and translation.diagnostics scopes. WordPress object permissions also apply.
2. Read the source and current version, create a target draft, then prepare a text proposal.
3. Review the exact proposed text and explicitly apply it. Approve the current draft, then publish in a separate action.
4. If the source or target has changed, reload and review before retrying. Edit already published translations in the WordPress backend.

Example: “Prepare a French draft of product 123. Show me the proposed title and description before applying them.” No price, stock or order data is writable through the Translation tools. Core and expired MCP subscriptions do not unlock these tools; local Translation use continues.

Troubleshooting

For support, include your order number if applicable, WordPress/PHP/plugin versions, client name and the exact error. Remove private data from screenshots.