Workflow Automation · Leverly + Claude
Leverly MCP with Claude: Automate Workflows Through Natural Language
The short answer
Claude connects to Leverly through the Model Context Protocol (MCP), an open standard that lets Claude use software securely. Once connected with an API key, Claude can trigger workflows, manage automations, fetch results and update process states from a natural language request, with access limits set by your organisation.
What is Leverly?
Leverly is a workflow automation platform. It connects the apps your business already uses and coordinates actions between them, so repetitive steps run automatically with fewer manual handoffs. Operations teams, IT departments and business managers typically use it to keep processes moving smoothly and quickly. Leverly also offers a direct API, and an MCP connection allows AI agents and chatbots to work with it.
How Claude connects to Leverly through MCP
The Model Context Protocol is an open standard that works like a universal adapter between Claude and other software. It lets Claude securely read information from a tool and take actions in it, using permissions your organisation controls. For Leverly, the connection is made with an API key, so access is tied to a credential you can issue, limit and revoke.
Once connected, Claude can work with Leverly using plain language. For example, a manager can ask Claude to start a particular workflow, check whether a process has finished, pull the result of a recent automation, or move a process to its next state. Claude carries out these requests through Leverly rather than through a separate interface.
Permissions and approvals keep people in charge. We typically configure the API key with least-privilege access, so Claude can only perform the actions a given workflow needs. Consequential changes, such as starting high-impact automations or altering live process states, can be set to require a person's approval first, and every action can be recorded in an audit log.
What you can automate
Starting a workflow on request
A department head asks Claude to start the onboarding workflow for a new hire. Claude triggers the matching Leverly automation with the right details, so account setup, equipment requests and welcome tasks begin without someone opening the platform. The team gets a confirmation once the workflow is running.
Checking process status
Operations managers often need to know where a process stands. Through Claude, they can ask whether an order-fulfilment or approval workflow has completed, and Claude fetches the current result from Leverly. This saves time chasing colleagues and gives a clear picture of work in progress.
Updating process states
When a step is finished outside the platform, someone can tell Claude to mark the matching process as complete or move it to the next stage. Claude updates the state in Leverly, keeping records accurate and preventing duplicate follow-up work across the team.
Managing routine automations
Teams can use Claude to review, switch on or pause routine automations, such as a weekly reporting run or a recurring data sync. Typical requests are simple and phrased in everyday language, which reduces the need for technical staff to handle small changes.
Retrieving results for reporting
Finance and operations leads can ask Claude to gather the results of recent workflow runs and summarise them for a report. This helps reduce manual copying of figures between systems and speeds up regular review meetings.
An end-to-end workflow: Invoice exception handling
TriggerA finance analyst asks Claude, 'Start the exception review for any invoice flagged today.'
Claude uses the Leverly MCP connection to start the invoice exception workflow and fetch the list of flagged invoices.
The workflow pulls matching purchase orders and supplier details from the organisation's ERP system.
Leverly routes each exception to the correct approver and records the request in the ticketing system.
An approver is asked to confirm or reject each adjustment before anything is posted.
Once approved, Claude updates the process state in Leverly to closed and returns a summary to the analyst.
OutcomeExceptions are cleared faster, with a clear approval trail and fewer manual lookups between finance, procurement and suppliers. Results vary by business and process.
How we set it up
Free automation audit
We review your current processes and identify the workflows in Leverly and your other systems that are worth automating. You receive a clear recommendation at no cost.
Secure connection
We connect Claude to Leverly using an API key, issued and stored securely with least-privilege access. Keys can be rotated or revoked at any time.
Workflow design
We design the end-to-end workflow across Leverly and your other business systems, deciding which actions Claude can take alone and which need a person's approval.
Testing and launch
We test the workflow against real past cases, then launch with monitoring and audit logs so you can see every action taken.
Team training
We train your staff on how to make requests in plain language, what to expect from Claude, and how to escalate when something needs a human decision.
Who benefits
- Operations manager
- Starts and tracks processes with simple requests instead of navigating multiple screens.
- IT head
- Controls access through scoped API keys and keeps a full audit trail of automated actions.
- Finance lead
- Gets faster status updates and results for reporting, with approvals kept in place.
- Department head
- Launches routine workflows, such as onboarding, without waiting for technical support.
Security and control
- API keys are scoped to least-privilege access, so Claude can only perform the actions each workflow requires.
- Consequential actions, such as high-impact automations or changes to live process states, can require human approval before they run.
- Every action is recorded in an audit log for review and accountability.
- Keys can be rotated or revoked immediately if access needs to change.
- Testing against real past cases takes place before any workflow goes live.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude integration in their chosen region to align with local data protection expectations. Businesses in India must consider the Digital Personal Data Protection Act, 2023, and we design data flows to support its requirements. Organisations in the UAE and Saudi Arabia are subject to local data protection laws, and we select a hosting region that meets those obligations. Compliance depends on your specific circumstances, and we help you assess it 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 Leverly MCP server do?
The Leverly MCP server lets Claude and other AI agents connect to Leverly securely. Through it, Claude can trigger workflows, manage automations, fetch workflow results and update process states using natural language requests. It acts as a bridge, so the AI works within Leverly's own capabilities and your permissions.
Is connecting Claude to Leverly secure?
Security depends on how the connection is set up. We use an API key with least-privilege access, so Claude only gets the permissions a workflow needs. Sensitive actions can require human approval, and every action is logged. Keys can be revoked at any time if access needs to change.
What can Claude do with Leverly once connected?
Typically, Claude can start workflows, check whether processes have completed, retrieve results for reporting, switch automations on or off, and move process states forward. Requests are made in everyday language. The exact actions available depend on the permissions granted to the API key.
How long does setup take?
Timelines depend on the number of workflows and systems involved. A focused connection with a single workflow can often be launched within a few weeks, while broader multi-system projects take longer. The free automation audit gives you a realistic estimate before any work begins.
Which plan or permissions are needed?
In general, you need access to Leverly with an API key that has permission for the actions you want Claude to perform. The exact requirements depend on your Leverly account and how your organisation has configured it. We confirm what is needed during the audit.