Model Context Protocol

Connect your agent

WorkflowsMCP speaks MCP natively. Connect once and your agent can search workflows, read any of them, and fetch install plans it can execute step by step — checking with you only where a human is required.

What it is

A stateless streamable-HTTP MCP server at /api/mcp. Instead of reading a workflow page and copying setup steps by hand, you tell your agent what you want; it searches WorkflowsMCP, fetches an ordered install plan, and executes the parts it can. The plan marks the parts it cannot — OAuth grants, admin rights, which channel to post into — so the agent brings those back to you rather than guessing.

Workflows here are plain instructions and configs — no proprietary engine, nothing to import.

All three tools are read-only: nothing an agent calls here can change the marketplace. This prototype has no authentication, so run it locally or behind your own gateway.

Connect

Any client that speaks streamable HTTP can connect directly — there is no stdio wrapper and no SSE endpoint to configure.

terminal

claude mcp add --transport http workflowsmcp https://workflowsmcp.com/api/mcp

Adds to this project by default — add --scope user for all projects.

Every snippet prints https://workflowsmcp.com — from NEXT_PUBLIC_BASE_URL when that is set, otherwise this site’s own origin in production and the dev origin locally. Set the variable to point every snippet in the app somewhere else; the path stays /api/mcp.

Tools

Tool	Parameters	Returns
`search_workflows`	`query`optional — free text over title, tagline, tags and app names `app`optional — app slug, e.g. slack `category`optional — category slug, e.g. team-ops (the tool description lists all seven) `tag`optional — tag, e.g. standup	A compact list, most-upvoted first: slug, title, tagline, apps, tags, difficulty, setupMinutes, upvotes. Filters combine with AND; no arguments lists everything.
`get_workflow`	`slug`required — exact workflow slug	The complete workflow: description, every app with its role and full per-app setup steps (with copyable snippets), the end-to-end flow, tags, difficulty and setup time.
`get_install_plan`	`slug`required — exact workflow slug	An executable plan: prerequisites (accounts and permissions per app), steps flattened into one ordered list in the order the flow runs them, humanCheckpoints the agent must clear with its human, and verification checks. Workflows the publisher did not mark agent-installable still return a plan, with a top-level note saying to treat it as guidance for a human.

Example session

Installing the standup digest, end to end. Note where the agent stops.

You
Set up the WorkflowsMCP daily standup digest for our team.
Call
search_workflows { query: 'standup' }
Result
1 result — daily-standup-digest-slack-notion · "Collect standup thread replies, summarise them, file the digest in Notion." · starter · 25 min
Call
get_install_plan { slug: 'daily-standup-digest-slack-notion' }
Result
7 ordered steps across Slack and Notion · 2 prerequisites · 5 human checkpoints · 5 verification checks
Agent
This needs a Slack account that can create an app, and a Notion account that can add an internal connection. Step 1 posts the prompt to a channel — is #standup the right one?
You
Yes, #standup.
Agent
Step 1 done — Workflow Builder posts the prompt at 09:30 on weekdays.
Agent
Step 2 needs a Slack bot token with channels:history, channels:read, chat:write and users:read. I will not create or hold that for you — make the app at api.slack.com/apps, put the token in SLACK_BOT_TOKEN, and tell me when it is there.
You
Done, it's in SLACK_BOT_TOKEN.
Agent
Steps 3–6 done, pausing once more at the Notion integration secret.
Agent
Installed. To verify: trigger the 09:30 prompt, reply in-thread, and confirm a new page lands in Standup Log. Then run it twice — you should get one page, not two.