Keitaro TDS API MCP Plugin MCP Server

Keitaro TDS API MCP Plugin MCP server exists for a simple reason — assistants are far more useful when they can act on Keitaro TDS API MCP Plugin directly instead of describing what you should do. Keitaro API MCP Server.

What you get

1. Clone the repository bash git clone <repository-url> cd mcp-keitaro-tds

MCP server for integration with Keitaro TDS API, providing tools to work with campaigns, streams, offers, and other Keitaro entities.

What the assistant can call

Once Keitaro TDS API MCP Plugin is connected, these are the calls the assistant has available:

• Campaigns — The Campaigns tool exposed by this server
• Offers — The Offers tool exposed by this server
• Reports — The Reports tool exposed by this server
• Domains — The Domains tool exposed by this server

Configuration and credentials

You will need 2 environment variables: KEITARO_API_URL, KEITARO_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Keitaro TDS API MCP Plugin's toolset — Campaigns, Offers, Reports and 1 more — is a fair guide to whether it matches your workflow. It is maintained by GodzillaDancer; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the keitaro tds api mcp plugin mcp server does with a few real requests.