TrafficBud SEO

io.trafficbudPublished by trafficbud.ioOfficial publisherv1.0.0Updated Oct 25, 2026

Real SEO data for AI assistants: page audits, Keyword Planner volumes, Search Console history.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

TrafficBud SEO gives an AI assistant real SEO data: page audits, Keyword Planner search volumes and Search Console history, via a hosted remote endpoint.

What you can do
Run page audits to check on-page SEO issues for a URL or site page. Look up keyword search volumes and related data from Keyword Planner. Retrieve Search Console history to review past search performance. All of this is exposed to the assistant through a hosted remote MCP endpoint rather than a local package.
When to use it
Useful when you want an assistant to ground SEO advice in actual audit results, keyword volume figures or Search Console performance data instead of general knowledge, for example while planning content or reviewing a page's optimization.
Requirements
A remote MCP connection to the TrafficBud hosted endpoint over streamable HTTP. Authentication is required via OAuth and an Authorization header carrying a Bearer API key obtained from the TrafficBud dashboard; a free account is available and no card is required.
Before you install
The server requires an API key sent in the Authorization header, so treat it as a secret and avoid exposing it in logs or shared transcripts. Queries about your sites and keywords are sent to a third-party service, TrafficBud.

Installation

In SourceWeft

  1. Open TrafficBud SEO in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.trafficbud%2Ftrafficbud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "trafficbud-seo": {
      "type": "http",
      "url": "https://www.trafficbud.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.