Skip to content
mcp/harbor
Grok

mcp-authprobe for Grok

io.github.enigmacker/mcp-authprobe

Active OAuth tests for remote MCP servers you own: tokens, PKCE, redirect_uri, audience, CSRF.

client:Grok transport:stdio runtime:npm

Install mcp-authprobe in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen. 

{
  "mcpServers": {
    "mcp-authprobe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-authprobe"
      ],
      "env": {
        "MCP_AUTHPROBE_SECRET_FILE": "<MCP_AUTHPROBE_SECRET_FILE>",
        "MCP_AUTHPROBE_SECRET": "<MCP_AUTHPROBE_SECRET>",
        "MCP_AUTHPROBE_CREDENTIALS_FILE": "<MCP_AUTHPROBE_CREDENTIALS_FILE>",
        "MCP_AUTHPROBE_ALLOW_PRIVATE": "<MCP_AUTHPROBE_ALLOW_PRIVATE>",
        "MCP_AUTHPROBE_LAB_ORIGINS": "<MCP_AUTHPROBE_LAB_ORIGINS>",
        "MCP_AUTHPROBE_TIMEOUT_MS": "<MCP_AUTHPROBE_TIMEOUT_MS>",
        "MCP_AUTHPROBE_BEARER_FILE": "<MCP_AUTHPROBE_BEARER_FILE>",
        "MCP_AUTHPROBE_BEARER_TARGET": "<MCP_AUTHPROBE_BEARER_TARGET>",
        "MCP_AUTHPROBE_BEARER_HEADER": "<MCP_AUTHPROBE_BEARER_HEADER>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

mcp-authprobe in other clients

mcp-authprobe MCP server