[KongchangAI]
ProductTraffic Creator MCP

Traffic Creator

A SaaS product for managing paid advertising campaigns that provides an API for querying and managing campaigns. An MCP server was built to support integration with AI assistants.

Timeline (last 90 days)

Oct 16

The Traffic Creator team built an MCP server for its paid SaaS product, allowing Claude and ChatGPT users to query and manage advertising campaigns through natural language.

Unverified50%
Oct 16

Traffic Creator's MCP server does not store state (except for a brief key cache); each tool uses the caller's own credentials through a call to the /api/v1/account route and returns JSON, while ownership checks, balance checks, rate limits, read-only scopes and activity logs are all centralized in the API layer.

Unverified50%
Oct 16

Traffic Creator's API layer rate limit is 60 reads and 10 changes per minute.

Unverified50%
Oct 16

Traffic Creator changed its MCP tools from a one-to-one correspondence with API routes to grouping by the way users ask questions, ultimately designing 34 tools covering reading data, rankings, single-campaign analysis, price and cost previews, creation, modification/pausing/resuming, credits and billing, support tickets, and account management.

Unverified50%
Oct 16

Traffic Creator defined five MCP tool annotation combinations: READ (read-only, non-destructive, idempotent), SPEND (mutating, destructive, non-idempotent), CHANGE (mutating, destructive, idempotent), STOP (mutating, non-destructive, idempotent), and MESSAGE (used to create or reply to support tickets).

Unverified50%
Oct 16

Before creating a campaign, Traffic Creator requires the user to show the results of preview_campaign and obtain consent; the preview returns which wallet will pay, how many credits the campaign needs, and whether the balance is sufficient.

Unverified50%
Oct 16

Traffic Creator uses an optimistic locking mechanism, where each campaign carries a settings_version, update_campaign must send back the version number it read, and if the campaign has already been modified the API will reject the change.

Unverified50%
Oct 16

Traffic Creator deliberately excluded MCP tools for deleting and cloning campaigns, buying credits, billing payment details, and profile- or password-related operations; the billing tool can only read purchase records, refunds and subscription information.

Unverified50%
Oct 16

In Traffic Creator's MCP dual-track authentication, Claude and ChatGPT connect via OAuth, and the OAuth flow includes: a 401 response with a resource_metadata pointer, dynamic client registration or a client ID metadata document, mandatory PKCE with only S256 supported, a consent page for choosing full access or read-only, corresponding to four scopes (campaigns:read, campaigns:create, campaigns:update, campaigns:control).

Unverified50%
Oct 16

Traffic Creator's OAuth tokens are opaque and stored only as SHA-256 digests; access tokens are valid for one hour, refresh tokens for thirty days and are rotated after each use; if a rotated refresh token appears again, the entire token family is revoked (per RFC 9700 Section 4.14.2).

Unverified50%

3 more timeline events

All Facts (13)

Unverified

The Traffic Creator team built an MCP server for its paid SaaS product, allowing Claude and ChatGPT users to query and manage advertising campaigns through natural language.

50%
Unverified

Traffic Creator's MCP server does not store state (except for a brief key cache); each tool uses the caller's own credentials through a call to the /api/v1/account route and returns JSON, while ownership checks, balance checks, rate limits, read-only scopes and activity logs are all centralized in the API layer.

50%
Unverified

Traffic Creator's API layer rate limit is 60 reads and 10 changes per minute.

50%
Unverified

Traffic Creator changed its MCP tools from a one-to-one correspondence with API routes to grouping by the way users ask questions, ultimately designing 34 tools covering reading data, rankings, single-campaign analysis, price and cost previews, creation, modification/pausing/resuming, credits and billing, support tickets, and account management.

50%
Unverified

Traffic Creator defined five MCP tool annotation combinations: READ (read-only, non-destructive, idempotent), SPEND (mutating, destructive, non-idempotent), CHANGE (mutating, destructive, idempotent), STOP (mutating, non-destructive, idempotent), and MESSAGE (used to create or reply to support tickets).

50%
Unverified

Before creating a campaign, Traffic Creator requires the user to show the results of preview_campaign and obtain consent; the preview returns which wallet will pay, how many credits the campaign needs, and whether the balance is sufficient.

50%
Unverified

Traffic Creator uses an optimistic locking mechanism, where each campaign carries a settings_version, update_campaign must send back the version number it read, and if the campaign has already been modified the API will reject the change.

50%
Unverified

Traffic Creator deliberately excluded MCP tools for deleting and cloning campaigns, buying credits, billing payment details, and profile- or password-related operations; the billing tool can only read purchase records, refunds and subscription information.

50%
Unverified

In Traffic Creator's MCP dual-track authentication, Claude and ChatGPT connect via OAuth, and the OAuth flow includes: a 401 response with a resource_metadata pointer, dynamic client registration or a client ID metadata document, mandatory PKCE with only S256 supported, a consent page for choosing full access or read-only, corresponding to four scopes (campaigns:read, campaigns:create, campaigns:update, campaigns:control).

50%
Unverified

Traffic Creator's OAuth tokens are opaque and stored only as SHA-256 digests; access tokens are valid for one hour, refresh tokens for thirty days and are rotated after each use; if a rotated refresh token appears again, the entire token family is revoked (per RFC 9700 Section 4.14.2).

50%
Unverified

Changing the password in Traffic Creator or revoking the app on the API & MCP page immediately terminates that access.

50%
Unverified

Traffic Creator records the tool name, result and credential type for every tool call, but does not record parameters or account data; the monitor connects once every five minutes to check the number of tools returned by tools/list and calls one read tool.

50%
Unverified

The core lessons Traffic Creator summarized include: build on top of the public API rather than creating a separate one, write tool descriptions for readers who have never seen the product, treat every tool that spends money as something the user must see before running it, and keep irreversible operations in the UI.

50%

Source Articles