Developers

Wireflow MCP Connector

Wireflow speaks the Model Context Protocol. Connect Claude or any MCP client and let it build, inspect, and run your AI workflows on your behalf, with explicit consent and per-scope permissions.

Connect

Add a custom connector in your MCP client and point it at the Streamable HTTP endpoint below. The client walks you through Wireflow’s OAuth sign-in and a consent screen, no manual API keys, no client setup.

https://www.wireflow.ai/api/mcp

How auth works

  • OAuth 2.1 authorization code flow with PKCE (S256).
  • Dynamic Client Registration (RFC 7591), so clients self-register with no pre-shared credentials.
  • You approve a consent screen listing exactly the permissions the client asked for. Revoke anytime from settings.

Permissions

A client that asks for nothing in particular gets the read and run scopes. Anything marked opt-in is withheld unless the client names it in its OAuth scope parameter, so no existing connection silently gains it.

workflows:readView your workflows and templates
workflows:executeRun your workflows on your behalf (this spends credits)
executions:readView the status and results of your runs
models:readList the available AI models
usage:readView your credit balance and usage
workflows:writeCreate and edit workflows in your accountopt-in

Tools

whoamiConfirm which Wireflow account this connection acts as
list_workflowsList the workflows in your account
get_workflowInspect a workflow’s nodes and the inputs it accepts
list_templatesBrowse published template workflows
list_modelsList available image / video / audio models
get_credit_balanceCheck your credit balance and plan
clone_templateCopy a template into your account as a private draft (free, exact)
create_workflow_from_promptBuild a new workflow from a description and save it as a private draft
update_workflow_configChange config or prompt values on nodes in a workflow you own
run_workflowRun a workflow (consumes credits) and get an executionId
get_executionPoll a run for status and output URLs

Only run_workflow spends credits. The three write tools save private drafts and never run anything, so building a workflow costs nothing until you ask for a run.