BeanCloud Agent API

BeanCloud as agent infrastructure

One Developer API Key, one OpenAPI contract, one official MCP package. Wire site discovery, utilities, and lookups into your agent workflows.

Official MCP server

@beancloud/mcp-server speaks stdio for Cursor and peers—Tools plus an OpenAPI resource, following mainstream MCP practice.

OpenAPI contract

Machine-readable /openapi.yaml shared by REST and MCP so agents call a stable surface.

Open authentication

bc_live_ developer keys with optional HMAC on writes—isolated from browser JWT and internal bot keys.

Curated tools

Directory search, utility/game catalogs, IP/Whois lookup, favourites—high-value reads first, then writes.

Wire it into Cursor

Three steps to make BeanCloud available to your side agent.

  1. Sign in and create a bc_live_ key under API Keys (shown once).
  2. Paste the JSON below into Cursor MCP settings and fill in your key.
  3. Restart MCP, then ask the agent to call nav_search_sites, tools_list_items, and more.
{
  "mcpServers": {
    "beancloud": {
      "command": "npx",
      "args": ["-y", "@beancloud/mcp-server"],
      "env": {
        "BEANCLOUD_API_KEY": "bc_live_YOUR_KEY",
        "BEANCLOUD_BASE_URL": "https://coffeecloud.info",
        "BEANCLOUD_LOCALE": "zh-CN"
      }
    }
  }
}

Local checkout (package not on npm yet)

Run npm i && npm run build in packages/mcp-server, then point args at your absolute dist/index.js path.

{
  "mcpServers": {
    "beancloud": {
      "command": "node",
      "args": ["/ABS/PATH/beancloud/packages/mcp-server/dist/index.js"],
      "env": {
        "BEANCLOUD_API_KEY": "bc_live_YOUR_KEY",
        "BEANCLOUD_BASE_URL": "http://127.0.0.1:8080",
        "BEANCLOUD_LOCALE": "zh-CN"
      }
    }
  }
}
Manage API Keys