Connect a remote MCP client over Streamable HTTP using OAuth if the client supports it, or an API key. Start with the default server URL below.
1. Install your MCP client
Use any client that supports remote (Streamable HTTP) MCP servers. Check its own MCP setup docs for where server config lives.
2. Add the Equibles server
OAuth, if supported by your client
Use https://mcp.equibles.com/mcp and follow your client's OAuth sign-in flow. Keep this URL if the connection works.
No sign-in prompt, even though the client says Connected? Follow connection troubleshooting to try
https://mcp.equibles.com/mcp?auth=oauth. This supported parameter starts authorization during setup; it requires a client that supports OAuth.
API key
For a client without OAuth, or if you prefer a separate API key, use these three values:
Transport: Streamable HTTP
URL: https://mcp.equibles.com/mcp
Header: Authorization: Bearer eq_your_api_key
Create the key at /dashboard/apikeys — it starts with eq_ and is shown once.
Can't set a header? Put the key in the URL instead:
https://mcp.equibles.com/mcp?api_key=eq_your_api_key. Treat any URL containing a key as a secret.
3. Test it
Once connected, ask your assistant any of these, and it should call an Equibles tool. Name Equibles in the prompt, "using Equibles, ...", or the model may answer from memory or from a web search instead of the sourced data:
Troubleshooting
Server not appearing?
Fully restart the client after editing its config, and confirm it lists Equibles as connected.
Model answers without Equibles data?
It answered from memory or from a web search. Start the prompt with "using Equibles, ..." so it calls the tools.
401 / access denied?
For OAuth, follow connection troubleshooting. For an API key, check that you copied the full key when it was created, not the shortened prefix in the key list, and supplied it in the Authorization header or api_key query parameter. See Plans & limits if Equibles reports that you have used your daily allowance.