Any MCP-capable client can reach the Equibles server over Streamable HTTP with an API key — here's the generic recipe.
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
Point the client at the Equibles server with 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?
Your key is missing or wrong — re-copy it from /dashboard/apikeys into the Authorization header (or the api_key query parameter). If you're over your daily limit, see Rate limits.