AI Access (MCP)

Manage your links by asking Claude.

The FIFO MCP server connects AI assistants like Claude to your links and analytics using the open Model Context Protocol (MCP). Ask questions in plain English — “which links got the most clicks last week?” — or ask for changes: “tag every fishing link for my outdoor site”, “add a fall sale with code FALL60 through Oct 8”, “disable the TideWe link when the program closes on Nov 1”.

It uses your API key and only offers the tools that key is scoped for, so it is read-only unless you grant write scopes. It cannot delete anything, and every change it makes to a link can be undone from your dashboard. It 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

  • MCP server at mcp.fifo.media
  • Ask about clicks, sources, and trends in plain English
  • Create and edit links, tags, promos, schedules, and categories
  • Bulk changes to up to 100 links, with a preview mode
  • No delete tools; every link change can be undone
  • 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 reading your links, stats, clicks, overview, and categories, and — with write scopes — for creating and updating them. When you connect it, an assistant like Claude works with live data from your FIFO account 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.

Hand off the busywork

Give the key write scopes and the assistant can do the edits too: shorten a URL and file it in the right category, retitle or repoint a link, add or remove tags, put a sale and coupon code on a link with start and end dates, schedule a link to switch off, or rename and deactivate categories.

For changes across many links there is a bulk tool that works on up to 100 at once. It has a preview mode, and FIFO tells assistants to preview first and show you which links would change before applying anything.

Secure by design

The server authenticates with the same fifo_ API keys as the REST API, and only offers the tools your key is scoped for — a read-only key never sees the tools that create or change anything. There are no delete tools at all: to take a link down the assistant disables it, which is reversible and keeps its click history, and permanent deletion requires signing in to the dashboard.

Every change the assistant makes to a link is recorded in that link’s history with the old and new values, and you can undo it from the dashboard. Clients such as Claude Code also ask for your approval before running a tool unless you have chosen to allow it. Keys can be revoked at any time.

Perfect for

  • Asking Claude for a weekly performance summary
  • Tagging and re-filing links conversationally
  • Setting and clearing promos as advertisers send them
  • 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 read your FIFO links and analytics and, when you grant write scopes, create and update links, tags, promos, schedules, and categories. You connect it with an API key and work in plain English.
Which AI tools can connect to it?
Any MCP client that supports remote servers with an API key header, including Claude Code, Cursor, and the Claude API’s MCP connector. The Claude.ai and Claude Desktop custom connectors are not supported yet, because they require OAuth sign-in.
Can an AI assistant delete my links?
No. There are no delete tools. An assistant can disable a link or deactivate a category, both reversible; permanent deletion requires signing in to the dashboard.
What if the assistant makes a change I did not want?
Open the link’s history in the dashboard. Each change shows who made it, including which API key, with the old and new values, and you can revert it. An undo is refused if the same field has changed again since, so revert newer changes first.
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.

Related features