Connect Claude Code

Claude Code connects to remote MCP servers over HTTP and can send custom headers, so it talks to your site directly — no bridge needed. Both commands below were tested with Claude Code 2.1: each server reported Connected in claude mcp list.

First prepare your site: choose WooCommerce MCP or the MCP Adapter, create the credential and the Raqvio Agent Guardrails agent.

Add the server

Run one of these in your terminal.

WooCommerce MCP (API key):

claude mcp add --transport http my-store https://your-store.example/wp-json/woocommerce/mcp --header "X-MCP-API-Key: ck_your_key:cs_your_secret"

MCP Adapter (application password) — the header carries the Base64 of user-name:application-password, computed here by the shell:

claude mcp add --transport http my-site https://your-store.example/wp-json/mcp/mcp-adapter-default-server --header "Authorization: Basic $(printf '%s' 'agent-user:abcd efgh ijkl mnop qrst uvwx' | base64)"

By default the server is added for the current project only and stored in your user settings, not in the project folder. Add --scope user to make it available in every project. Avoid --scope project for these servers: it writes the configuration, including the credential, to a .mcp.json file in the project that is meant to be shared.

Check the connection

claude mcp list

The server should be listed as connected. In a Claude Code session, /mcp shows its status and tools. Then check that it works in Raqvio Agent Guardrails’s audit log.

To remove it later: claude mcp remove my-store.

Troubleshooting

• Self-signed HTTPS on a local development site: start Claude Code with NODE_EXTRA_CA_CERTS=/path/to/your-site.crt claude so it trusts the certificate.
• 401 Unauthorized: the key or password is wrong, or the WooCommerce key belongs to a different user than the one bound to your agent.