Connect an AI client to Argorant.
Use Argorant as an OAuth-gated MCP data source for aggregate counts, company coverage, and redacted previews. Reveal and export remain account-controlled.
Paste this URL into an MCP-compatible client that supports remote servers and OAuth authorization. This is the production connector endpoint; package installs are only needed for a future optional local bridge.
In an MCP-compatible client, add the hosted Argorant server URL. No package install is required for clients that support remote MCP.
The OAuth flow ties the connector to an Argorant account. Tool access, limits, and admin behavior come from that account.
Use aggregate counts and redacted previews before revealing or exporting anything in the signed-in application.
Argorant runs as a hosted remote MCP server. Use the same connector URL across clients that support remote MCP and OAuth. If a client asks for package details, use the connector manifest endpoints below rather than an npm package name.
Add a custom web connector and use the remote MCP server URL.
Use a custom remote MCP connector in developer mode when available for the workspace.
Point your MCP client at the server URL and complete the OAuth authorization flow.
Before submitting Argorant to public connector directories, these checks should stay true in production.