> For the complete documentation index, see [llms.txt](https://docs.autentique.com.br/api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autentique.com.br/api/autentique-mcp/other-mcp-clients.md).

# Other MCP clients

Connection requirements for other remote MCP clients.

Use Autentique with any MCP client that supports remote Streamable HTTP servers and OAuth 2.0.

### Connection details

* **Name:** Autentique
* **Server URL:** `https://api.autentique.com.br/mcp`
* **Transport:** Streamable HTTP
* **Authentication:** OAuth 2.0 with PKCE

Do not paste an Autentique password, access token, or API key into the client configuration. The client should open the Autentique authorization page and complete OAuth interactively.

### Connect

1. Open the client's MCP or integration settings.
2. Add a remote HTTP MCP server.
3. Enter the Autentique server URL.
4. Start the connection.
5. Sign in on the Autentique authorization page.
6. Review the requested permissions and select **Allow**.
7. Return to the client and confirm that the tools were discovered.

### Verify the connection

Start with a read-only request:

“Show my Autentique profile and list the organizations I can access.”

Then test document discovery:

“List the documents that are awaiting signatures.”

### Client requirements

The MCP client must support:

* Remote Streamable HTTP transport.
* OAuth authorization for remote MCP servers.
* Tool discovery and invocation.
* User approval or another clear safety control for write actions.

If the client cannot open the authorization flow or does not support remote OAuth, it cannot connect to the Autentique MCP server securely.