Assuric MCP Server

MCP (Model Context Protocol) is a way for AI assistants like Claude and ChatGPT to connect directly to the tools you already use, so you don't have to copy and paste information back and forth. Instead of manually pulling data out of a platform to hand to an AI, MCP lets that platform and the AI talk to each other directly, securely, and in real time.

Assuric offers a remote MCP server that makes this easy to set up. With minimal configuration, you can connect your Assuric workspace to any MCP-compatible AI assistant using your existing Assuric account!

Capabilities through MCP are scoped to your Assuric account's permissions within a workspace, and can be further scoped granularly, so you stay in control of exactly what data and actions are available through the connection.

The connector can be used both to pull/read information from your Assuric workspace, as well as make updates to certain items.

Write-back actions will prompt for user approval inline with your MCP client settings and operations appear in your platform activity log with source "MCP" alongside the user who performed them, so all actions are fully traceable.

AI can make mistakes - check outputs carefully and reference citations before trusting content.

The Assuric connector is available as a Remote MCP Server published to common connector directories, and also available at the following URL:

You can connect using OAuth with the same sign in flow you use to login to your Assuric workspace.

Adding the connector to an existing organisational account can be done with minimal configuration from the dashboards of common AI applications (MCP clients), with instructions provided below:

You may need to ask a platform administrator to add the Assuric connector to your organisation. (Steps 1 & 2).

The Assuric MCP is a well supported Claude Connector, and can be installed to Claude with a few clicks!

1. Navigate the Settings -> Connectors / Browse Connectors and search for "Assuric". Alternatively, visit the Assuric Connector directory listing directly.

2. Click Connect to Claude

3. Sign in to your Assuric account, and then select which organisation you wish to connect to, and the level of permissions you which to grant MCP:

4. You will now see the tools available to your AI chat and can begin interacting with Assuric from Claude! Try asking Claude questions about your hazard log, policies, or evidence catalogue.

Note that connections are scoped to one workspace, if you wish to access multiple workspaces, you can add a new connector and name each one accordingly e.g: "Assuric (My Workspace)"

You may need to ask a platform administrator to add the Assuric connector to your organisation. (Steps 1 & 2).

1. Navigate to Settings -> Apps -> Advanced Settings -> Enable "Developer Mode"-> Click "Create App"

2. Add a new any name e.g: Assuric , connection type of Server URL with URL https://mcp.assuric.com and authentication "OAuth" (default). Then click "Create".

3. Follow the on screen prompt to "Sign in with Assuric"

4. Sign in to your Assuric account, and then select which organisation you wish to connect to, and the level of permissions you which to grant MCP:

5. You will now see the tools available to your AI chat and can begin interacting with Assuric from ChatGPT! Try asking ChatGPT questions about your hazard log, policies, or evidence catalogue.

Note that connections are scoped to one workspace, if you wish to access multiple workspaces, you can add a new connector and name each one accordingly e.g: "Assuric (My Workspace)"

Microsoft uses the "Copilot" name across several products, and not all of them support external MCP servers. The consumer Copilot app (web, Windows, iOS) has no MCP extensibility. To use Assuric from Microsoft 365 Copilot, you add the server as a tool on an agent in Copilot Studio, then publish that agent to Microsoft 365 Copilot. This requires a Copilot Studio licence, and you may need a platform administrator to complete steps 1–5.

The Assuric MCP server uses the Streamable HTTP transport. Copilot Studio dropped support for the deprecated SSE transport in August 2025, so make sure you are not configuring a legacy SSE connection.

Note that connections are scoped to one workspace, if you wish to access multiple workspaces, you can add a new connector and name each one accordingly e.g: "Assuric (My Workspace)"

Because Copilot Studio routes MCP traffic through Power Platform connector infrastructure, any Data Loss Prevention policies your tenant applies to connectors will also apply to Assuric.

For full detail on the Copilot Studio side of this setup, see Microsoft's guide to connecting an agent to an existing MCP server. Developers building a declarative agent instead can follow Build a plugin for a declarative agent from an MCP server, and point it at the same https://mcp.assuric.com endpoint.

Whilst instructions are provided for the most common AI applications, the mcp server can be connected to using the url above and OAuth from anywhere e.g Claude Code:

In Claude Code, run /mcp and select assuric. A webpage will open in your Assuric app to authorise MCP.