Skip to main content

Model Context Protocol

Run ForestSEO from your AI assistant.

ForestSEO ships a native MCP server, so Claude, ChatGPT, Cursor, or any MCP client can drive your research, content, keyword, ASO, and outreach workflows — grounded in your own project data. One endpoint, one-click connect.

Start freeOpen your dashboard

MCP endpoint

https://forestseo.com/mcp

Curated tools

A curated tool set, not a REST dump.

Every tool is designed for an agent to call: high-value actions, token-efficient responses, and async runs that hand back a job to poll. Access mirrors your plan — an assistant can only use the features your project already includes.

  • Research
    Kick off and read topic research runs at a chosen effort level, then reuse the brief downstream.
    • research_start
    • research_get
    • research_list
    • research_rerun
  • Content
    Draft, advance, and list content — plus generate reusable content plans from a natural-language goal.
    • content_create
    • content_generate
    • content_get
    • content_plan_generate
  • Keyword & ads
    Expand seeds into ideas, pull historical metrics, forecast a paid campaign, and manage persisted keyword sets.
    • keyword_ideas
    • keyword_metrics
    • keyword_forecast
    • keyword_set_expand
  • App Store (ASO)
    Search apps, discover keywords, run competitor gaps and metadata audits, and generate listing copy.
    • aso_search_apps
    • aso_keyword_discovery
    • aso_metadata_audit
    • aso_generate_listing
  • Outreach & link building
    Discover prospects, enrich and verify contacts, enroll into sequences, and read pipeline outcomes.
    • discover_prospects
    • enrich_contact
    • verify_contact
    • enroll

Works with

Bring your own AI assistant.

The ForestSEO MCP server is a standard remote Streamable HTTP endpoint (protocol 2025-06-18), so it works with any MCP-capable client.

  • Claude Code
  • Claude Desktop
  • Codex CLI
  • Cursor
  • VS Code
  • Windsurf
  • ChatGPT
  • Cline
  • Any MCP client

Connecting

Two ways to connect.

One-click OAuth for interactive apps, or an API key for programmatic clients. Both point at the same endpoint.

OAuth 2.1 — one-click

  1. 1Add ForestSEO as a custom connector in your host and paste the MCP endpoint.
  2. 2Approve the ForestSEO consent screen — sign in and pick the project.
  3. 3Choose read and/or write scopes; a project-scoped token is stored for you.
  4. 4The ForestSEO tools appear in your assistant.

API key — Bearer header

  1. 1Best for CLIs and scripts (for example Claude Code).
  2. 2Send your key as an Authorization: Bearer fseo_… header — no project id needed.
  3. 3Project-scoped by construction and supported alongside OAuth — nothing to migrate.

Built for trust

Project-scoped, revocable, honest.

Every connection is bound to a single project and the scopes you approve. An assistant can never read or act across your other projects.

Read our privacy policy
  • OAuth 2.1 with mandatory PKCE (S256); tokens are audience-bound to the MCP resource.
  • Read/write scopes — a read-only token cannot call write tools.
  • Project-scoped by construction: no tool takes a project id; the token decides.
  • Revoke access anytime from the host connector or by rotating the API key.

Connect your first assistant.

Start free, open a project, and connect Claude, ChatGPT, or Cursor in a couple of minutes.

Start freeOpen your dashboard