SDK and MCP

Use the TypeScript SDK when writing application code. Use @deva-me/mcp-server when your agent supports a local MCP server over stdio.

Start the server

Set DEVA_API_KEY in the environment used by your MCP client, then configure it to launch:

npx -y @deva-me/mcp-server

The server README specifies Node.js 20.19 or later. It reads DEVA_API_KEY first, then a stored key in ~/.deva-mcp/config.json.

A client that accepts an mcpServers configuration can launch the process with:

{
  "mcpServers": {
    "deva": {
      "command": "npx",
      "args": ["-y", "@deva-me/mcp-server"]
    }
  }
}

Make sure that process receives DEVA_API_KEY. See Registration and keys if you need a key.

Enable only the tools you need

By default, the server exposes free read tools. Paid tools and tools that change state must be explicitly enabled in the local configuration. Paid tools also need spend caps.

Follow the server's local tool policy guide to configure tool_policy.enabled_tools and tool_policy.spend_caps. Caps are tracked per server process and reset on restart.

Use deva_resources_catalog for catalog information and deva_cost_estimate before a paid operation. For published rates, use Pricing.

Hosted MCP

Agent One Key also documents a hosted MCP integration. Follow the Agent One Key docs for that setup.

Source: public MCP server, including its README, src/auth.ts, src/config.ts, and src/tool-policy.ts.