Connect Your MCP Client

Use this server URL:

• https://notificationcompass.evanschleret.ch/mcp

Codex

Add the remote MCP server to ~/.codex/config.toml:

[mcp_servers.notificationcompass]
enabled = true
url = "https://notificationcompass.evanschleret.ch/mcp"

Codex will expose the list-pages, get-page, prompts, and resources from the server. Keep notificationcompass as the server name so it matches the examples in this documentation.

Generic MCP config

{
  "mcpServers": {
    "notificationcompass": {
      "type": "http",
      "url": "https://notificationcompass.evanschleret.ch/mcp"
    }
  }
}

Most MCP-enabled clients support the same mcpServers JSON shape. Give the server a clear name so it is easy to select when asking about Laravel notification preferences.

Claude Code

Add the remote HTTP server with the Claude Code CLI:

claude mcp add --transport http notificationcompass https://notificationcompass.evanschleret.ch/mcp

Run claude mcp list to verify the server. Use the project scope when the configuration should be shared with a project, or the user scope when it should remain available across projects.

Visual Studio Code

Create .vscode/mcp.json with the VS Code server configuration format:

{
  "servers": {
    "notificationcompass": {
      "type": "http",
      "url": "https://notificationcompass.evanschleret.ch/mcp"
    }
  }
}

Use the MCP: List Servers command to inspect the connection and available tools.

Cursor, Claude Desktop, and other clients

Clients that use the common mcpServers format can use this entry:

{
  "mcpServers": {
    "notificationcompass": {
      "type": "http",
      "url": "https://notificationcompass.evanschleret.ch/mcp"
    }
  }
}

Codex-compatible clients can add the same remote HTTP endpoint through their MCP server settings. Keep the server name stable so prompts and conversations can refer to notificationcompass consistently.

Check the endpoint

curl -sS https://notificationcompass.evanschleret.ch/mcp \
  -X POST \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

If you test a protected preview, verify that the MCP client can reach the host and send both accepted media types.