Requirements
- An Exploratory account
- An MCP client that supports Streamable HTTP (a way to send MCP over HTTP) and OAuth (sign in through the browser and approve access)
- You do not need a client ID or an API key. The client registers itself.
Steps
Register and sign in
See the client’s own documentation for where and how.-
Register this server URL in the client’s MCP server settings.
- Follow the client’s prompts to sign in to Exploratory in the browser.
- Approve the access.
Check that it is connected
-
In a new chat of the client, send this.
Connect with an API key
If your client cannot open a browser, use an API key. Create the key in Account Settings > API Keys, put it in an environment variable, and have the client send it from there as Authorization: Bearer <your key>. If you type the key on a command line or write it in a settings file as it is, it stays in your shell history or in that file. See Connect with an API key for what a key can read.Troubleshooting
A request without a valid token gets HTTP 401. Sign in again with your client’s own steps.- Data and permissions - The authorization mechanism and the metadata URLs.
- Troubleshooting - Fixes by symptom for the Server MCP as a whole.
