MAJR AI SEO

io.github.majrdotappPublished by GitHub account majrdotappv1.7.3Updated Oct 24, 2026

Audit a page for search and AI answer engines; generate robots.txt, sitemap, head, llms.txt.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Audits a web page for search and AI answer engines and generates robots.txt, sitemap, head and llms.txt files.

What you can do
This remote MCP server lets an assistant audit a page for search and AI answer engine visibility. It can generate supporting artifacts such as robots.txt, a sitemap, head markup and an llms.txt file. The manifest does not list individual tool names, so the exact tool surface is not documented here.
When to use it
Use it when you want an assistant to check how a page is likely to be read by search engines and AI answer engines, or to produce standard SEO and AI-discovery files like robots.txt, sitemap, head tags and llms.txt.
Requirements
A remote MCP endpoint at over streamable HTTP. Authentication is required: a bearer token supplied in the Authorization header as Bearer . No packages or environment variables are declared. Network access to the endpoint is needed.
Before you install
The server is a remote endpoint that requires a bearer token in the Authorization header; treat that key as a secret and avoid exposing it in shared logs or client configs. The audit and generated files may be sent to the provider's service, so consider whether page content is sensitive before use.

Installation

In SourceWeft

  1. Open MAJR AI SEO in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.github.majrdotapp%2Fseo/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.

{
  "mcpServers": {
    "majr-ai-seo": {
      "type": "http",
      "url": "https://seo.majr.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.7.3LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.