CorpusIQ is now live in the ChatGPT app store.
Find CorpusIQ in ChatGPT
Connector directory
Files & Storage
Advertising & Analytics
CRM
Email Marketing
Commerce
Finance
CorpusIQ is now live in the ChatGPT app store.
Find CorpusIQ in ChatGPTConnector directory
For Claude users with business systems
One MCP connection gives Claude read-only access to every business system you approve. No local servers, no config files, no credential spread across machines.
Read-only OAuth · 30-day free trial · Cancel anytime
Each of these reaches live systems and returns the records behind the answer.
The first server is easy. The tenth is the problem.
Wiring Claude to your business one server at a time means a separate process, a separate credential, and a separate failure mode for every system. Five tools is a config file. Twenty is an operations problem nobody owns.
Each locally configured server holds its own token. Rotating them, revoking one cleanly, or answering which machine currently holds access to the books becomes guesswork.
A server running on a laptop serves that laptop. Colleagues on Claude web, another device, or a different assistant see none of it, so the setup has to be repeated per person and per machine.
When the CRM and the accounting system disagree about a number, a pile of independent servers has no view about which one is authoritative. Whichever answers first wins, which is not the same as being right.
What changes when the connection is consolidated and remote.
A single MCP endpoint fronts every system you authorize, so Claude gets one connector to manage instead of one per tool. 40+ connectors and 650+ tools are reachable through it.
Each system is authorized separately through its own login screen, and each can be revoked on its own. Adding a tool does not widen access to anything else, and removing one leaves the rest untouched.
Claude sees named tools with typed arguments, not a pile of undifferentiated API surface. That is what makes it pick the right call for a vague question instead of guessing at parameters.
Responses carry the records behind them. When two systems could answer the same question, the answer says which one it used, so a disagreement is visible rather than silently resolved.
Six steps, all inside Claude. Nothing is installed on your machine.
Go to the connector settings in Claude. The connection is configured in Claude itself, so nothing is installed on your machine and nothing runs locally.
Choose to add a custom connector. This is Claude's built-in path for remote MCP servers, which is what CorpusIQ is.
Use https://mcp2.corpusiq.io/mcp. The transport is streamable HTTP, so any MCP client that supports remote servers can use the same endpoint.
Sign in to CorpusIQ when prompted. Claude holds the resulting credential, so there is no key to paste into a config file or keep in sync by hand.
Approve each tool you want reachable through its own official login screen. Read-only scopes, granted per system, revocable per system.
The tools appear in Claude immediately. Ask in plain English and the answer comes back with the records it drew on.
Add a tool by authorizing it, not by editing a config and restarting a process. The MCP connection in Claude does not change when your connected systems do.
The server is remote, so the same connection is there on web, desktop, and other devices. There is nothing installed to fall out of date on one machine.
The endpoint is a standard remote MCP server, so the same authorized systems are reachable from ChatGPT, Perplexity, Slack, and any MCP client you point at it. Authorize once, not once per assistant.
The scope is read-only everywhere. Claude can read the books and cannot post to them, can read a thread and cannot reply to it. A mistaken tool call returns a wrong answer, never a changed record.
Disconnect a single tool without disturbing the others, or disconnect the whole connector at once. Access is a list you can see and edit, not something spread across machines.
Each query reads and discards. There is no index to build, no sync to fall behind, and no second copy of your company data to secure.
One connection does not mean broad access. Every system is authorized and revoked on its own.
Every connector authenticates through the provider's own OAuth flow and requests read scopes only. CorpusIQ never sees a password and cannot write to a connected system.
Queries read at the moment they run and retain nothing. Disconnecting a tool leaves no residue, because there was never a copy to remove.
Customer data is not used to train models. SOC 2 aligned, CASA Tier 2 certified by DEKRA, with the certificate published.
Each connector lists the exact scopes it requests before you approve it. Read the full security posture.
https://mcp2.corpusiq.io/mcp. It is a remote MCP server over streamable HTTP, so it works with Claude's custom connector flow and with any other MCP client that supports remote servers.
No. The server is remote, so there is no local process, no config file, and nothing to keep running. That is also why the same connection works across your devices instead of only the machine you set it up on.
No. Every connector is authorized with read-only scopes. Claude can read your books, orders, threads, and documents, and cannot modify any of them. Everything it returns links back to the source record so a person takes the action.
One connection instead of many, one credential path instead of one per server, and access you can revoke per system from a single place. It also arbitrates when two connected systems could answer the same question, which independent servers cannot do.
Yes. The systems you authorize are reachable from ChatGPT and Perplexity, inside Slack, and from any MCP client pointed at the same endpoint. Microsoft Teams is coming soon. You authorize a tool once rather than once per assistant.
Adding the connector in Claude takes about a minute. Each business system is another two minutes or so through its own login screen. 30-day free trial, no credit card.
The protocol behind the connection, explained without the marketing.
Endpoint, transport, headers, and the device-login flow for other MCP clients.
What CorpusIQ reads on Claude's behalf, connector by connector.
The same connected systems, reached from ChatGPT instead of Claude.
What the connection looks like against a single system, the accounting file.
The cross-system reporting view, for questions that span several tools at once.
30-day free trial. Read-only OAuth. Cancel anytime.