"LoopBack" matching MCP servers:

Lets AI agents and developers inspect and query local MySQL, Redis, and MongoDB instances over STDIO or authenticated loopback HTTP, with read-only defaults and allowlisted non-production writes that require explicit opt-in. Production connections always reject writes, and database-enforced read-only accounts are recommended.

Local-first Gmail MCP server using PKCE + loopback OAuth flow that stores refresh tokens in the OS keychain, enabling secure read/write Gmail access via MCP tools without tokens leaving the device.

Enables MCP clients that can only send a fixed Authorization header to reach OAuth 2.1-protected MCP servers, by running a loopback proxy that handles RFC 9728 discovery, PKCE login, and silent token refresh so no pasted JWT is ever needed. The client keeps a stable local token while the rotating OAuth credentials stay in the gateway's state file.

Enables a remote MCP client to access narrowly scoped local filesystem resources and process capabilities through a loopback-only bridge. Supports guarded file reads, searches, and mutations, authenticated transport, and private reachability via OpenAI Secure MCP Tunnel.

Enables permission-scoped MCP clients to interact with DeepSeek Harness Desktop over a local loopback HTTP bridge, including checking status, listing models/workspaces/sessions, reading bounded session history, and creating, sending, waiting for, or canceling chats. Access is restricted per bearer token and only exposes the tools and sessions granted to that token.

Enables AI assistants to invoke generated NostrHost operations over MCP, with read operations executed immediately and write operations gated on approval. Client authentication uses NIP-98, results are redacted, and the HTTP transport binds to loopback only.