Connect your agent to the right site.
The connection depends on three things: a reachable endpoint, supported authentication, and tools enabled for the account being used.
Use your installation’s connection details
Open Avius in WordPress and copy the connection details provided for your client. An MCP endpoint is a tool connection, not the public homepage URL.
Confirm the site name and environment before authorizing. A staging site and a production site may look similar while pointing at very different data.
Check the client’s connection method
Clients such as Claude and Cursor support MCP, but their interfaces, transports, and account requirements differ. A local desktop connection and a remote cloud connector are not interchangeable.
Follow the current client documentation alongside the connection instructions generated by Avius. Keep secrets in the client’s supported credential configuration, not in an ordinary prompt.
- Claude remote connectors run from the provider’s infrastructure, so the endpoint must be reachable there.
- Cursor MCP configuration supports remote-server details and authentication settings.
- For another client, confirm its transport and authorization support before troubleshooting the plugin.
Confirm the tools, then the task
Check that your client can discover the expected tools. Start by asking it to inspect the active plugins without making changes.
If authentication works but the tool list is empty, review enabled abilities, account permissions, and the client’s cached connection. Avoid repeatedly changing credentials before identifying the failing step.
Diagnose a failed connectionCurrent client references
Provider instructions change independently of Avius. Use these official references for the client-side setup.