Yes. AgentKey is a master key — one platform that unlocks external capabilities for your agent. By design, we have no access to your local files, your credentials, or your agent's conversations. The only data AgentKey collects is anonymous usage telemetry — which agent you installed into, your skill version, and upgrade outcomes — never your queries or responses. See "How do I opt out of telemetry?" below.

Native web access in Claude and ChatGPT has limited platform coverage. It often can't reach Twitter, on-chain data, etc. AgentKey fills those gaps.

Just top up. No auto-renewal, no hidden charges.

There are two pieces and they update differently:

• MCP server: the real server is hosted at https://api.agentkey.app/v1/mcp, so it's always up to date — no local upgrade step. The @agentkey/cli package (run as npx -y @agentkey/cli --auth-login) only writes the remote-HTTP MCP config into each AI client and never has to be re-run unless you want to rotate your key.

• Skill files (SKILL.md + helpers): how this updates depends on your client.

Claude Code

Updates are automatic. On the first call of a session the skill runs a silent version check; if a new release is available it prompts you to upgrade and (with your consent) runs npx skills update -g agentkey.

Claude Desktop, Cursor, and other clients without an inline Bash tool

The skill cannot run the inline check itself, but starting in v1.4.0 the MCP server publishes the latest skill version via a dedicated metadata tool (agentkey_skill_meta). Your agent calls it once per session, compares against this skill's own version, and prompts you to upgrade with the exact command for your client. See protocol/skill-meta-v1.md for the protocol details.

One-time bootstrap on Desktop: if you're stuck on a pre-1.4.0 skill in Claude Desktop, the metadata tool exists but your skill rule doesn't know how to read it. Bring yourself current once with:

# Replace <UUID1>/<UUID2> with the actual session folder under skills-plugin
# (usually there's just one; pick the one that contains skills/agentkey/SKILL.md)
DESKTOP_BASE="$HOME/Library/Application Support/Claude/local-agent-mode-sessions/skills-plugin"
LATEST_REPO_ZIP=$(mktemp -d)/agentkey.tar.gz
curl -fsSL https://github.com/chainbase-labs/agentkey/archive/refs/heads/main.tar.gz -o "$LATEST_REPO_ZIP"
tar -xzf "$LATEST_REPO_ZIP" -C "$(dirname "$LATEST_REPO_ZIP")"
find "$DESKTOP_BASE" -type d -path "*/skills/agentkey" 2>/dev/null | while read -r dst; do
  cp -R "$(dirname "$LATEST_REPO_ZIP")"/agentkey-main/skills/agentkey/. "$dst/"
done
# Then fully quit and restart Claude Desktop.

After this one bootstrap, future versions will be discovered automatically via the metadata tool.

Force manual update (any client)

# Refresh the skill content
npx skills update agentkey

# Pin a specific version
npx skills add chainbase-labs/agentkey@v1.0.0

Note: npx skills update writes to ~/.agents/skills/agentkey and ~/.claude/skills/agentkey, which is where Claude Code reads from. Claude Desktop reads from its own sandbox path and is not touched by npx skills update — use the Desktop bootstrap command above for Desktop.

Re-run npx -y @agentkey/cli --auth-login only when you want to rotate your API key.

One command, cleans every agent and config file.

macOS / Linux

curl -fsSL https://agentkey.app/uninstall.sh | bash

Windows (PowerShell)

irm https://agentkey.app/uninstall.ps1 | iex

Removes the skill from every agent, strips the agentkey MCP entry + API key from all MCP client configs, and clears caches/logs. Pass --keep-marketplace (bash) / -KeepMarketplace (PowerShell) to retain the Claude Code plugin marketplace entry.

Prefer manual two-step?

# 1. Remove the skill from every agent
npx skills remove chainbase-labs/agentkey

# 2. Delete the "agentkey" entry under mcpServers in each MCP client config:
#    - Claude Code:     ~/.claude.json
#    - Claude Desktop:  ~/Library/Application Support/Claude/claude_desktop_config.json  (macOS)
#                       %APPDATA%\Claude\claude_desktop_config.json                      (Windows)
#    - Cursor:          ~/.cursor/mcp.json

The one-command uninstaller additionally cleans npm/npx caches, legacy shell rc entries, CLAUDE.md sections, and MCP stdio logs — use that if you want a fully clean slate.

AgentKey sends anonymous usage telemetry (which agent you use, skill version, upgrade outcomes — never queries or responses). Three ways to opt out, any of them works:

# Persistent opt-out (recommended)
touch ~/.config/agentkey/telemetry-disabled

# One-shot env override (CI / single session)
AGENTKEY_TELEMETRY=0 <your command>

# At install time
curl -fsSL https://agentkey.app/install.sh | bash -s -- --no-telemetry

