# techtenstein-seo [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/sathvic-kollu/techtenstein-seo-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/techtenstein-seo

## Description
On-page SEO audit for any URL. Titles, meta, headings, links, score, and fix recommendations.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "techtenstein-seo": {
    "command": "uvx",
    "args": ["techtenstein-seo-mcp"],
    "env": {
      "TECHTENSTEIN_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `TECHTENSTEIN_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What techtenstein-seo MCP server does

The techtenstein-seo MCP server gives Claude, Cline, Cursor, and other configured MCP clients access to the Techtenstein SEO Audit API. It evaluates publicly specified URLs for common on-page SEO information and returns structured results that an agent can summarize or compare.

The single-page audit reports the target URL, an SEO score, title content and length, whether the title is marked optimal, meta description details, heading counts, word count, image totals and alt-text coverage, internal and external link counts, and a list of recommendations. The returned data is suitable for prompts such as asking an agent to identify the most important fixes.

## How it works

The server runs as a local command through `uvx` and communicates with the MCP client using the configured server entry. When a client invokes `seo_audit`, the server sends the requested URL to the Techtenstein SEO Audit API and returns the API response as tool data.

`seo_batch_audit` accepts a list of URLs and supports batches of up to 20. This allows an agent to request several audits in one operation, then produce a comparison such as a table of SEO scores or differences between competitor pages.

## Setup and configuration

The techtenstein-seo MCP server requires a Techtenstein API key supplied through the `TECHTENSTEIN_API_KEY` environment variable. The README directs users to obtain a key from the Techtenstein API site. It documents a free tier of 100 audits per day and paid plans beginning at $5 per month for 5,000 audits.

For Claude Desktop, add a `techtenstein-seo` entry to the client configuration, set the command to `uvx`, and pass `techtenstein-seo-mcp` as its argument. Put the API key in the entry's environment settings, then restart the client. Cline can use the same setup through Claude Desktop configuration. Cursor uses a corresponding entry in `~/.cursor/mcp.json`.

## Tools and capabilities

- `seo_audit(url)`: runs an on-page SEO audit for one URL.
- `seo_batch_audit(urls)`: audits up to 20 URLs in one request.
- Reports title and meta description content and lengths.
- Counts H1, H2, and H3 headings, words, images, and links.
- Reports image alt-text coverage and internal versus external links.
- Returns an SEO score and fix recommendations.

## Limitations and notes

The techtenstein-seo MCP server depends on the external Techtenstein SEO Audit API and a valid API key. API usage is subject to the account's audit allowance. The documented response covers the listed on-page fields; it does not claim to provide rankings, backlink analysis, keyword research, or broader technical SEO crawling.

The repository identifies the project as MIT licensed. Documentation and issue support are linked from the Techtenstein API site and the project's GitHub repository.

_Full upstream README: https://allmcps.com/mcp/techtenstein-seo/readme_