Skip to content

VS Code MisarSEO MCP Server get_audit_internal_links

How to: VS Code MisarSEO MCP Server get_audit_internal_links

client:VS Code transport:streamable-http tool:get_audit_internal_links

Add MisarSEO MCP Server to VS Code

  1. 01

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

{
  "servers": {
    "misarseo-mcp": {
      "type": "http",
      "url": "https://api.misar.io/seo/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

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

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

MisarSEO MCP Server will not start until these are set, so get_audit_internal_links never becomes available.

  • MISARSEO_API_KEY
  • MISARSEO_BASE_URL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 17 October 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.