Hovers MCP (beta)

Hovers exposes a remote Model Context Protocol (MCP) server so AI assistants can perform core SaaS actions: content calendars, articles, site settings, topical analysis status, and integrations.

Status: MCP is in beta. Tools and auth may change; you may hit rough edges. Please report issues to support.

Production MCP URL:

https://www.hovers.ai/api/mcp

(Use your workspace host if it differs.)

What you can do

Credits for calendar and article generation match the Hovers UI. Most tools need a siteId (UUID from list_sites).

Authentication overview

Create an API key

1. Sign in to Hovers
2. Open Account settings → MCP / API keys
3. Create a key and copy it once (hovers_sk_…)

Send it as:

Authorization: Bearer hovers_sk_…

OAuth (ChatGPT and similar)

Hovers advertises:

• /.well-known/oauth-protected-resource
• /.well-known/oauth-authorization-server

On connect you sign in, pick a team workspace that owns your sites (not an empty personal account), then Allow.

Claude Code

1. Create an API key in Hovers (see above)
2. Add Hovers to your MCP config (project .mcp.json or Claude Code MCP settings):

{
  "mcpServers": {
    "hovers": {
      "url": "https://www.hovers.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer hovers_sk_YOUR_KEY"
      }
    }
  }
}

Or via CLI:

claude mcp add --transport http hovers https://www.hovers.ai/api/mcp \
  --header "Authorization: Bearer hovers_sk_YOUR_KEY"

3. Restart / reload Claude Code and ask: “List my Hovers sites.”

Claude Desktop

Claude Desktop’s Custom Connector UI is aimed at OAuth and reaches servers from Anthropic’s cloud. For an API key against Hovers, use local config + mcp-remote.

1. Create an API key in Hovers
2. Edit the Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "hovers": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.hovers.ai/api/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer hovers_sk_YOUR_KEY"
      }
    }
  }
}

3. Fully quit and reopen Claude Desktop
4. Ask Claude to list your Hovers sites (approve tool use when prompted)

Requires Node.js (npx). Putting the Bearer token in env avoids spacing issues in args.

ChatGPT

ChatGPT does not accept a pasted API key for remote MCP. Use OAuth.

1. Enable Developer mode in ChatGPT (Settings → Security / Apps; Team/Enterprise may need an admin)
2. Open Settings → Apps / Plugins / Connectors (or chatgpt.com/plugins)
3. Create an app / connector:
   • Name: Hovers
   • MCP server URL: https://www.hovers.ai/api/mcp
   • Authentication: OAuth
4. Complete the Hovers consent screen — select the team account with sites
5. In a chat, enable the Hovers app and try: “Show all my sites in Hovers”

If you see “no sites,” disconnect and reconnect, choosing the correct team workspace on consent.

Cursor and other clients

Any client that supports Streamable HTTP MCP with a Bearer header can use the same URL and API key:

{
  "mcpServers": {
    "hovers": {
      "url": "https://www.hovers.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer hovers_sk_YOUR_KEY"
      }
    }
  }
}

Exact config keys vary by client (Cursor, Windsurf, Codex, etc.). Prefer HTTP + headers over stdio for Hovers.

Local development

Against a local Next.js app:

http://localhost:3000/api/mcp

Point Claude Code / Desktop mcp-remote at that URL with a key created in your local (or remote-backed) account settings.

Troubleshooting

Security notes

• Treat API keys like passwords; they are shown only once
• Revoke unused keys in Account settings
• OAuth tokens are account-scoped; prefer the least privilege account you need
• Do not commit keys to git

Related

• Integrations overview
• Account settings → MCP / API keys (in-app)