Connect your tools directly
By CorpusIQ
You can now connect external tools straight to the CorpusIQ MCP server, without going through ChatGPT, Claude, or Perplexity. Tools like Clawbot, Hermes agents, CI runners, and IDE plugins sign in once with device login, receive a secure token, and reach every connector you have already authorized. No embedded browser. No client secret to store. This page explains what that means and when to use it.
The feature lives inside your dashboard. Authorize your connectors once, then point any external tool at the MCP server.
Set it up in your dashboardTwo ways to connect
CorpusIQ gives you two ways in. The first is through your assistant: you authorize your connectors in the dashboard and use them inside ChatGPT, Claude, or Perplexity. That is how most people start, and nothing about it changes.
The second is a direct MCP connection. An external tool connects straight to the CorpusIQ MCP server using device login. Both paths reach the same server and the same 25+ connectors. Pick whichever fits the tool in front of you. For the side-by-side, see the features page.
When to use device login
Device login is the right path when your tool runs outside a normal browser, a terminal, a daemon, a CI runner, an IDE plugin, or an agent loop, and you do not want to store or embed an OAuth client secret. It also keeps access scoped to the actual person signing in, so your connector permissions stay tied to you rather than a shared service account.
If your tool is a standard web app, or it is ChatGPT, Claude, or Perplexity, you do not need device login. Those clients ship their own browser sign-in and connect through that.
How it works
Device login follows the OAuth 2.0 Device Authorization Grant, a published standard. The shape is four steps, and you only touch one of them by hand:
- Your tool asks the MCP server to start a session and gets back a short code.
- The tool shows you that code and a link.
- You open the link in a browser on any device and sign in to CorpusIQ once.
- The tool receives a secure token and uses it for every request to the MCP server.
From then on, the tool reaches the MCP server directly. No browser stays open, and nothing about the flow asks you to copy a client secret into your tool. The exact setup for your specific tool lives in your dashboard.
What it works with
Device login works with Clawbot, Hermes agents, and any MCP client SDK. In practice that covers terminal tools, background agents, CI runners, and IDE plugins. Anywhere a client can send an Authorization header with a bearer token, it can talk to the CorpusIQ MCP server. That is the only authentication the server needs.
Your connector access carries over
You authorize each connector once, in the dashboard. After that, any tool you connect with device login reaches every connector you have already authorized, with no re-linking. Sign in once, and your authorized connectors come with you. To review or add connectors, open your connectors in the dashboard.
Related reading
- What is the Model Context Protocol?
- MCP Security: Protecting Your Data in the Context Window
- See all 25+ live CorpusIQ connectors
- Two ways to connect, on the features page
Frequently asked questions
A direct MCP connection lets an external tool talk to the CorpusIQ MCP server on its own, without going through ChatGPT, Claude, or Perplexity. The tool authenticates with device login, receives a bearer token, and calls the same MCP endpoint your assistant uses. It is a second way to connect, alongside the assistant-based path.
Device login is the OAuth 2.0 Device Authorization Grant. Your tool shows a short code, you sign in once in a browser on any device, and the tool receives a secure token. It is the standard way for tools that cannot open their own browser, like a terminal, a CI runner, or an agent loop, to authenticate a real user.
Any MCP client that supports a bearer token. That includes Clawbot, Hermes agents, CI runners, IDE plugins, shell scripts, and any MCP client SDK. If your tool runs outside a normal browser and you do not want to embed a client secret, device login is the path.
No. You authorize each connector once in the dashboard. After that, any tool you connect with device login reaches every connector you have already authorized. Your existing connector access carries over automatically.
Yes. ChatGPT, Claude, and Perplexity ship their own sign-in flow and connect through that. Device login is for external tools that do not have a built-in browser flow. Both paths reach the same MCP server and the same connectors.
Set up your account, authorize each connector once in the dashboard, then connect any external tool directly. Device login confirms it is you. The setup steps for your specific tool live inside your dashboard.