AI Access (MCP)
Let Claude answer questions about your links.
The FIFO MCP server connects AI assistants like Claude directly to your links and analytics using the open Model Context Protocol (MCP). Instead of clicking through dashboards, you ask questions in plain English — "which links got the most clicks last week?" — and the assistant queries your data and answers.
It is scoped to your API key — read-only unless you grant write scopes — and works with Claude Code, Cursor, the Claude API’s MCP connector, and other MCP-compatible clients. AI access is available on the Maker Pro plan.
What you get
- Read-only MCP server at mcp.fifo.media
- Works with Claude and other MCP-compatible AI tools
- Uses the same API keys and scopes as the REST API
- Available on the Maker Pro plan
What is the Model Context Protocol (MCP)?
MCP is an open standard for connecting AI assistants to external tools and data. An MCP server exposes a set of tools an assistant can call; FIFO’s server exposes tools for your links, stats, clicks, overview, and categories. When you connect it, an assistant like Claude can pull live data from your FIFO account to answer your questions accurately instead of guessing.
Because it is an open protocol, the same FIFO connection works across many AI clients — not just one vendor’s app.
Ask your analytics anything
With the MCP server connected, you can ask things like "summarize my top traffic sources this month", "which category is growing fastest?", or "list my links with no clicks in the last 30 days" and get an answer grounded in your real data. It turns analysis that used to take several dashboard views into a single question.
You can connect it in Claude Code or Cursor with a single command, or attach it to the Claude API using the MCP connector to build your own AI workflows.
Secure by design
The server authenticates with the same fifo_ API keys as the REST API, and only advertises the tools your key is scoped for — a read-only key never sees the tools that create or change anything. There is no delete tool at all: taking a link out of circulation disables it, which is reversible and keeps its click history. Keys can be revoked at any time.
Perfect for
- Asking Claude for a weekly performance summary
- Exploring analytics conversationally instead of via dashboards
- Building AI workflows on top of your link data
- Letting an assistant surface underperforming links
Frequently asked questions
- What is the FIFO MCP server?
- A Model Context Protocol server at mcp.fifo.media that lets AI assistants like Claude query your FIFO links and analytics, and create links when you grant write scopes. You connect it with an API key and work in plain English.
- Which AI tools can connect to it?
- Any MCP-compatible client works, including Claude Code, Cursor, and the Claude API’s MCP connector. You can also connect other assistants that support remote MCP servers.
- Is the MCP server safe to use?
- Yes. It authenticates with the same API keys and scopes as the REST API, so an assistant can only do what the key you gave it allows — read-only unless you grant write scopes. There is no delete tool, and every write in Claude Code asks your permission before it runs. Keys can be revoked at any time.
- Which plan includes AI access via MCP?
- AI access via the MCP server is available on the Maker Pro plan, the same plan that includes REST API access.