MCP operator and connection guide

Choose the correct MCP surface

Cointacted MCP has two separate trust boundaries. Free provides the administrator operations server for trusted operators using WordPress administrator authentication. Pro can provide a user MCP server that connects an individual registered account through OAuth 2.1 and exposes only that user's approved account and terminal scopes.

For administrator clients, use WordPress Application Passwords over HTTPS or an authenticated WordPress cookie plus REST nonce. The operations endpoints include /wp-json/cointacted-mcp/v1/rpc, /tools, /tools/{name}, /health, and /telemetry/commands. The JSON-RPC endpoint supports initialize, tools/list, tools/call, and ping.

Administrator server setup

1. Open Cointacted → Operations MCP → Settings and enable only the administrator server.
2. Leave write tools disabled. Save and open the Status or Testing panel to confirm the REST base, authentication mode, and health response.
3. In Users → Profile, create a WordPress Application Password for the dedicated administrator account that will operate the MCP client. Do not reuse the normal account password.
4. Configure the client with the exact site HTTPS URL and application-password credentials, then call initialize, tools/list, and one read-only status tool.
5. Return to Cointacted → Operations MCP and review activity. The test must identify the client, tool, outcome, and time without storing tool arguments or credentials.

Enable the global write-tools switch only after every intended write tool has been reviewed separately. A tool remaining absent from tools/list is safer than exposing a generic mutation surface.

Connect a user client

First activate MCP Pro, then enable Cointacted → Operations MCP → Settings → User MCP connections. No OAuth discovery, consent, token, user endpoint, or connected-app surface is published while that switch is off. Then open Account Security → Connected MCP apps. If SnapWeb Auth is unavailable, publish [cointacted_mcp_connected_apps] on a signed-in account page. Copy the displayed server URL into a compatible client and complete the authorization-code flow with PKCE S256.

Approve only the scopes required:

• terminal:read lists commands available to the account.
• terminal:execute requests execution of commands with reviewed server handlers.
• account:read returns the connected user's basic profile.

Access tokens last 15 minutes. Refresh tokens rotate when used. Disconnecting an app revokes that client immediately.

Remote-command policy

Each command owner classifies remote access as read, execute, approval, or blocked. Unknown commands fail closed. Browser-only behavior, wallet signing, passwords, private keys, administrator commands, and commands without a server-safe handler are unavailable.

An approval command first returns a short-lived approval URL without running. The approval screen shows client, command, exact arguments, and expiry. Approval is bound to the same user, client, command, and arguments and can be consumed once; changing any field or replaying it fails.

Tools and write protection

Free includes safe inventories and status tools for the site, Cointacted products, integrations, capabilities, terminal commands, usage, AI, and Blockchain Core. Add-ons may register their own read-only status tools. MCP Pro can unlock guarded administrative tools, but the administrator must also enable the global write-tools switch and each callback must pass its own permission checks. There is no arbitrary shell, SQL, PHP, shortcode, or terminal bypass.

Privacy and troubleshooting

User authorization codes and tokens are stored only as hashes. Redirect URIs require exact matching. Activity retains client, tool, outcome, and time—not arguments. Default user activity retention is 90 days; Pro may configure up to 365 days.

• Client cannot connect: verify HTTPS, the exact server URL, redirect URI, PKCE S256, and system clock.
• Tool missing: check the owning add-on, current capability, tool registration, and Free/Pro profile.
• Command blocked: inspect its declared policy; unknown and browser-only commands cannot be forced through MCP.
• Approval expired: begin a new call and approve the newly issued request.
• Administrator receives 401/403: verify the WordPress user, Application Password, capability, and REST authentication headers.