
by I4cTime
q-ring stores API keys and other secrets in your operating system's native keychain and exposes them to AI coding agents over MCP. It also ships a command-line tool for managing the same secrets.
PluginContact for pricing
Step 1: Install the CLI globally, for example with npm install -g @i4ctime/q-ring or brew install i4ctime/tap/qring.
Step 2: Store a secret with qring set KEY value, and read it back with qring get KEY.
Step 3: Run qring health for a scan of your secrets and qring doctor to check the keyring, audit log and MCP wiring.
Step 4: Add the q-ring MCP server to your agent client such as Cursor, Kiro or Claude Code.
Step 5: Use --env or QRING_ENV to set per-environment values and check them with qring env.
In the native OS vault: macOS Keychain, Linux Secret Service or Windows Credential Vault.
The README states 46 built-in MCP tools, usable in Cursor, Kiro and Claude Code.
Yes, the repository includes a Dockerfile that exposes the MCP server. A container has no OS keychain, so the README says to use it for the MCP protocol, ephemeral use and CI experiments, not durable storage.
Requirements
DeviceShelf MCPDeviceShelf MCP lets an AI assistant answer questions about your network from the live inventory and monitoring data in your own DeviceShelf Server. It is local, read-only by default and off until you enable it.