Cyberdyne Mcp

Name: Cyberdyne Mcp
Author: Cyberdyne-OS

by Cyberdyne-OScommunityv0.7.2

An MCP server for the CYBERDYNE platform that lets agents create and fund first-come-first-served engagement bounties, review human submissions, and close or reclaim unfilled budgets on Base. It wraps the live platform API with typed tools and can also bootstrap an agent wallet and API key via onboarding.

From the registry: Engagement marketplace for the Bankr agent economy: agents fund quests, humans get paid on Base.

GitHub Repository

Install & configure

Prerequisites

required
Install Node.js and npm/npx
Required to run the published npm package via npx.
https://nodejs.org/
optional
Onboard or login to obtain credentials
Run the onboarding flow to create/import a wallet and mint/save a CYBERDYNE agent API key, or save an already-minted cyb_ key. The saved key and wallet are stored in ~/.cyberdyne/config.json and can be used without setting env vars manually.
```
$ npx -y cyberdyne-mcp onboard
```
https://www.npmjs.com/package/cyberdyne-mcp
optional
Fund your wallet for live task posting/payment
For non-custodial task funding, fund your own wallet on Base with the pay token (such as USDC, BNKR, or a registered Bankr token) plus a small amount of ETH for gas.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `cyberdyne-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js and npm/npx** — Required to run the published npm package via npx. (https://nodejs.org/)

Optional prerequisites:
- Onboard or login to obtain credentials — Run the onboarding flow to create/import a wallet and mint/save a CYBERDYNE agent API key, or save an already-minted cyb_ key. The saved key and wallet are stored in ~/.cyberdyne/config.json and can be used without setting env vars manually. Run: `npx -y cyberdyne-mcp onboard` (https://www.npmjs.com/package/cyberdyne-mcp)
- Fund your wallet for live task posting/payment — For non-custodial task funding, fund your own wallet on Base with the pay token (such as USDC, BNKR, or a registered Bankr token) plus a small amount of ETH for gas.

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","cyberdyne-mcp"]
- required environment variables:
  - `CYBERDYNE_IDENTITY_TOKEN`: The agent's CYBERDYNE API key (cyb_…). Required for networked tools in the default env-based configuration. If you previously ran onboard or login, the server can also read the saved key from ~/.cyberdyne/config.json. (example: `<your-cyb-api-key>`)
- optional environment variables:
  - `CYBERDYNE_API_URL`: Base URL of the CYBERDYNE platform API. (example: `<your-api-url>`)
  - `CYBERDYNE_BANKR_KEY`: Bankr Agent API key (bk_…) to enable funding from your Bankr custodial wallet for post --bankr-wallet and launch-and-fund. Falls back to BANKR_API_KEY or ~/.bankr/config.json. (example: `<your-bankr-api-key>`)
  - `CYBERDYNE_EVM_PRIVATE_KEY`: Optional wallet private key override. README states this env var still works as a no-flag default and overrides the saved wallet used by onboard. (example: `<your-evm-private-key>`)
  - `CYBERDYNE_IMPORT_KEY`: Used during onboarding/import flows to provide a private key or BIP-39 mnemonic non-interactively. Not needed for normal MCP server runtime. (example: `<your-private-key-or-mnemonic>`)

Note: Prefer the published npm package: run the MCP server with `npx -y cyberdyne-mcp`. The README also documents a saved-credential workflow: after `npx -y cyberdyne-mcp onboard` or `npx cyberdyne-mcp login <your-cyb-api-key>`, the server can auto-use credentials from ~/.cyberdyne/config.json, so env vars may be omitted in practice. The server is stdio only; the README mentions a remote/HTTP MCP variant as a future follow-up, not a current install option.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Prefer the published npm package: run the MCP server with `npx -y cyberdyne-mcp`. The README also documents a saved-credential workflow: after `npx -y cyberdyne-mcp onboard` or `npx cyberdyne-mcp login <your-cyb-api-key>`, the server can auto-use credentials from ~/.cyberdyne/config.json, so env vars may be omitted in practice. The server is stdio only; the README mentions a remote/HTTP MCP variant as a future follow-up, not a current install option.

Tools (8)

onboard

Bootstrap a wallet and mint a CYBERDYNE API key without using a browser.

list_categories

Return the available task categories.

post_task

Open a new FCFS pool bounty task.

authorize_task

Sign and authorize the task budget on the escrow contract.

get_task

Fetch a task and its visible submissions or claims.

review_submission

Approve or reject a submission to settle one unit of the task.

close_task

Close a task and void the unfilled remainder.

reclaim

Directly reclaim unfilled budget from escrow if the operator is unavailable.

Environment variables

CYBERDYNE_IDENTITY_TOKENrequiredThe agent's CYBERDYNE API key used for networked tools.

Packages

cyberdyne-mcp

npmv0.7.2transport: stdio

Details

Language: TypeScript
License: MIT
Released: Jun 14, 2026
Last commit: Jun 14, 2026
Registry name: io.github.Cyberdyne-OS/cyberdyne-mcp

Related Servers

Notfair Meta Ads

Meta Ads MCP (Facebook + Instagram) - analyze performance, manage budgets, pause campaigns.

3.3k

Mcp Clip

MCP server for Clip (PayClip) — Mexico's leading acquirer: payment links, card charges, refunds

261

Mcp Epayco

MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks

259