TamRank

com.tamrankPublished by tamrank.comOfficial publisherv1.0.0Updated Oct 30, 2026

WordPress SEO for your AI assistant: change plans, approval in chat, rollback. Needs TamRank PRO.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an AI assistant plan and apply WordPress SEO changes, with in-chat approval and rollback.

What you can do
  • Plan SEO changes for a WordPress site from the assistant.
  • Review and approve proposed changes inside the chat before they are applied.
  • Roll back changes that were made.
When to use it
Useful if you run a WordPress site and want an assistant to propose, approve and undo SEO changes without leaving the conversation.
Requirements
A remote endpoint at mcp.tamrank.com using streamable HTTP, with OAuth sign-in required. A TamRank PRO subscription is needed. No environment variables or headers are declared.
Before you install
The server can change a live WordPress site's SEO settings, so review each plan before approving it. It requires OAuth access to your TamRank account and a paid PRO plan.

Installation

In SourceWeft

  1. Open TamRank 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/com.tamrank%2Ftamrank/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": {
    "tamrank": {
      "type": "http",
      "url": "https://mcp.tamrank.com/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.0LatestOct 30, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.