Process Street

@Process Street show me all active workflows in our account and tell me which ones have the most runs this month

I found 12 active workflows in your Process Street account. The top three by run count this month are: 'Client Onboarding' (47 runs), 'Weekly Sales Review' (18 runs), and 'Employee Offboarding' (9 runs). The Client Onboarding workflow appears to be your highest-volume process. Would you like me to create a new run from any of these templates, or see details about a specific workflow's structure?

This example shows the MCP's ability to list workflows and pair that data with the AI's analytical reasoning. The response is illustrative — actual run counts depend on your team's activity. Requires read access to workflows via API key.

@Process Street create a new run of our 'New Hire IT Setup' workflow for Jordan Lee starting Monday

I've created a new workflow run for 'New Hire IT Setup' with the name 'Jordan Lee - IT Setup'. The run is now active in Process Street with a unique ID (wfr_abc123xyz). All tasks in the workflow are initialized and ready for your team to complete. You can assign specific tasks to team members directly in Process Street, or I can help you update task assignments if you provide the task IDs.

This demonstrates the MCP's core write capability: launching a new workflow instance from a template. The response confirms the action taken but doesn't auto-assign tasks — that requires additional calls. Side-effect: a live workflow run is created in your account.

@Process Street search our 'Customer Feedback' data set for all rows where satisfaction score is below 3 and summarize the common themes

I found 8 records in the 'Customer Feedback' data set with satisfaction scores below 3. Common themes from the feedback include: slow response times (mentioned in 5 records), unclear pricing documentation (3 records), and difficulty navigating the onboarding workflow (4 records). The most recent low-score entry was submitted 2 days ago citing 'support took 48 hours to respond'. These patterns suggest opportunities to improve response SLAs and clarify onboarding materials.

This example pairs the MCP's data set search tool with the AI's ability to synthesize patterns across records. The summary is illustrative — actual themes depend on your data set's structure and content. Requires the data set to exist and have searchable form fields configured.

When Process Street wins for repeatable client kickoffs

A 6-person agency onboards 3-5 new clients per month, each requiring the same 12-step checklist: contracts signed, Slack channel created, discovery call scheduled, project tracker initialized. The Process Street MCP lets Switchy create a workflow run from the onboarding template the moment a deal closes in your CRM, then mark tasks complete as the team progresses. The Complete a Workflow Run tool closes the loop when onboarding wraps, triggering downstream automations. This works when your onboarding is genuinely repeatable—same steps, same order. If every client needs a bespoke process, you're fighting the tool. If you onboard fewer than 2 clients per month, the setup overhead outweighs the gain. For teams running the same playbook 20+ times a year, this MCP turns checklist chaos into a one-command operation.

How this MCP enforces exit checklists at scale

A 15-person startup with quarterly turnover needs to ensure every departure hits the same compliance steps: laptop return, access revoked, exit interview scheduled, final paycheck processed. The Process Street MCP creates a workflow run when HR logs the termination date, then tracks completion across IT, finance, and people ops. The Undelete Workflow Run tool recovers runs if someone accidentally archives an in-progress offboarding. This is the right call when you have regulatory or audit requirements that demand proof of process—healthcare, fintech, or any vertical where missing a step costs you. If your team is under 8 people and turnover is rare, a shared Google Doc is faster. For teams where offboarding happens monthly and compliance matters, this MCP is the audit trail you need.

When Process Street is overkill for ticket workflows

A 4-person support team wants to standardize how they resolve complex tickets: reproduce the bug, escalate to engineering, notify the customer, close the loop. The Process Street MCP could create a workflow run per ticket and mark steps complete as the team progresses, but the Find Data Set Rows tool is designed for structured records, not freeform ticket metadata. If your tickets live in Zendesk or Linear, those tools already track status and handoffs—adding Process Street is a second source of truth that drifts out of sync. This MCP makes sense only if your support process is so rigid that every ticket follows the exact same 8-step playbook, which is rare outside of tier-1 triage. For most support teams, this integration adds ceremony without adding clarity. Stick with your ticketing system's native workflows unless compliance demands a separate audit log.