# BlogSEO [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/BlogSEO-io/blogseo-agent-plugin  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/blogseo-2

## Description
SEO that executes: keywords, calendar, articles written, scored and published to your CMS, backlinks

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "blogseo": {
    "url": "https://mcp.blogseo.io/mcp"
  }
}
```

## Documentation

## What BlogSEO does

BlogSEO MCP server gives an AI assistant access to SEO workflows for websites connected to a BlogSEO account. Its tools cover keyword research, ranking analysis, content scheduling, article editing, SEO checks, publishing, CMS synchronization, and backlink monitoring.

The server exposes 60 tools grouped by task. Keyword tools can list tracked terms with search volume, difficulty, and Search Console positions; research terms from seed keywords; refresh metrics; expand topic clusters; identify possible keyword cannibalization; and compare rankings across two periods. Calendar tools read scheduled work, create article briefs, change dates, edit pending entries, remove pending entries, and suggest headlines.

Article tools list and read content, change headlines, slugs, meta descriptions, cover images, and alt text, apply AI edits, and publish or sync articles to a connected CMS. SEO tools score an article or supplied content, compare it with competitors, suggest AI improvements, and measure keyword density on a page. Backlink tools show links placed through the BlogSEO exchange, Domain Rating, and a domain’s backlink profile.

## How it works

BlogSEO MCP server uses Streamable HTTP at `https://mcp.blogseo.io/mcp`. Authentication uses OAuth 2.1. On the first connection, the user signs in through BlogSEO’s consent page and selects which administered websites the assistant may access. Websites where the user is only a member are not exposed. A connection can be revoked from BlogSEO under Settings > Security.

Read-only operations do not consume credits. Operations such as keyword research, AI editing, and competitor benchmarking report their credit cost before execution and require explicit confirmation. Destructive actions are marked so the client can request confirmation. Tokens, payment information, and integration credentials are not returned by the tools.

## Setup and configuration

A BlogSEO account with at least one website is required. For VS Code, add an HTTP server entry to `.vscode/mcp.json` or the user MCP configuration:

```json
{
  "servers": {
    "blogseo": {
      "type": "http",
      "url": "https://mcp.blogseo.io/mcp"
    }
  }
}
```

The server can also be added with `code --add-mcp`. Start it from the MCP view, complete the browser sign-in, choose the allowed websites, and approve access. Cursor supports installation through its marketplace or Cursor Directory. Claude Code can install the packaged plugin with `claude plugin marketplace add BlogSEO-io/blogseo-agent-plugin` followed by `claude plugin install blogseo@blogseo`. Claude, ChatGPT, and other clients can add the URL as a remote MCP server or custom connector.

## Tools and capabilities

The repository also packages an Agent Plugin with skills for SEO workflows, connecting a hosted blog or custom webhook, and replacing article images while setting alt text. Client manifests are included for Cursor and Claude Code. With multiple websites, the assistant can ask which one to use, or the prompt can identify the website explicitly.

Typical tasks include finding pages ranking between positions 5 and 15, comparing recent and previous search traffic, scheduling an article around a target keyword, scoring an article and applying fixes, and locating articles that compete for the same keyword.

## Limitations and notes

The BlogSEO MCP server does not use an API key; access depends on OAuth approval and the websites selected during consent. The available website scope is limited to sites the user administers. Credit-consuming operations do not run until their cost is confirmed. Publishing and synchronization depend on a connected CMS or configured integration, while custom sites can use a hosted blog or webhook setup supported by BlogSEO.

_Full upstream README: https://allmcps.com/mcp/blogseo-2/readme_