Endpoint
MCP endpoint:https://mcp.indices.io
The MCP server requires API key authentication. Your requests must contain a header Authorization: Bearer <your_api_key>. Instructions below on how to include this easily with agents like Claude.
Usage
First, generate an API key in the dashboard. We recommend using a separate API key for each agent. Then add the indices MCP server to your AI agent or application. Use the Streaming HTTP transport, with the URLhttps://mcp.indices.io, and ensure requests will contain the Authorization header with your API key.
Adding to Claude
Setup
With Claude, add the following MCP server to your configuration:mcp-remote library proxies the requests to our MCP server, adding the Authorization header to all requests to authenticate them. mcp-remote isn’t always necessary if your MCP client supports adding headers to outbound requests, as Claude Code does for example.
If you’re using Claude Code, you can either first add the MCP server to Claude Desktop first and then run claude mcp add-from-claude-desktop, or you can run claude mcp add indices-mcp https://mcp.indices.io --transport http --header "Authorization: Bearer <paste your API key here>". This leads to a config (in ~/.claude.json) like:
mcp-remote was not needed here. Refer to the MCP documentation for further guidance on adding MCP servers to typical MCP clients, or the documentation for your specific MCP client.
OpenAI’s Responses API supports passing through Authorization headers as well.
Interaction
Now, you can chat with Claude and ask it to perform tasks using the MCP server. In the following example, we already have a task set up to retrieve AI events in London from Luma. We can ask the agentCan you get a list of Luma events happening today (via indices.io MCP)?
The agent responds, informed by live data from Luma, retrieved via the indices platform!
Image of response in Claude Code
Image of response in Claude Code
