Without remote Caplets
Each agent client needs its own provider tokens, OAuth login, and local MCP wiring.
- Repeat auth per client
- Duplicate secrets
- Debug setup in every agent
Agent tools without the wall
Caplets wraps MCP servers, APIs, and commands as focused capabilities. Your agent picks a source, searches inside it, inspects the schema, then calls the tool.
npm install -g caplets caplets setup codex Direct MCP aggregation exposed 106 flat tools. Caplets started with 3 capability cards and an 87.9% smaller initial payload.
Remote Caplets server
Run Caplets as a small HTTP service. Provider tokens and OAuth state stay with that server; Codex, OpenCode, Pi, Claude Code, and any MCP client connect to the same capability surface.
Each agent client needs its own provider tokens, OAuth login, and local MCP wiring.
One server holds provider auth; every agent connects to the same capability surface.
CAPLETS_SERVER_URL=https://caplets.example.com/caplets
CAPLETS_SERVER_PASSWORD=...
caplets serve --transport http CAPLETS_MODE=remote
CAPLETS_SERVER_URL=https://caplets.example.com/caplets
CAPLETS_SERVER_PASSWORD=...
opencode Step 1
Install the Claude Code plugin from the Caplets marketplace entry; the bundled MCP config runs caplets serve.
claude plugin marketplace add spiritledsoftware/caplets
claude plugin install caplets@caplets {
"mcpServers": {
"caplets": {
"command": "caplets",
"args": ["serve"]
}
}
} After adding the marketplace, install caplets from Codex plugins; the bundled MCP config runs caplets serve.
codex plugin marketplace add spiritledsoftware/caplets {
"mcpServers": {
"caplets": {
"command": "caplets",
"args": ["serve"]
}
}
} Use the native @caplets/opencode plugin; it reads Caplets config and does not start the MCP server.
npm install -g caplets {
"plugin": ["@caplets/opencode"]
} The extension reads existing Caplets config; this Pi settings snippet registers the package.
npm install -g caplets
pi install npm:@caplets/pi {
"packages": ["npm:@caplets/pi"]
} Any MCP-compatible client can launch Caplets over stdio.
npm install -g caplets {
"command": "caplets",
"args": ["serve"]
} Step 2
Pick the integration above, then try one premade Caplet. Your agent sees one focused capability before it can search or call downstream tools.
A huge hosted MCP surface for repositories, issues, pull requests, branches, commits, and reviews.
Use it when the value is avoiding a giant GitHub tool wall.
githubinspectsearch_toolsget_toolcall_tool If setup fails, check Node 22+, plugin installation, and GH_TOKEN.
export GH_TOKEN=github_pat_... caplets install spiritledsoftware/caplets github codex "try using the github caplet" Hosted code search for finding examples, references, and implementation patterns across repositories.
Use it when the agent should search code first, then inspect only the matching operations.
sourcegraphinspectsearch_toolsget_toolcall_tool If setup fails, check Node 22+, plugin installation, and Sourcegraph OAuth login.
caplets install spiritledsoftware/caplets sourcegraph caplets auth login sourcegraph codex "try using the sourcegraph caplet" A small explicit HTTP API for vulnerability lookups by package, purl, commit, or batch query.
Use it when Caplets should bound a sharp task without exposing arbitrary HTTP calls.
osvinspectsearch_toolsget_toolcall_tool OSV is public and does not need auth; check Node 22+ and plugin installation.
caplets install spiritledsoftware/caplets osv codex "try using the osv caplet"