Oscilar AI and the MCP Server: Oscilar's agents in the platform, your AI assistant at the controls

Up until today, analysts who worked through a policy change in Claude still had to retype the input, workflow steps and test cases into Oscilar, the Agentic Risk Platform, by hand.

Now, Oscilar AI gives you one assistant across the entire platform, backed by Oscilar's specialized agents. The Oscilar MCP Server brings your own AI assistant into Oscilar, so it can explore, build, and test on your behalf.

Oscilar AI works inside the platform. The MCP Server connects your own AI assistant. Both run under the same permissions.

TL;DR

• Oscilar AI and the Oscilar MCP Server are now generally available.

• Oscilar AI is the assistant inside the Oscilar platform. Open it from a workflow, a case, or any other screen and it already knows what you’re looking at. It works with Oscilar’s specialized agents to explain decisions, build schemas and aggregations, and generate test cases.

• The Oscilar MCP Server connects Claude, Claude Code, or any MCP-compatible client to your Oscilar environment. Your assistant can turn a policy into a draft workflow, test it, and work cases without anyone retyping it into Oscilar.

• Both run under your existing roles, permissions and audit trail. Workflow changes from your assistant are saved as drafts, and someone on your team deploys them in Oscilar.

• The MCP Server is included with Oscilar at no additional cost.

Oscilar AI: one assistant, Oscilar's agents behind it

Oscilar AI is how you work with all of Oscilar's agents. Open it from a workflow, a case, or anywhere else in Oscilar and it already knows what you're looking at. It remembers your past conversations. Capabilities that used to sit in separate tools, like answering questions about the documentation or generating workflows, now come through the same conversation:

• Create complex schemas from a plain-language description or a data sample.

• Build a full set of aggregations in one request instead of one at a time.

• Explain why a decision was made, rule by rule, without tracing the workflow yourself.

• Clarify what a workflow does, whether you inherited it or need to walk an auditor through it.

• Generate a test case for a workflow before it goes live.

How Oscilar AI helps analysts work cases

In a case, an analyst opens an alert. Instead of clicking through tabs to piece together what happened, they ask Oscilar AI for a summary. The results come back with the case context and what Oscilar's agents have already found, including how the sanctions agent scored it. But while the agents gather the context, the analyst still makes the final call.

The same holds when you build. Start a chat from a workflow and the conversation stays scoped to it, so Oscilar AI can explain it and edit it. Ask it to create a new input and it checks what already exists in your environment, validates the result inline, and links you straight to the new object.

The Oscilar MCP Server: bring your AI assistant into Oscilar

A lot of risk work starts outside the platform. An analyst reasons through a policy change in Claude, gets it right, then switches to Oscilar and retypes the input, the workflow steps, and the test cases by hand. However, retyping is tedious and time-consuming. It’s also where human error creeps in.

The Oscilar MCP Server removes that step. MCP (Model Context Protocol) is an open standard for connecting AI assistants to outside systems. Connect Claude, Claude Code, or any MCP-compatible client to your Oscilar environment, sign in, and your assistant can work directly in Oscilar, using everything else it already has in front of you: the policy doc, the spreadsheet, the ticket, the code.

From there, you can ask your assistant to:

• Turn a policy into a workflow. Read a credit or fraud policy and draft the matching rules, decision tables, inputs, and aggregations in Oscilar.

• Test before anything ships. Send test events through a draft and check the resulting decisions against the policy.

• Explore what's already running. List and inspect workflows, cases, decisions, schemas, and rules, all actions that help when you inherit an environment.

• Work cases. Update, assign, and route cases, and set up queues and quality control.

• Tune Oscilar's agents, including their prompts and knowledge files.

• Answer questions about your analytics, configuration history, and user access.

Oscilar built the MCP Server's tools for these jobs specifically, rather than exposing the raw API. All you have to do is describe what you want, in plain language, like "send scores under 700 to manual review," and the MCP Server handles the steps and validation underneath.

Example: updating a credit policy with the Oscilar MCP Server

Your credit policy team publishes an updated policy. A risk analyst opens Claude, shares the new policy, and asks it to update the matching workflow in Oscilar. Claude drafts the rule changes through the MCP Server and runs test events to confirm the new thresholds behave as written. The analyst reviews the draft in Oscilar and deploys it. From then on, Oscilar's agents work the cases that workflow produces, and Oscilar AI is there when the analyst wants to know why a decision went the way it did.

Permissions, audit and drafts in the Oscilar MCP server

Both products run under your existing roles, permissions and audit trail:

• Your assistant acts as you. The MCP Server signs in through your company's single sign-on and inherits your existing roles and permissions. There's no shared service account and no privilege escalation, and every action is recorded under your name in the audit trail.

• It only sees what you can see. If your role can't reach it in Oscilar, your assistant can't either.

• It drafts, people deploy. Every workflow change your assistant makes is saved as a draft. Deploying happens only in Oscilar, by someone on your team..

This is the principle behind every Oscilar agent: AI gathers context and recommends, and your team confirms and owns the outcome.

Why connect your AI assistant through the Oscilar MCP server

Scripts on raw APIs run outside your roles and audit trail. The MCP Server runs inside them, keeping the work where it belongs. Analysts get an assistant inside the platform that brings Oscilar's agents to them. Engineers and analysts who already work in Claude get a supported, governed way to build in Oscilar without retyping anything. Both run on the same customer view, the same permissions, and the same audit trail.

Get started today

Oscilar AI is rolling out to customers now. Look for it throughout the platform.

The Oscilar MCP Server is included with Oscilar at no additional cost. You can connect it from your own Claude setup in a few minutes; just add your Oscilar environment as a connector in Claude or your MCP client, sign in with your Oscilar account, and start asking. 

For more information, read Oscilar MCP Server documentation and our current use cases.

Want to see it in action? Book a demo.

FAQ

What is Oscilar AI?
Oscilar AI is the assistant built into the Oscilar platform. You can open it from a workflow, a case, or anywhere else in Oscilar. It works with Oscilar’s specialized agents to explain decisions, build schemas and aggregations, and generate test cases.

What is the Oscilar MCP Server?
The Oscilar MCP Server connects your own AI assistant to your Oscilar environment through the Model Context Protocol (MCP). Your assistant can then explore, build, and test in Oscilar directly, without anyone retyping work by hand.

Which AI assistants work with the Oscilar MCP Server?
Claude, Claude Code, and any other MCP-compatible client. Users add their Oscilar environment as a connector in their own setup and sign in with their Oscilar account.

What can my AI assistant access and change in Oscilar?
Only what your role can reach. The assistant signs in through your company’s single sign-on, inherits your permissions, and records every action under your name. Workflow changes are saved as drafts, and someone on your team deploys them in Oscilar.

Does the Oscilar MCP Server cost extra?
No. It’s included with Oscilar at no additional cost.