
Content Optimizer
io.github.sharozdawaPublished by GitHub account sharozdawav1.0.0Updated Oct 24, 2026
SERP-based content scoring and optimization with 7 SEO categories.
Overview
A local MCP server that scores and optimizes web content against search results, with SEO recommendations across seven categories.
- What you can do
- Score content against a target keyword across seven SEO categories with a 0-100 breakdown per category and prioritized improvement recommendations, plus readability checks (Flesch-Kincaid, grade level, sentence stats, reading time). Analyze SERP data for top-ranking pages, including word counts, headings and topic benchmarks, and find topics competitors cover that your content is missing. Review heading structure and get suggested keyword-rich heading improvements.
- When to use it
- Useful when drafting or revising SEO articles and you want an assistant to benchmark a draft against top-ranking pages, spot missing topics, and get concrete scoring and readability feedback without a paid subscription tool.
- Requirements
- Runs locally over stdio via npx from the npm package content-optimizer-mcp; Node.js 18+ and npm 9+ are needed. No authentication, environment variables or headers are declared. SERP analysis implies network access to fetch search results.
Installation
In SourceWeft
- Open Content Optimizer in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
SERP-based content scoring, entity analysis, and actionable SEO recommendations.
Score your content against top-ranking pages. Know exactly what to improve.
[npm] [stars] [license] [PRs Welcome] [Content Optimizer MCP server]
Why Content Optimizer?
Paid content optimization tools charge $89-$170/month for SERP-based scoring. Content Optimizer gives you the same analysis — for free, self-hosted, and extensible.
:sparkles: Features
:dart: Content Scoring — Score content 0-100 across 7 SEO categories with per-category breakdowns
:mag: SERP Analysis — Analyze top-ranking pages for word count, headings, and topic benchmarks
:abc: Readability Analysis — Flesch-Kincaid scoring, grade level, sentence length, reading time
:bookmark_tabs: Heading Optimization — Detect hierarchy issues, suggest keyword-rich heading structure
:brain: Entity Coverage — Find topics competitors cover that you're missing
:clipboard: Actionable Recommendations — Prioritized improvements ranked by impact
:robot: MCP Server — Use with Claude Desktop, Cursor, or any MCP-compatible AI tool
:chart_with_upwards_trend: Scoring Categories
:camera: Screenshots
Screenshots coming soon — the web UI is under active development.
:rocket: Self-Hosting Setup
Prerequisites
- Node.js 18+
- npm 9+
Installation
Development
Open http://localhost:3000.
Production Build
:electric_plug: MCP Server
The MCP server lets you use Content Optimizer directly inside AI coding tools like Claude Desktop and Cursor.
Install via npx
No setup required — just add the config:
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Cursor
Add to .cursor/mcp.json in your project:
Build from Source
Then use node ./mcp-server/dist/index.js as the command in your MCP config.
MCP Tools
:open_book: More Open Source SEO Tools
:handshake: Contributing
Contributions are welcome! See CONTRIBUTING.md for guidelines.
:page_facing_up: License
MIT — see LICENSE for details.
Built by Sharoz Dawa
[GitHub]
Source: README.md at commit 96a551a
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts