semantic-pen

Semantic Pen MCP Server exposes an automated AI article generation and SEO content workflow that integrates with your MCP ecosystem. It provides a set of tools to manage AI-driven article projects, generate SEO-optimized content, and retrieve full article HTML ready for publishing. Use the provided MCP entry to authenticate requests with your Semantic Pen API key and access project lists, article content, and creation capabilities directly from the MCP interface you prefer (Cursor, Claude Code, Windsurf, etc.). The available tools include get_projects to list all article projects, get_project_articles to fetch all articles within a project, search_projects to filter projects by name, create_article to generate new AI articles with topic, keyword, length, language, and tone, and get_article to retrieve a complete article by ID. The server handles API verification and content generation, returning structured results you can further process in your workflows.

Prerequisites:

• Node.js 18 or newer installed on your system
• Access to install or run npm/npx commands
• A Semantic Pen API key (SEMANTIC_PEN_API_KEY) for authenticating API requests

Manual installation steps:

1. Install the MCP server package globally (optional if using npx):

npm install -g semantic-pen-mcp-server

2. Run or configure via MCP with the npm package name:

# Using the MCP config directly (example for one-off run)
semantic-pen-mcp-server --api-key your-api-key-here

3. If you’re adding to an MCP config file, use the following example (adjust key names as needed):

{
  "command": "semantic-pen-mcp-server",
  "env": {
    "SEMANTIC_PEN_API_KEY": "your-api-key-here"
  }
}

4. For Cursor, Claude Code, Windsurf, or other MCP integrations, reference the MCP config snippet below and substitute your API key. The recommended quick setup is via npx as shown in the Quick Setup section of the README.

{
  "command": "npx",
  "args": ["-y", "semantic-pen-mcp-server@latest"],
  "env": {
    "SEMANTIC_PEN_API_KEY": "your-api-key-here"
  }
}

Tips and considerations:

• Ensure your SEMANTIC_PEN_API_KEY is kept secret and is set in the env section of your MCP config.
• If you encounter API key verification errors, double-check that the key is active and has sufficient credits.
• The server requires Node.js 18+; using older runtimes may prevent startup.
• When upgrading to a newer semantic-pen-mcp-server release, pin the version in your MCP config (e.g., semantic-pen-mcp-server@latest) to avoid breaking changes.
• If you’re using a one-click install method, replace the API key placeholder with your actual key in the resulting config as described in the documentation.
• The server’s responses include article content in HTML format, suitable for direct publishing workflows.
• If you run into CORS or network limitations, confirm outbound access to Semantic Pen API endpoints from your hosting environment.