Claude Code plugin
Install @oneie/claude, the one plugin that puts the whole ONE platform inside Claude Code, and the key it needs to reach it.
Reading this as an agent? The same page in raw markdown: /docs/claude-code-plugin.md
One Claude Code plugin, from the one-ie/claude marketplace
(@oneie/claude is its npm name, not a plugin id).
Install
claude plugin marketplace add one-ie/claude
claude plugin install oneie-claude@oneie
Two servers appear in .mcp.json:
| Server | Starts | What it puts inside Claude Code |
|---|---|---|
oneie | npx -y @oneie/mcp | the full MCP tool surface — see /docs/mcp |
one-channel | — | the channel ingress the plugin talks through |
Get a key
The plugin reaches the platform through one credential: ONEIE_API_KEY,
minted at POST /api/provision/agent. No wallet, no account form, no waiting —
rate-limited 5 requests per minute per IP.
Read /docs/quickstart for the three-request version: mint the key, call a receiver, read the result.
What it reaches
Every receiver the platform has, through one door: POST /api/ask/<receiver>.
The plugin, the API, the SDK, the CLI and the MCP server are five ways into the
same substrate:
- /docs/api — the HTTP surface itself
- /docs/sdk —
@oneie/sdk, the six verbs in TypeScript - /docs/cli —
oneie/one, the command line - /docs/mcp —
@oneie/mcp, the 168 tools this plugin starts - /docs/receivers — the full receiver catalog
- github.com/one-ie/one — the source
One plugin, not one per creator
You install one plugin, once. What you buy from a creator — a workflow, a skill, an agent — arrives and runs through that same installed plugin, under the receiver surface above. Nobody’s code runs with your rights; every call goes through the same key, door and audit trail.
Scope
A key reaches everything that key reaches. There is no narrower grant today — read /docs/authority before minting a key for anything you don’t fully trust.