Troubleshoot the ezeep MCP connection
Choose the symptom that matches your connection.
On this page
- No tools: check the MCP endpoint and client support, then restart
- Sign-in loops: restart sign-in and check browser pop-up and cookie settings
- Authorization expired: disconnect MCP and complete a fresh sign-in
- Action refused: check the connected account’s roles and scopes
- Printer or Connector ID fails: fetch a fresh list and use its IDs
- List incomplete: ask for every page of groups or Connectors
- File-type answer too broad: ask specifically for supported extensions
- Invitation missing: check delivery in the portal before sending it again
- Job accepted but not printed: check the job, Connector and printer
[Step] 1. No tools: check the MCP endpoint and client support, then restart
- Check the endpoint is exactly https://mcp.ezeep.com/mcp.
- Confirm that the AI client supports remote HTTP MCP servers.
- If using a configuration file, check its syntax and the client’s required format.
- Restart the client after making changes.
[/Step]
[Step] 2. Sign-in loops: restart sign-in and check browser pop-up and cookie settings
Close the sign-in window and start the connection again from the AI client. Check whether the browser is blocking pop-ups or cookies needed by the sign-in page.
[/Step]
[Step] 3. Authorization expired: disconnect MCP and complete a fresh sign-in
Disconnect the ezeep server in the client, then reconnect and complete a fresh sign-in. Reusing the existing connection does not force reauthorization.
[/Step]
[Step] 4. Action refused: check the connected account’s roles and scopes
Ask which account, organization and roles the ezeep connection uses. Reconnect with the appropriate account if they are wrong. For OAuth-client registration, also check the accounts scope.
[/Step]
[Step] 5. Printer or Connector ID fails: fetch a fresh list and use its IDs
Ask for a fresh printer or connector list and use the returned ID. A nonexistent printer ID can produce an empty properties result rather than an error.
[/Step]
[Step] 6. List incomplete: ask for every page of groups or Connectors
Groups and connectors paginate. Ask the assistant for every page and compare the total count.
[/Step]
[Step] 7. File-type answer too broad: ask specifically for supported extensions
Ask specifically for the supported file extensions. The underlying configuration response contains other system details.
[/Step]
[Step] 8. Invitation missing: check delivery in the portal before sending it again
Check the invitation’s delivery state in the ezeep portal before sending another. An open invitation with a future expiry date does not prove its email was delivered.
[/Step]
[Step] 9. Job accepted but not printed: check the job, Connector and printer
Ask for offline ezeep connectors, then check the submitted job’s status. Verify the connector and printer in the portal.
A working printer-list request confirms basic MCP connectivity; it does not verify physical printing. Continue with connector troubleshooting or Hub troubleshooting as appropriate.
[/Step]