MCP Server
MCP
three.ws Autopilot
Set autopilot scopes and a daily SOL spend cap, then propose, execute, and undo agent actions.
Install
npx -y @three-ws/[email protected]
Configuration Example
{
"remotes": [],
"packages": [
{
"registryType": "npm",
"identifier": "@three-ws/autopilot-mcp",
"version": "0.2.1",
"runtimeHint": "npx",
"transport": {
"type": "stdio"
},
"environmentVariables": [
{
"description": "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.",
"isRequired": true,
"format": "string",
"isSecret": true,
"name": "THREE_WS_API_KEY"
},
{
"description": "Base URL of the three.ws API that serves the autopilot endpoints. Override only when self-hosting or targeting a preview deployment.",
"format": "string",
"default": "https://three.ws",
"name": "THREE_WS_BASE"
},
{
"description": "Per-request timeout in milliseconds. Proposal generation runs a real server-side LLM pass, so the default is generous.",
"format": "number",
"default": "60000",
"name": "THREE_WS_TIMEOUT_MS"
}
]
}
]
}
mcp
model-context-protocol
npm
By
Comments
Sign in to leave a comment