SERP.technology

technology.serpPublished by serp.technologyOfficial publisherv1.0.0Updated Nov 11, 2026

Read workspaces, sites, keywords, articles and analytics from the SERP.technology SEO platform.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant read workspaces, sites, keywords, articles and analytics from the SERP.technology SEO platform.

What you can do
  • Read workspaces and sites configured in the SERP.technology SEO platform
  • Look up keywords and articles tracked in those workspaces
  • Retrieve analytics data from the platform
  • No individual tools are documented in the supplied material, so exact operations are not confirmed
When to use it
Useful when you want an assistant to pull SEO workspace, keyword, article and analytics information from SERP.technology into a conversation without leaving the chat.
Requirements
A remote MCP connection to the hosted endpoint at app.serp.technology; OAuth authentication is required, so a SERP.technology account with access to the relevant workspaces is needed. No packages, environment variables or headers are declared.
Before you install
Access is granted through OAuth to your SERP.technology account, so review the scopes requested at sign-in. The description mentions only reading, but no tool list is provided to confirm that nothing is written or changed; verify before relying on it. SEO and analytics data is sent to the assistant's model provider.

Installation

In SourceWeft

  1. Open SERP.technology 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/technology.serp%2Fserp/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": {
    "serp-technology": {
      "type": "http",
      "url": "https://app.serp.technology/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.0LatestNov 11, 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.

Other Serp integrations