SAS Viya MCP integration connects an approved AI assistant to selected Viya capabilities through Model Context Protocol. We configure the connection, limit available tools and test one workflow with your team before you decide where to use it.
For Clinical programming leaders, SAS platform owners and IT reviewers
Follow a clinical programmer from a question in an approved assistant to a source record in SAS Viya. See where the connection helps, where it stops and what your team receives.
Discovery PilotSample Study / DEMO-042
At your pace · 6 scenes
Select Play to watch the workflow, or explore this scene.
01 / Start with the Work
A Familiar Question. A Clear Starting Point.
A programmer needs the QC job behind an adverse-event summary. The approved assistant becomes a way to find that information, without changing how the team accepts clinical work.
What This Helps WithFind the relevant record without searching through disconnected screens.
Clinical Programmer Original INNOVIZZ interface illustration
The task is to find and inspect. No job is started and no clinical data is changed.
02 / Define the Access
The Connection Has a Defined Scope.
The selected tools and the user’s permissions determine what can be retrieved. In this discovery pilot, inspecting job information is allowed; starting a job is outside the scope.
What INNOVIZZ EstablishesThe client, identity, permitted tools and approved data path.
Tool results may reach the assistant’s model provider. The complete deployment determines the data path.
Illustrated Connection
Approved AssistantThe request
↓
Configured MCP ConnectionSelected tools + user access
↓
SAS ViyaPermitted job information
Outside This PilotExecution is not enabled here. No job was started. An execution pilot needs a separate scope, permissions and review process.
03 / Find the Source
Bring the Right Job Into View.
The connection retrieves the selected job information available to this user. The record identifies the study, workspace and output so the programmer can check that it is the right match.
What the Team GainsA named source to inspect, rather than an unsupported answer.
Sample Job Record
AE Summary QC
QC-AE-017
Read Only
Study
DEMO-042
Workspace
Clinical Test
Registered Output
AE Summary · Table 14.3.1
Latest Recorded Run
RUN-042
Run State
Completed
A run state is one fact. “Completed” does not establish that the output passed QC or was accepted for use.
04 / Explain What Was Found
An Answer You Can Check Against Its Source.
The assistant summarizes the retrieved facts and identifies the source. The programmer can inspect that record instead of treating fluent wording as proof.
Why It MattersKeep retrieved facts separate from a decision about output quality.
Illustrative Assistant Answer
AE Summary QC is registered for DEMO-042 in the Clinical Test workspace.
Its latest recorded run, RUN-042, is marked Completed. This record does not establish QC acceptance.
Source: QC-AE-017 / RUN-042
Inspect the Sample Source +
Job
QC-AE-017 · AE Summary QC
Study / Workspace
DEMO-042 / Clinical Test
Registered Output
AE Summary · Table 14.3.1
Run
RUN-042 · Completed
QC Acceptance
Not established by this record
These are prepared sample fields, not a live SAS response.
05 / Keep the Reviewer in Control
The Programmer Decides the Next Step.
The job was found. The output still needs the appropriate QC evidence. The reviewer can request that evidence or keep the item in review under the team’s existing process.
The BoundaryFinding a completed run does not approve a clinical output.
Sample Review Desk
AE Summary · Table 14.3.1
✓Source job identified QC-AE-017
✓Run state retrieved Completed
○QC acceptance Not established
QC acceptance is not established. No message is sent and no output is approved.
06 / Make the First Engagement Concrete
Start with One Useful Connection.
INNOVIZZ assesses your environment, configures the agreed connection and tests its behavior with your team. You decide whether the pilot is useful before expanding the scope.
Your Next StepBring one workflow, your Viya release and your approved AI client.
Readiness and ScopeOne task, prerequisites and acceptance criteria.
Configured ConnectionAgreed client, identity and selected tools.
Test RecordsAllowed actions, denied requests and failure behavior.
Operating HandoverGuidance, responsibilities and change procedures.
Production use and any required qualification or validation are agreed separately.
Scene 1 of 6
Interactive interface simulation. Inspect the prepared job response, review the finding and follow the handoff.
Read the Walkthrough +
Ask. A programmer asks for the AE summary QC job for sample study DEMO-042.
Limit. This configured discovery pilot allows job information retrieval. Starting a job is outside its scope.
Find. Job QC-AE-017 identifies the registered AE Summary output and RUN-042 in Clinical Test.
Explain. The assistant summarizes the recorded state, Completed, and points to its source. QC acceptance is not established.
Review. The programmer checks the facts and requests QC evidence or keeps the item in review. No clinical output is approved here.
Decide. INNOVIZZ scopes and configures one suitable pilot, tests the controls and provides the operating handover.
To respect client confidentiality, this uses sample records and an original interface. Your implementation depends on your environment, technology stack, permissions and review requirements.
Start with One Task
Choose the Access You Actually Need.
Inspecting platform information and executing code need different controls. We agree one pilot route, the permitted inputs and the criteria for accepting its result.
01 / Discovery Pilot
Discover and Inspect.
Help a programmer or platform owner find selected metadata, report definitions or job information through their approved assistant.
Enable supported read-only tools for the task.
Check which information the signed-in user can retrieve.
Test unavailable sources and denied requests.
Your decision
Does the connection help the intended user find the right information within the agreed access limits?
Tools that write or launch work stay outside this pilot. The returned information still needs an approved data path.
02 / Execution Pilot
Execute a Defined Task.
Connect an assistant to an agreed SAS task in a test environment, then inspect what was run and what it produced.
Use approved test inputs and a defined execution context.
Agree permissions, approval steps and failure handling.
Review code, logs and outputs against acceptance criteria.
Your decision
Can your team explain the action, assess the result and operate the workflow under its procedures?
Execution is a separate scope. General SAS code execution can change data, so a tool label alone is not an approval control.
Start with suitability. We confirm the Viya release, selected APIs, licensing, AI client and identity setup before agreeing a build. Existing SAS 9.4 or LSAF workflows require a separate integration assessment.
The Engagement / SAS Viya MCP Integration
What Your Team Receives.
Choose one discovery or execution pilot around a defined task. Agree the selected deliverables and review criteria in the scope.
01
Readiness and Scope
A release and dependency review, documented data path, selected task and acceptance criteria.
At Review
Is MCP suitable for this workflow and environment?
02
Configured Connection
The agreed server and client setup, identity configuration and selected tools for the pilot.
At Review
Can the intended users access only the agreed capabilities?
03
Tested Controls
Records of allowed actions, denied requests, failure handling and reviewed task outputs.
At Review
Do permissions and review steps behave as specified?
04
Operating Handover
Versioned configuration, operating guidance, responsibilities and change or rollback steps.
At Review
Can your team operate and change the accepted integration?
Responsibilities from the Start
Make the Review Part of the Scope.
A working connection is one part of the engagement. The pilot also establishes who can use it, what they can do and who accepts the result.
01
Before Connection
Your platform and security leads confirm the environment, client, identity and permitted data flow. INNOVIZZ documents the selected task, dependencies and acceptance checks.
Platform Owner + Security
02
During the Pilot
INNOVIZZ configures the agreed integration and records allowed actions, denied requests and failure behavior. Your programming or operations lead reviews the task results.
INNOVIZZ + Workflow Owner
03
Before Operational Use
Your authorized team accepts the scoped work and its operating handover. Any qualification, validation or production release follows your own quality and change-control process.
Authorized Owner + QA Where Required
Before You Commit
Questions Before You Connect.
What Problem Does This Solve? +
It gives an approved AI assistant a defined connection to selected Viya capabilities, so the team can inspect information or perform an agreed task from that client. The engagement tests whether that connection is useful for your actual workflow and documents the controls needed to operate it.
Does This Replace SAS or Its Licenses? +
No. The MCP server provides a connection to SAS capabilities. Your licensed Viya environment, the entitlements for selected services and the approved AI client remain prerequisites. SAS 9.4 and LSAF are assessed separately; this is not a universal connector for every SAS installation.
Does All Data Stay in Our Environment? +
That depends on the complete deployment. The assistant and its model provider may receive tool results, even when the MCP server runs in your environment. We map that data path, narrow what the pilot exposes and confirm the arrangement with your security team before use.
Does MCP Make AI-Generated SAS Code Validated? +
No. MCP standardizes the connection, not the correctness of generated code or analytical outputs. An execution pilot needs appropriate review, reference checks and documented acceptance. A regulated use also needs the qualification and validation work required by your quality system.
How Are Timing, Fees and Support Agreed? +
We first confirm the task, environment readiness, selected tools and review requirements. The written scope sets deliverables, buyer involvement, timing, fees and handover. Ongoing support, third-party licenses and later workflows are identified separately.
Capabilities depend on the selected SAS release, client, deployment and entitlements. SAS trademarks belong to SAS Institute Inc.; no endorsement is implied.
Clinical / Your Next Decision
Scope One Viya Workflow.
Tell us where your team needs an assistant to connect with SAS. We will establish whether MCP fits the task and what a first pilot would need.
30-Minute Scope Conversation
Bring One Workflow.
Useful Context for the Call
Your Viya release, approved AI client, example task, available test environment and the people responsible for access and acceptance.
Choose a time on Calendly. Any assessment or build is agreed separately.
If You Proceed
A readiness decision and, if suitable, an agreed pilot with configured access, test records and an operating handover. Production use and any required validation are scoped separately.
01
Confirm the Fit
Discuss the workflow, readiness and the person responsible.
02
Agree the Scope
Review deliverables, responsibilities, timing and fees in writing.
03
Decide Whether to Proceed
Agree the evidence and review criteria before authorizing the work.
Built for Your Team to Operate.
Receive the agreed source or configuration, specifications, test records and operating handover. The statement of work identifies client-owned deliverables, existing INNOVIZZ methods, third-party licenses and support terms.
