Three.ws Autopilot MCP Server

Three.ws Autopilot is an MCP integration. Set autopilot scopes and a daily SOL spend cap, then propose, execute, and undo agent actions.

Packages and local setup

The published npm package is @three-ws/autopilot-mcp, version 0.2.1. Its declared MCP transport is stdio.

The package declares THREE_WS_API_KEY (required): REQUIRED. The agent owner's three.ws credential — a three.ws API key (sk_live_… / sk_test_…) or an OAuth access token. Sent as Authorization: Bearer on every request; every autopilot endpoint is owner-scoped and rejects unauthenticated calls. This credential can move real SOL via execute_proposal — treat it like a password. THREE_WS_TOKEN / THREE_WS_BEARER are accepted aliases.; THREE_WS_BASE: Base URL of the three.ws API that serves the autopilot endpoints. Override only when self-hosting or targeting a preview deployment.; THREE_WS_TIMEOUT_MS: Per-request timeout in milliseconds. Proposal generation runs a real server-side LLM pass, so the default is generous..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.2.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.