To re-enable, delete ~/.config/agentkey/telemetry-disabled.

Inside your agent, try /agentkey status — it diagnoses your MCP config, version, and connectivity.

Available slash commands:

Still stuck? See the "Where do I get help" item below.

The installer auto-detects which AI agents you have on this machine (by probing well-known config dirs and binaries from the vercel-labs/skills supported-agents list) and pre-selects them — no multi-select prompt. Override with the flags below.

Installer flags:

# Non-interactive (CI / unattended): install to every detected agent, no prompts
curl -fsSL https://agentkey.app/install.sh | bash -s -- --yes

# See which agents the installer would auto-select on this host (and exit)
curl -fsSL https://agentkey.app/install.sh | bash -s -- --list-agents

# Only install the skill for specific agents (overrides auto-detection)
curl -fsSL https://agentkey.app/install.sh | bash -s -- --only claude-code,cursor

# Skip our agent detection; let `skills` CLI install for every agent it finds
curl -fsSL https://agentkey.app/install.sh | bash -s -- --all-agents

# Only the skill, or only the MCP auth
curl -fsSL https://agentkey.app/install.sh | bash -s -- --skip-mcp
curl -fsSL https://agentkey.app/install.sh | bash -s -- --skip-skill

PowerShell equivalents: -Yes, -ListAgents, -Only, -AllAgents, -SkipMcp, -SkipSkill.

Manual two-step install (if you'd rather run the two underlying commands yourself, or the one-line installer can't reach your machine):

# 1. Install the skill into every detected agent
npx skills add chainbase-labs/agentkey

# 2. Authenticate and register the MCP server
npx -y @agentkey/cli --auth-login

Headless / SSH / Docker? The auth step always tries to open a browser and prints the URL — so on a machine without a usable display, just copy the printed URL to any device with a browser to finish auth. Prefer typing the key manually? npx -y @agentkey/cli --setup opens an interactive wizard instead.

MCP auto-configuration covers Claude Code, Claude Desktop, and Cursor. For Codex / OpenCode / Gemini CLI / Hermes / Manus (or Linux Claude Desktop), the skill still installs automatically — but you'll need to paste this MCP snippet into the agent's own config (path varies per agent):

{
  "mcpServers": {
    "agentkey": {
      "type": "http",
      "url": "https://api.agentkey.app/v1/mcp",
      "headers": { "Authorization": "Bearer ak_..." }
    }
  }
}

Then restart the agent. The skill's first-run activation will also walk you through this.

Install from a local checkout:

git clone https://github.com/chainbase-labs/agentkey.git
cd agentkey

# 1. Install your working tree into every detected agent
npx skills add .

# 2. Register the MCP server (if you haven't already)
npx -y @agentkey/cli --auth-login

npx skills add . accepts a local path (or a file:// URL) — run it again after each edit to skills/agentkey/SKILL.md. The MCP step only needs to run once per machine.

Iterating on the MCP server itself? The server lives at AgentKey-Server/ (Go) and exposes the MCP endpoint at /v1/mcp. Run a local server (make run) and point your MCP config at http://localhost:8081/v1/mcp to test changes end-to-end.

Claude Code plugin mode — add the repo as a local marketplace:

claude plugin marketplace add /absolute/path/to/agentkey
claude plugin install agentkey

Reload with claude plugin update agentkey after edits. Use the skills-CLI path for day-to-day edits; the plugin path only for testing Claude Code plugin internals (e.g. MCP env-var wiring through CLAUDE_PLUGIN_OPTION_*).

Repo layout:

agentkey/
├── .claude-plugin/plugin.json   # Claude Code plugin manifest
├── .mcp.json                    # Used when installed as a plugin
├── skills/agentkey/
│   ├── SKILL.md                 # Decision tree + routing rules
│   ├── scripts/                 # check-mcp / check-update helpers
│   └── version.txt              # Managed by release-please
└── scripts/
    ├── install.sh               # One-command installer (mac/linux)
    ├── install.ps1              # Windows PowerShell installer
    ├── uninstall.sh             # One-command uninstaller (mac/linux)
    └── uninstall.ps1            # Windows PowerShell uninstaller

Release a new version (maintainers): releases are cut automatically by release-please. Merging a PR with a feat: or fix: title opens a Release PR that bumps skills/agentkey/version.txt, plugin.json, and CHANGELOG.md. Merging the Release PR creates the tag + GitHub Release + uploads the agentkey.skill asset.

Early access. There are rough edges and we appreciate your patience. Feature requests and bug reports are welcome via GitHub Issues or Telegram (see below).

• Telegram: t.me/AgentKey_Official — general questions, support, feature requests
• Bug reports: GitHub Issues
• Release announcements: ⭐ star this repo to get notified