Workflow Automation · Process street + Claude
Process Street MCP with Claude: Automate Recurring Checklists and SOPs
The short answer
Claude connects to Process Street through the Model Context Protocol, a secure standard that lets Claude use the tool with permissions you control. Once connected, Claude can help create workflows, start checklists, support standard operating procedures and check how far a process has progressed, all through plain-language requests from your team.
What is Process street?
Process Street is a collaborative workflow and checklist platform used by teams to run recurring processes consistently. It helps organisations turn standard operating procedures into step-by-step checklists that people complete together. Operations managers, compliance teams, HR, finance and service teams commonly use it to make sure routine work is done the same way every time and that completion can be tracked across the organisation.
How Claude connects to Process street through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other software. It lets Claude use a tool such as Process Street securely, reading information and taking actions only within the permissions your organisation sets. Process Street supports sign-in with an API key, so access is granted through a key that your team issues and can revoke at any time.
Once connected, Claude can typically help you create new workflows, run checklists, draft or update standard operating procedures and look up the status of processes that are in progress. A manager might ask in plain English which onboarding checklists are still open, and Claude can answer from the live data rather than from a stale report.
Permissions and approvals keep people in charge. We set up access with least-privilege rules, so Claude only sees and changes what a given role needs. Consequential actions can be routed for human sign-off, and audit logs record what was done and by whom, which supports compliance reviews.
What you can automate
Onboarding new employees
When a new hire starts, Claude can launch the matching onboarding checklist in Process Street, assign tasks to IT, HR and the line manager, and report which steps remain open. Managers no longer need to chase each person individually, and new starters reach their first week with equipment, access and paperwork in place.
Running compliance checks
Compliance teams can use Claude to start recurring audit checklists, confirm which controls have been completed for the period and flag overdue items. This gives a clear, current picture of compliance across departments without manual spreadsheet tracking, which helps with reviews and internal audits.
Maintaining standard operating procedures
Operations leads can ask Claude to turn a written procedure into a structured Process Street checklist, or to update an existing one when a step changes. Keeping SOPs and the checklists people actually follow in step with each other reduces errors and makes training new staff faster.
Tracking customer onboarding projects
Account and client teams can run repeatable onboarding checklists for each new customer, with tasks split between sales, delivery and support. Claude can report which customers are waiting on which step, so handovers happen on time and nothing is missed between teams.
Managing facilities and maintenance routines
Facilities teams can schedule recurring inspection and maintenance checklists, such as weekly safety walkthroughs or monthly equipment checks. Claude can start these runs, collect status updates in plain language and summarise open issues for the facilities manager at the end of each week.
An end-to-end workflow: New client onboarding with CRM and Microsoft 365 handover
TriggerA deal is marked as won in the company CRM.
Claude reads the won deal details from the CRM and identifies the matching client onboarding checklist in Process Street.
Claude starts a new checklist run for the client and assigns tasks to the account manager, delivery lead and finance contact.
Each owner completes their steps in Process Street, with human approval required before access credentials or contract documents are released.
Claude posts status updates to the relevant Microsoft 365 Teams channel and notifies the account manager of any overdue tasks.
When all steps are complete, Claude records the completion date back in the CRM and closes the checklist run.
OutcomeClient handovers that once took days of follow-up emails typically move in a single, traceable flow, with fewer missed steps and a clear record of who completed what.
How we set it up
Free automation audit
We review how your teams currently run recurring processes and identify the checklists and SOPs most worth automating. You receive a clear list of priorities, with no obligation to proceed.
Secure API key connection
We connect Claude to Process Street using an API key that your administrator issues. The key is stored securely, and access is limited to the workspaces and actions your roles require.
Workflow design
We map the end-to-end process across Process Street and your other systems, such as Microsoft 365, your CRM or your ticketing tool, and agree where people must approve actions.
Testing and launch
We test the workflows against real past cases, then launch with monitoring and audit logs so you can see exactly what Claude did and when.
Team training
We train the people who will use the system day to day, and provide guidance for administrators on managing keys, permissions and ongoing changes.
Who benefits
- Operations managers
- Recurring processes run to the same standard every time, with a live view of what is open and what is overdue.
- Compliance and audit leads
- Current, traceable records of completed controls and checklists, ready for internal reviews.
- HR and onboarding teams
- Faster, more consistent starts for new employees, with fewer manual follow-ups.
- IT administrators
- Controlled access through API keys with least-privilege permissions and audit logs for oversight.
Security and control
- Access uses an API key with least-privilege permissions, limited to the workspaces and actions each role needs.
- Consequential actions, such as releasing credentials or changing contract documents, can require human approval before they happen.
- Audit logs record what Claude did, when, and on whose instruction, to support reviews.
- Keys can be rotated or revoked at any time by your administrator if access needs to end.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the solution in a region that meets their data residency and privacy requirements. For India, we design around the Digital Personal Data Protection Act, 2023, and for the UAE and Saudi Arabia we align with local data protection laws. We choose the hosting region for Claude to meet each client's compliance requirements, and we confirm those choices during the audit.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Process Street MCP server do?
The Model Context Protocol server lets Claude work with Process Street in a controlled way. It typically allows Claude to create workflows, run checklists, support SOPs and check process progress, using the permissions your organisation grants. It acts as a secure bridge rather than giving Claude open access to your account.
Is connecting Process Street to Claude secure?
Security depends on how the connection is set up. We use an API key with least-privilege access, restrict it to the workspaces needed, add human approval for sensitive actions and keep audit logs. Keys can be rotated or revoked at any time. We cannot guarantee security outcomes, but we design each connection with these safeguards in place.
What can Claude actually do with Process Street?
Once connected, Claude can typically help start and track checklists, draft or update standard operating procedures, answer questions about open and overdue tasks and record progress. Users make requests in plain language, and Claude carries out the actions that their permissions allow.
How long does setup take?
Timelines vary with the number of workflows and connected systems. A focused project covering a few key checklists often moves from audit to launch in a matter of weeks, while broader rollouts take longer. The free automation audit gives you a realistic estimate for your situation.
Which plan or permissions do I need?
Generally, you need a Process Street account that supports API access, along with an API key issued by an administrator with the permissions the connection requires. The exact requirements depend on your current plan and workspace settings, so we confirm them during the audit.