INDIVIDUAL MCP TOOL

get_introduction_path

Get the public directory URL and what an introduction to a firm requires.

grcmigrate.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://grcmigrate.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_introduction_path and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.grcmigrate-directory]
url = "https://grcmigrate.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "grcmigrate-directory": {
      "type": "http",
      "url": "https://grcmigrate.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: grcmigrate-directory
Remote MCP URL: https://grcmigrate.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "grcmigrate-directory": {
      "url": "https://grcmigrate.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "grcmigrate-directory": {
      "type": "http",
      "url": "https://grcmigrate.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "grcmigrate-directory",
  "transport": "streamable-http",
  "url": "https://grcmigrate.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

search_firms — Search the GRC Migrate directory of SOC 2 audit and compliance-readiness firms (facts compiled from public sources).
get_firm — Get one firm's public directory record by slug.
list_resources — List GRC Migrate guides, question pages, and blog posts available to read (title, description, url, type).
get_resource — Get one guide, question page, or blog post by slug — its title, description, and content (blog body markdown, or the FAQ question/answer pairs for guides and question pages).