# SEOmade MCP server: install guide for AI agents

This guide is written for AI coding agents (Claude Code, Cursor, Cline, Codex, Windsurf, VS Code) so they can add the SEOmade MCP server without help. Follow the steps in order.

## What the server does

`https://seomade.app/api/mcp` is a remote Streamable HTTP MCP server. It lets an agent:

- search a catalog of 1,000+ launch and SaaS directories with Ahrefs Domain Rating, link type and pricing
- read and save the product profile that directory forms ask for
- get the next directories to submit to, the exact field values for each form, and record the result
- run a site audit (SEO, AI visibility, agent readiness) and read the fix list
- run single-purpose SEO checks on any public URL (indexability, redirects, llms.txt, internal links and more)

## Before you start

The server needs an API key. Keys start with `sm_live_`.

1. Ask the user for their SEOmade API key. Do not guess or invent one.
2. If they do not have one, send them to https://seomade.app/developers to create it, and wait.
3. Store the key where the client keeps secrets. Never commit it to a repository.

## Install

Replace `sm_live_YOUR_KEY` with the user's key.

### Claude Code

```bash
claude mcp add --transport http seomade https://seomade.app/api/mcp \
  --header "Authorization: Bearer sm_live_YOUR_KEY"
```

### Cursor, Cline, Windsurf, Claude Desktop (`mcpServers` JSON)

```json
{
  "mcpServers": {
    "seomade": {
      "url": "https://seomade.app/api/mcp",
      "headers": { "Authorization": "Bearer sm_live_YOUR_KEY" }
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "seomade": {
      "type": "http",
      "url": "https://seomade.app/api/mcp",
      "headers": { "Authorization": "Bearer sm_live_YOUR_KEY" }
    }
  }
}
```

### Codex (`~/.codex/config.toml`)

```toml
[mcp_servers.seomade]
url = "https://seomade.app/api/mcp"
http_headers = { "Authorization" = "Bearer sm_live_YOUR_KEY" }
```

### Clients that only support stdio

Use the bridge in the `mcp/` folder of the SEOmade repository: run `node server.mjs` with `SEOMADE_API_KEY` set in the environment.

## Verify

Call `catalog_meta`. A working install returns catalog counts and the plan quota for the key.

- `401 missing_api_key`: the Authorization header is not being sent. Check the config.
- `401 invalid_api_key`: the key is wrong or revoked. Ask the user for a new one.
- `429`: the daily quota or rate limit is used up. The quota resets at midnight UTC.

## Next

Read https://seomade.app/mcp/SKILL.md for the recommended order of tool calls and the rules for submitting to directories.
