Skip to content

Cursor AgentSEO agentseo_content_programmatic_template

How to: Cursor AgentSEO agentseo_content_programmatic_template

client:Cursor transport:streamable-http tool:agentseo_content_programmatic_template

Add AgentSEO to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "agentseo-mcp": {
      "url": "https://www.agentseo.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something agentseo_content_programmatic_template does. Cursor lists the server's tools on connect and calls agentseo_content_programmatic_template itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that AgentSEO's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

AgentSEO will not start until these are set, so agentseo_content_programmatic_template never becomes available.

  • AGENTSEO_API_KEY
  • AGENTSEO_API_URL
  • AGENTSEO_PROJECT_ID
  • AGENTSEO_WORKFLOW_ID

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.