Troubleshooting
Resolve common Autentique MCP connection and tool errors.
Use these checks when an MCP client cannot connect to Autentique or a tool does not behave as expected.
The connector asks you to sign in again
The authorization may have expired or been revoked. Reconnect the MCP server and approve the requested permissions again.
The authorization page does not open
Confirm that the client supports OAuth for remote Streamable HTTP MCP servers. Remove the connection, add the server URL again, and restart the authorization flow.
The client cannot discover tools
Confirm that the server URL is exactly:
https://api.autentique.com.br/mcp
Do not add another path or use the GraphQL API endpoint. Restart the client after changing its MCP configuration.
A document or organization cannot be found
Confirm that the connected Autentique user has access to the resource and that the correct organization context is being used. The MCP server cannot access resources that are not available to that user.
A document could not be created
Prepare a new upload and retry deliberately. Do not reuse an upload identifier after a failed creation attempt. Uploads expire after 15 minutes and are bound to the authenticated user, organization, filename, content type, and file size.
A write tool is unavailable
The authenticated user may not have the required permission, the document may no longer be editable, or the MCP client may restrict write actions. Review the connected account, the document status, and the client's approval settings.
Need help?
Visit the Autentique Help Center and include the client name, approximate time of the failure, and the action you were trying to perform. Never include passwords or OAuth tokens.
Last updated