Koskamo

OpenWatch MCP

The OpenWatch MCP server provides AI assistants with direct access to verified, geolocated security incidents across Nigeria. It allows users to query data on kidnappings, banditry, and other threats by state, type, or date, retrieve daily intelligence briefs, and access case timelines, enabling risk assessment and location intelligence for logistics, humanitarian work, and security planning.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OpenWatch MCP logo, by OpenWatchOAuth sign-inEndpoint checked 2026-10-18Operated by OpenWatch
MCP endpoint (Streamable HTTP)
https://api.openwatch.ng/mcp/connect
Vendor documentation

What you can do with it

  • Query security incidents by state, type, or date range
  • Retrieve daily intelligence briefs for Nigeria
  • Get risk tiers and top threats for specific states
  • Access published case timelines with developments

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http openwatch-mcp https://api.openwatch.ng/mcp/connect

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add openwatch-mcp --url https://api.openwatch.ng/mcp/connect

Cursor

Merge this server into .cursor/mcp.json in your project, then enable openwatch-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "openwatch-mcp": {
      "url": "https://api.openwatch.ng/mcp/connect"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "openwatch-mcp": {
      "type": "streamableHttp",
      "url": "https://api.openwatch.ng/mcp/connect",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start openwatch-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "openwatch-mcp": {
      "type": "http",
      "url": "https://api.openwatch.ng/mcp/connect"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http openwatch-mcp https://api.openwatch.ng/mcp/connect

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "openwatch-mcp": {
      "url": "https://api.openwatch.ng/mcp/connect"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "openwatch-mcp": {
      "serverUrl": "https://api.openwatch.ng/mcp/connect"
    }
  }
}

Do you run OpenWatch MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing