Data & Analytics · 21risk + Claude
21risk MCP with Claude: Faster Checklists, Audits and Compliance Tracking
The short answer
Claude works with 21risk through the Model Context Protocol, an open standard that lets Claude use the tool securely. Once connected with an API key, Claude can create audits, update checklists, assign actions and monitor compliance tasks from a plain-language request, within permissions the organisation sets.
What is 21risk?
21risk is a web application for checklist, audit and compliance management. It helps teams organise risk processes in one place so they spend less time on paperwork and more time on what matters. Typical users include quality, health and safety, operations and compliance teams who run regular inspections, audits and follow-up actions across sites or departments.
How Claude connects to 21risk 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 securely, reading information and taking actions, with permissions the organisation controls. 21risk can be connected either through its MCP server or a direct API, depending on what suits the team.
Once connected, Claude can typically read existing checklists and audits, create new audits, update checklist items, assign actions to named people and check on open compliance tasks. A team member might simply ask for the overdue actions from last month's site inspections, and Claude retrieves and summarises them.
Access is set up with an API key and least-privilege permissions, so Claude only sees and changes what it needs. Consequential actions, such as closing an audit or reassigning a critical finding, can require a person to approve them first. Audit logs record what was done, keeping people in charge throughout.
What you can automate
Creating audits from a request
A quality manager can ask Claude to set up a monthly site audit using the standard checklist for a given location. Claude creates the audit in 21risk, pre-fills the sections and assigns it to the right inspector, saving the admin work that usually takes time at the start of each cycle.
Updating checklists in bulk
When a procedure changes, a compliance lead may need the same new step added to many checklists. Claude can identify the affected checklists and update them, with the lead reviewing the list before changes go live. This keeps templates consistent across sites without manual editing.
Assigning corrective actions
After an audit finds issues, Claude can turn each finding into an action, assign it to the responsible manager and set a due date. The team gets a clear list of who owns what, reducing the risk of findings being lost between meetings.
Monitoring overdue compliance tasks
An operations head can ask for a summary of all open or overdue compliance tasks by department. Claude gathers the data from 21risk and presents it in a short report, so leaders can spot patterns and chase delays before they become serious problems.
Preparing for external reviews
Before a regulator or client visit, a compliance team can ask Claude to pull evidence of completed audits and closed actions for a chosen period. This makes preparation faster and more consistent, though people still check the records before they are shared.
An end-to-end workflow: Monthly site audit to corrective action tracking
TriggerA calendar reminder or a request from the operations manager at the start of each month.
Claude creates the monthly site audit in 21risk using the approved checklist for each location.
Inspectors receive their assigned audits and complete the checklist items.
Claude reviews the completed results and flags any failed items for the site manager.
Claude creates corrective actions in 21risk and assigns each to the responsible person with a due date.
A summary of open actions is sent to the operations team in Microsoft 365 Teams, and the manager approves any escalations.
OutcomeAudits start on time, findings are assigned quickly, and leaders see one clear view of open actions across sites. Typically, this reduces manual admin and the chance of missed follow-ups.
How we set it up
Book a free automation audit
We review your current checklists, audit cycles and compliance tasks to identify the workflows worth automating first.
Set up secure access
We create a dedicated 21risk API key for Claude with least-privilege permissions, so access is limited to the workflows you approve.
Connect Claude to 21risk
We connect Claude through the 21risk MCP server or direct API, then design the workflow across 21risk and your other systems such as Microsoft 365, CRM or ticketing.
Test against real cases
We run the workflow on past audits and actions to check accuracy, and refine approval steps before anything goes live.
Launch, monitor and train
We launch with monitoring and audit logs in place, then train your team on how to ask Claude for what they need and how approvals work.
Who benefits
- Quality and compliance managers
- Faster audit set-up and a consistent checklist library across sites.
- Health and safety leads
- Corrective actions are assigned and tracked without manual follow-up emails.
- Operations directors
- A clear, current view of overdue compliance tasks across departments.
- IT and data governance teams
- Controlled API access with logs, so automation stays within approved boundaries.
Security and control
- Access uses a dedicated API key with least-privilege permissions, limited to agreed actions.
- People approve consequential changes, such as closing audits or reassigning critical findings.
- Audit logs record what Claude did and when, supporting internal review.
- Test runs on past records confirm accuracy before the workflow goes live.
- Access can be revoked or rotated at any time if requirements change.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the workflow in the region that matches their data policies. In India, deployments are designed to align with the Digital Personal Data Protection Act, 2023. For organisations in the UAE and Saudi Arabia, we configure access and hosting to meet local data protection laws. In every region, the hosting location is chosen to meet your specific requirements.
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 21risk MCP server do?
The 21risk MCP server gives Claude a secure way to work with your 21risk data. It typically allows Claude to read checklists and audits, create new records, update items and assign actions, all through natural language requests. It acts as a standard connection point, so the setup stays consistent and controlled.
Is connecting 21risk to Claude secure?
Security depends on how access is configured. We use a dedicated API key with least-privilege permissions, limit Claude to agreed workflows, require approvals for consequential actions and keep audit logs. Access can be revoked at any time. We do not guarantee compliance outcomes, but we design controls around your requirements.
What can Claude do with 21risk once connected?
Typically, Claude can create audits, update checklist items, assign corrective actions and report on open or overdue compliance tasks. Users make these requests in plain language, for example asking for last quarter's overdue actions by site. The exact actions available depend on the permissions you approve.
How long does setup take?
Timelines vary with the number of checklists, workflows and connected systems. A focused single workflow can often be connected and tested within a few weeks, while broader programmes take longer. Your free automation audit gives a realistic timeline before any work begins.
Which plan or permissions are needed?
Generally, you need an active 21risk account with the ability to generate an API key and the permissions required for the actions you want Claude to take. Your administrator should confirm what your account allows. We will check this during the free automation audit.