Skip to main content

Method API and MCP

Use Method CLI to create, edit, save, and run methods. The CLI handles browser sign-in, saved versions, and run uploads.

Saved files and runs

The CLI uses these routes on the selected server. Requests require the computer’s access token. Keep tokens out of method files and logs. New methods use format: method/2. The server validates names, data shapes, checks, and dependencies before saving. A saved version has not necessarily passed a run. Each run names the exact saved version it used.

MCP 5.2

Connect to https://dark-wave-v6i08.run.mcp-use.com/mcp with Streamable HTTP and OAuth with PKCE. A source response includes method_id, version_id, schema_version, source, and its sha256. Preserve the source text when checking this hash. Historical files can report workflow/1; new files report method/2. The executor also accepts workflow/2 without changing its saved hash. Only workflow/1 needs a rewrite before execution. Run the .method file through Method to get separate actions and checks, saved results, and dashboard logs. Copying a general prompt into an agent does not start Method’s executor. The old /api/workflows and /api/cli/workflows routes and the four legacy MCP tool names remain available. JSON fields such as workflow and workflow_id are kept for existing clients.