Connect WowInvoice to compatible desktop applications and command-line interface (CLI) tools using WordPress application passwords. These methods support reachable live and locally hosted websites.
| Application | Connection Method |
|---|---|
| Claude Desktop, Cursor, Windsurf | Local bridge using mcpServers |
| VS Code | Local bridge using servers and type: stdio |
| Claude Code, Gemini CLI | Direct HTTP with an Authorization header |
Before You Begin
- Complete Getting Started with WowInvoice MCP.
- Set Access Mode to Read only and save.
- Ensure your computer can reach your website.
- Confirm that WordPress application-password authentication is available.
Use HTTPS for live or remote websites. Local development environments may use HTTP where authentication is supported.
Create a WordPress Application Password
- Navigate to WooCommerce → WowInvoice → AI Tools → Connect an AI assistant.
- Select Desktop apps or CLI tools.
- Click Create an application password.
- Under Application Passwords, enter a name identifying the application.
- Click Add New Application Password.
- Copy and securely store the generated password.
WordPress displays the password only once. Create a separate application password for each client so you can revoke access individually.
Connect Desktop Apps Using the Local Bridge
Install Node.js on your computer and ensure npx is available to your application.
Claude Desktop, Cursor and Windsurf
- Copy the Desktop app configuration from WowInvoice.
- Replace the website address, username and application-password placeholders.
- Add the configuration to your application’s MCP configuration file.
- Save the file and restart the application.
| Application | Configuration File |
|---|---|
| Claude Desktop | claude_desktop_config.json |
| Cursor | .cursor/mcp.json |
| Windsurf | mcp_config.json |
Example configuration:
{
"mcpServers": {
"wowinvoice": {
"command": "npx",
"args": ["-y", "@automattic/[email protected]"],
"env": {
"WP_API_URL": "http://example.local/wp-json/winv/mcp",
"WP_API_USERNAME": "YOUR-WORDPRESS-USERNAME",
"WP_API_PASSWORD": "YOUR-APPLICATION-PASSWORD",
"OAUTH_ENABLED": "false"
}
}
}
}Use the appropriate configuration-file location for your application.
If mcpServers already exists, merge the wowinvoice entry without removing existing servers. Keep OAUTH_ENABLED set to "false".
Always prefer the configuration generated by your installed WowInvoice version.
VS Code
VS Code uses a different MCP configuration format.
Copy the VS Code configuration from WowInvoice and add it to .vscode/mcp.json.
{
"servers": {
"wowinvoice": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@automattic/[email protected]"],
"env": {
"WP_API_URL": "http://example.local/wp-json/winv/mcp",
"WP_API_USERNAME": "YOUR-WORDPRESS-USERNAME",
"WP_API_PASSWORD": "YOUR-APPLICATION-PASSWORD",
"OAUTH_ENABLED": "false"
}
}
}
}Replace the example server address and credential placeholders. Merge the WowInvoice entry into any existing servers object, save the file and restart the application.
Local bridge connections use your application password directly. Base64 encoding is not required.
Connect CLI Tools Using Direct HTTP
Claude Code and Gemini CLI authenticate through a Basic Authorization header containing your WordPress username and application password encoded in Base64.
Generate Your Base64 Credentials
Open Bash on macOS, Linux or Git Bash on Windows and run:
read -r -p "WordPress username: " winv_user
read -r -s -p "Application password: " winv_pass
printf '\n'
printf '%s:%s' "$winv_user" "$winv_pass" | base64 | tr -d '\r\n'
printf '\n'
unset winv_user winv_passEnter your actual WordPress username and generated application password when prompted.
Copy the resulting value and use it wherever the configuration says BASE64-CREDENTIALS.
Important: Base64 is encoding, not encryption. Treat the encoded value as a password and never use public online encoders.
Connect WowInvoice to Claude Code
Use the Claude Code command provided by WowInvoice or adapt this example:
claude mcp add --transport http wowinvoice \
'http://example.local/wp-json/winv/mcp' \
--header 'Authorization: Basic BASE64-CREDENTIALS'Replace the example server address and encoded credential placeholder before running the command.
Run claude mcp list, then use /mcp inside Claude Code to check the connection and available tools.
See Claude Code MCP documentation for additional configuration details.
Connect WowInvoice to Gemini CLI
Open or create ~/.gemini/settings.json and add the Gemini CLI configuration from WowInvoice.
{
"mcpServers": {
"wowinvoice": {
"httpUrl": "http://example.local/wp-json/winv/mcp",
"headers": {
"Authorization": "Basic BASE64-CREDENTIALS"
}
}
}
}Replace the example server address and encoded credential placeholder. Merge the WowInvoice entry into any existing mcpServers object.
Save the file, restart Gemini CLI and run /mcp to check the connection and available tools.
See Gemini CLI MCP documentation.
Test Your Connection
Enable WowInvoice in your application and send the prompt under Confirm your AI can read this store from the WowInvoice AI Tools page.
Confirm that a connected tool returns your actual document types and publication status.
This verifies read access, not PDF generation or Full access permissions.
Revoke Application Access
Navigate to Users → Profile → Application Passwords, revoke the relevant password and remove the saved credentials from your application.
Keep authentication values, configuration files, terminal history and output private. Never commit credentials to shared repositories.
For additional information, see the WordPress Application Passwords documentation and Automattic MCP WordPress Remote documentation.
For connection issues, see Troubleshooting WowInvoice MCP Connections.