Quantum-inspired keyring for AI coding agents with superposition, entanglement, and tunneling.
Most knowledge and memory work still happens through a UI a human drives. Q MCP server moves it into the conversation instead. Quantum-inspired keyring for AI coding agents with superposition, entanglement, and tunneling.
Stop pasting API keys into plain-text .env files or wrestling with clunky secret managers. q-ring securely anchors your credentials to your OS's native vault (macOS Keychain, Linux Secret Service, Windows Credential Vault) and supercharges them with mechanics from quantum physics.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 9 tools. What each one is for:
get_secret — Read a secret value (collapses superposition, audits the read)list_secrets — List keys + metadata in scope (values never exposed); filter by tag, expiry, globset_secret — Create or overwrite a single secret with optional TTL, per-env state, tags, rotation formatdelete_secret — Permanently remove a secret value (not undoable from q-ring)has_secret — Boolean existence check that respects decay (no audit read)export_secrets — Render multiple secrets as .env or JSON for one-off export (skips approval-protected keys without a grant)import_dotenv — Parse .env text and bulk-store every key/value pair (accepts raw content only — never reads files)check_project — Compare .q-ring.json manifest against the keyring for missing/expired/stale keysenv_generate — Render a complete .env body from the project manifest, with warnings for gapsConfiguration is passed through the environment: OPENAI_API_KEY, SESSION_TOKEN, CERT_KEY, OPENAI_KEY, STRIPE_KEY, REDIS_URL, SOME_KEY, AWS_ACCESS_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Q's toolset — get_secret, list_secrets, set_secret and 6 more — is a fair guide to whether it matches your workflow. It is maintained by I4cTime; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Q's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_secret | Read a secret value (collapses superposition, audits the read) |
| list_secrets | List keys + metadata in scope (values never exposed); filter by tag, expiry, glob |
| set_secret | Create or overwrite a single secret with optional TTL, per-env state, tags, rotation format |
| delete_secret | Permanently remove a secret value (not undoable from q-ring) |
| has_secret | Boolean existence check that respects decay (no audit read) |
| export_secrets | Render multiple secrets as .env or JSON for one-off export (skips approval-protected keys without a grant) |
| import_dotenv | Parse .env text and bulk-store every key/value pair (accepts raw content only — never reads files) |
| check_project | Compare .q-ring.json manifest against the keyring for missing/expired/stale keys |
| env_generate | Render a complete .env body from the project manifest, with warnings for gaps |
{
"mcpServers": {
"q-ring": {
"command": "npx",
"args": ["-y", "@i4ctime/q-ring"],
"env": {
"OPENAI_API_KEY": "your-value",
"SESSION_TOKEN": "your-value",
"CERT_KEY": "your-value",
"OPENAI_KEY": "your-value",
"STRIPE_KEY": "your-value",
"REDIS_URL": "your-value",
"SOME_KEY": "your-value",
"AWS_ACCESS_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| SESSION_TOKEN | Credential the server authenticates with. | Yes |
| CERT_KEY | Credential the server authenticates with. | Yes |
| OPENAI_KEY | Credential the server authenticates with. | Yes |
| STRIPE_KEY | Credential the server authenticates with. | Yes |
| REDIS_URL | Endpoint or connection string the server talks to. | Yes |
| SOME_KEY | Credential the server authenticates with. | Yes |
| AWS_ACCESS_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.