Connect Equibles to Grok on the web as a custom MCP connector. Use the OAuth setup below to sign in without an API key, or choose the separate API-key alternative.
1. Open Grok's connectors
Sign in at grok.com/connectors, or open Plugins in Grok's sidebar and select the Connectors tab. Click New Connector, then Custom.
For a Grok Business or Enterprise workspace, a team administrator must first make the connector available through the xAI console.
2. Add Equibles
In the Custom Connector form, enter Equibles under Name and this address under Server URL:
https://mcp.equibles.com/mcp?auth=oauth
Keep ?auth=oauth in the URL: it asks Equibles to require authorization from the first connection request. It contains no secret and needs no API key. The plain URL allows public tool discovery, which can leave Grok showing Connected without starting sign-in. Grok can then fail on data requests because account authorization never completed. See connection troubleshooting for how public discovery and OAuth differ.
Click Add Connector and follow any sign-in prompt. If the connector already exists with the plain URL, disconnect it in Grok and add it again using the full URL above.
A successful data request is the check that account authorization works.
3. Make a test request and sign in
Start a new conversation and ask:
Using Equibles, show NVIDIA's top institutional holders and cite the source and reporting period.
If Grok shows Connect Equibles, click Continue.
When Grok opens Equibles, sign in and review the requested permissions. If you are already signed into Equibles, you may only see the permission screen. Approve access and the permission to stay connected without re-approving, if requested, then return to Grok. That permission lets Grok renew access after the short-lived token expires.
If Continue returns to the chat without opening sign-in and the request still fails, check that the saved URL includes ?auth=oauth. If it does, contact support with the approximate time and timezone of the attempt. The Connected label alone does not prove authorization succeeded.
A successful test calls Equibles and returns sourced data. An answer from Grok's memory or web search alone does not verify the connection.
4. API-key alternative
Create a separate key for Grok in your Equibles API keys. Copy the full key when it is shown, not the shortened prefix displayed later in the key list.
In Grok's Plugins → Connectors, open the Equibles connector and click Disconnect. Add a new custom connector using Equibles as the name and this URL, replacing the placeholder with your key:
https://mcp.equibles.com/mcp?api_key=eq_your_api_key
Click Add Connector, then repeat the test request in a new conversation. This authenticates with your key instead of the browser sign-in flow.
Treat the full URL as a secret: do not share it in screenshots, prompts, or support tickets. You can revoke the separate Grok key from Equibles without affecting your other integrations.
Browse the tool reference for available data and rate limits for your plan's allowance.
Troubleshooting
Grok keeps asking you to authorize again?
Remove the Equibles connector from Grok and add it again using https://mcp.equibles.com/mcp?auth=oauth. Sign in and approve the stay-connected permission if it appears. Re-adding lets Grok discover the current authorization settings.
If the permission is missing or the connection expires again, contact support with the approximate time and timezone of the failed attempt. Do not include API keys or tokens.
The connector is missing from your workspace?
Check that you are signed in to the intended Grok account or workspace. Business and Enterprise users may need their team administrator to add the connector first. See Grok's connector documentation for current availability.
Equibles reports a daily limit or unavailable market data?
Follow the message returned by Equibles. Reconnecting does not reset your daily limit or change your plan's market-data access.