# MCP troubleshooting

### The client cannot see tools

Check the address `https://api.viralmaxing.com/api/mcp` and use HTTP transport. Remove a trailing slash, custom headers, and API keys from the OAuth configuration. Reconnect the server and call `tools/list` again.

### Sign-in keeps opening

The token may have expired or the connection may have been revoked. Open [Settings → API keys](/settings/api), check connected agents, and start sign-in again. If the client retains the old session, remove the server from the client and add it again.

### The agent sees the wrong data

Call `list_workspaces` and check the current workspace. Switching through MCP changes context only for that connection. It does not change the workspace open in the user's app.

### A paid tool returns an error

Read the quoted price first. Get the user's approval and pass the exact value as `confirm_cost`. A different amount is rejected. Retrying cannot fix an inactive plan or insufficient energy.

### The server returns 401

The client did not send a valid token. Refresh the OAuth session or sign in again. For unattended server automation, use an [API key](/developers/rest/authentication).

### The server returns 403

The connection is valid, but the workspace role does not allow this operation. Ask the workspace owner to perform the action or provide suitable access.

If these checks do not resolve the problem, open support from the documentation header. Include the client name, error text, and request time. Do not send tokens or keys.