Skip to main content

​
Installation

Stobo MCP is distributed as a Python package and runs via uvx for zero-config installation. No OAuth, no complex setup — just add the config and go.

​
Prerequisites

Before installing Stobo MCP, ensure you have:
1

MCP-compatible AI client

You need an AI editor that supports the Model Context Protocol:
  • Claude Desktop
  • Claude Code (CLI)
  • Cursor
  • VS Code (with Copilot)
  • Windsurf
  • Any other MCP-compatible client
2

uv package manager

Install uv to use the uvx runtime:
pip install uv
Verify installation:
uvx --version
3

Stobo API key (optional)

Only needed for premium tools like generate_llms_txt, extract_tone, and rewrite_article.Free tools (audit_site, audit_article, fix generators) work without an API key.Get your key at trystobo.com:
  1. Sign up or log in
  2. Go to Settings > API Keys
  3. Create a new key and copy it

​
Install the package

Stobo MCP is installed automatically when you configure your AI editor. No manual pip install needed — uvx handles everything.
The package is pulled from PyPI as stobo-mcp. Version 0.4.3 is the latest stable release.
If you want to install it manually for testing: 
pip install stobo-mcp

​
Configure your AI editor

Add Stobo MCP to your editor’s MCP server configuration. Choose your editor below:
1

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
  "mcpServers": {
    "stobo": {
      "command": "uvx",
      "args": ["--native-tls", "stobo-mcp"],
      "env": {
        "STOBO_API_KEY": "your-api-key"
      }
    }
  }
}
Restart Claude Desktop after saving the config file.
2

Claude Code (CLI)

Add the server via the CLI:
claude mcp add stobo -- uvx --native-tls stobo-mcp
If using premium tools, export your API key in your shell:
export STOBO_API_KEY="your-api-key"
Add to ~/.bashrc, ~/.zshrc, or your shell config to persist across sessions.
3

Cursor

Open Settings > MCP Servers > Add Server, then paste:
{
  "stobo": {
    "command": "uvx",
    "args": ["--native-tls", "stobo-mcp"],
    "env": {
      "STOBO_API_KEY": "your-api-key"
    }
  }
}
Restart Cursor after saving the configuration.
4

VS Code (Copilot)

Add to .vscode/mcp.json in your project root:
{
  "servers": {
    "stobo": {
      "command": "uvx",
      "args": ["--native-tls", "stobo-mcp"],
      "env": {
        "STOBO_API_KEY": "your-api-key"
      }
    }
  }
}
Reload VS Code after creating the config file.
5

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:
{
  "mcpServers": {
    "stobo": {
      "command": "uvx",
      "args": ["--native-tls", "stobo-mcp"],
      "env": {
        "STOBO_API_KEY": "your-api-key"
      }
    }
  }
}
Restart Windsurf after saving the configuration.

​
Environment variables

Stobo MCP uses two environment variables:
VariableRequiredDefaultDescription
STOBO_API_KEYNo(empty)Your API key from trystobo.com. Free tools work without it.
STOBO_BASE_URLNohttps://api.trystobo.comAPI endpoint. Only change this if told to by Stobo support.
Do not change STOBO_BASE_URL unless instructed by Stobo support. The default endpoint is correct for all users.

​
Verify installation

Test that Stobo MCP is working correctly:
1

Manual test

Run the server manually to verify it starts without errors:
uvx --native-tls stobo-mcp
You should see the MCP server start. Press Ctrl+C to stop.
2

Test in your AI editor

Open your AI editor and ask:
"Check if Stobo is working"
The AI should use the check_connection tool and confirm the API is reachable.
3

Run a free audit

Test with a real audit (no API key needed):
"Audit https://example.com"
You should get a full SEO + AEO audit report with scores and recommendations.

​
Troubleshooting

​
Tool not showing up in your editor

1

Save and restart

Ensure you saved the config file and restarted your editor completely.
2

Verify uvx installation

Run uvx --version in your terminal to confirm uv is installed correctly.
3

Test manually

Run uvx --native-tls stobo-mcp — it should start without errors. If it fails, check your uv installation.
4

Check config syntax

Validate your JSON config file. Even a missing comma can break MCP server loading.

​
”No API key configured”

Free tools work without a key. If you’re calling a premium tool:
1

Get an API key

Sign up at trystobo.com and go to Settings > API Keys.
2

Add to config

Add STOBO_API_KEY to the env block in your editor config.
3

Restart your editor

Environment variables are loaded when the MCP server starts. Restart to pick up the new key.

​
”Your API key is invalid or expired”

Log in at trystobo.com, generate a new key, and update your config file.

​
”You’ve run out of credits”

Top up at trystobo.com. Free tools still work without credits.

​
”Rate limit reached”

Wait a moment and try again. Rate limits reset quickly. Normal conversational use stays well within limits.

​
Connection issues

Ask your AI assistant to run check_connection. Common fixes:
  • Check your internet connection
  • Make sure STOBO_BASE_URL is not set (it defaults to the correct value)
  • Try again in a few minutes if the API is temporarily down

​
Next steps

Quick start

Run your first audit and generate fixes in minutes