"Ingress" matching MCP servers:

Enables a single MCP connector to route requests to independent local Chat and Codex runtimes, supporting workspace operations, process control, reviews, browser-backed tasks, and Codex workflows through one public ingress.

Enables zero-execution AST auditing of Python ingress code to catch circular imports, broken contracts, and version-gated PEP violations before any bytecode runs.

Bridge between IITC and MCP agents, enabling AI assistants to interact with Ingress Intel: view map, count portals, track players, and communicate via COMM without manual input.

Exposes an OAuth-gated MCP endpoint that lets web-based AI clients work directly on a local machine through 38 governed tools covering files, shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, localhost services, clipboard, notifications, ports, and Postman control. Local tools can connect straight to the loopback address for offline, low-latency use, while remote clients reach the same machine over an optional public ingress.

Exposes an OAuth-gated MCP endpoint with 38 governed tools that let web-based AI chat clients read and edit local files, run whitelisted shell commands, search, use Git and SQLite, fetch localhost/intranet APIs, automate Chromium and DevTools, and manage background tasks, ports, clipboard, notifications, and Postman. Local IDEs can connect directly over 127.0.0.1, while remote clients reach the same machine through a secure public ingress.

Exposes a governed suite of 38 tools over one OAuth-gated MCP endpoint, letting web-based AI clients such as Claude, ChatGPT, and Grok read and edit files, run whitelisted shell commands, search content, use Git, inspect SQLite databases and localhost APIs, automate browsers, manage background tasks, and control Postman. It runs locally with a tailnet or public ingress so browser-based chats can act on your own machine without granting unrestricted shell access.