Integrate Using Cursor / Claude Code (MCP Server)

Overview

The RiskOS™ MCP Server connects AI development tools like Cursor and Claude Code to your RiskOS™ account. Use it to:

• Access the embedded RiskOS™ documentation set from your assistant.
• Retrieve the current RiskOS™ OpenAPI specification and API schemas.
• Check your account configuration, including use cases and workflows.
• Guide integration work with RiskOS™-specific prompts.

Quickstart

Connect your AI development tool to the RiskOS™ MCP Server in four steps. Each step links to more detailed information in the following sections.

1. Generate an MCP Server Key. In the RiskOS™ Dashboard, go to Developer Workbench > API & SDK Keys, create a key, and copy the token. See MCP keys.

2. Add the server to your client. Configure your MCP client with the Sandbox base URL https://mcp.riskos.socure.com/sandbox and your key as a bearer token. See Client configuration examples.

3. Run your first prompt. Start a session in your client and ask a question such as "What use cases are configured for my account?"

4. Confirm the response. The assistant calls the list_usecases tool and returns your account's use cases. If your client cannot connect, see Troubleshooting.

   Example response:

   Text

   Your account has the following use cases configured:
   - consumer_onboarding
   - business_onboarding
   - login_authentication

Key features

• Embedded RiskOS™ documentation access:
  Agents can retrieve the full RiskOS™ documentation set: concepts, fields, workflows, and API behavior.
• Retrieve the latest API specification:
  Retrieve the current RiskOS™ OpenAPI specification for code generation, validation, or starting a new integration. You can also browse the API Reference directly.
• Check RiskOS™ configuration (workflows):
  List the use cases and workflows configured in your RiskOS™ account to confirm setup and reference workflow identifiers programmatically.
• Use RiskOS™-specific prompts:
  The server includes prompts tailored for RiskOS™ development, helping agents provide accurate, implementation-ready guidance.

How it works

The RiskOS™ integration ecosystem uses a hybrid architecture of Logic and Data to provide AI assistants with both procedural expertise and real-time environment context.

High impact: the RiskOS™ Integration Skill

The RiskOS™ Integration Skill is a critical feature, acting as the "operating manual" for your assistant to integrate with RiskOS™. It defines standard integration patterns to ensure your agent follows best practices for integration in a guided path rather than guessing integration steps.

• Instructional Logic: Teaches agents to handle evaluation decisions from RiskOS™ (Accept, Reject, Review).
• Task Automation: Guides assistants through multi-step integration sequences like managing API Keys or setting up webhooks.
• Expert Mode Reasoning: Ensures integration code generation is seamless and manages error-handling effectively.

Install from here RiskOS™ Integration Skill

RiskOS™ MCP Server (the "Data Layer")

The RiskOS™ MCP Server provides an interface to your environment, acting as the dynamic data source for all development tasks.

• Real-time Retrieval: Fetch the latest documentation, API schemas, and workflow metadata directly from your account.
• Account Discovery: Programmatically inspect your organization's specific solutions and active workflows.

Component comparison

flowchart LR

    subgraph Client["Your environment"]
        A["AI assistant"]
        B["RiskOS™ Skill"]
        C["MCP client"]
    end

    subgraph RiskOS["RiskOS™ platform"]
        D["RiskOS™ MCP server"]
        E["Documentation"]
        F["OpenAPI spec"]
        G["Workflows"]
    end

    A --> C
    C --> D

    D --> E
    D --> F
    D --> G

    B -.->|enhances| A

MCP keys

RiskOS™ supports MCP Server Keys for authenticating to the RiskOS™ MCP Server. MCP Server Keys provide a secure, streamlined authentication method and enable MCP Server access for all customers, including organizations that use Single Sign-On (SSO).

Manage MCP server keys

Create and manage MCP Server Keys from the MCP Server Keys section of the RiskOS™ Dashboard, under Developer Workbench > API & SDK Keys. Each key includes:

• A unique key name
• A generated authentication token
• Key status (Active or Inactive)
• A creation timestamp

You can securely view and copy the token when configuring your MCP clients.

Install and configure

The RiskOS™ MCP Server exposes a simple HTTP interface compatible with any MCP-enabled client, including VS Code, Cursor, and other AI-driven development tools. Once configured, your AI assistant can automatically access RiskOS™ documentation, API schemas, and development guidance.

The MCP Server provides separate endpoints for the Sandbox and Production environments. Use the Sandbox endpoint for testing and integration, and the Production endpoint for live traffic. Authenticate to either environment with your MCP Server Key.

Client configuration examples

Troubleshooting

Use the following table to resolve common connection issues.

Available tools

The RiskOS™ MCP Server provides the following tools for retrieving documentation, exploring workflows, and supporting integration development. The Environment column shows where each tool is available.

Example usage:

• What fields are required for Consumer Onboarding?
• Which workflows are available for Business Onboarding?
• What steps do I need to complete to integrate Verify Plus?

Advanced usage:

• Use the list_usecases tool to retrieve the list of available use cases.
• Use the list_workflows tool to identify active workflows. If there are no workflows - remind me to activate one in the RiskOS™ Dashboard.

Prompts

Prompts guide how the assistant reasons, not what data it can access. They do not call MCP tools directly.

These modes help the assistant produce higher-quality explanations or integration-level code depending on your task.

Example usage:

• documentation: Explain how a RiskOS™ workflow evaluates a request.
• integration: Generate a Python example for calling the Evaluation API.

Resources

Resources expose static, machine-readable artifacts suitable for code generation, schema validation, and IDE integration.

Example usage:

• riskos_openapi_spec: Return the schema for /api/evaluation/{eval_id}.
• riskos_openapi_spec: Extract all workflow-related paths and schema objects.
• Download and save the RiskOS™ OpenAPI specification into riskos_openapi.json using the riskos_openapi_spec resource.

---

Security best practices

The RiskOS™ MCP Server is designed for secure development assistance. The following best practices help ensure credentials and environments remain protected.

Next steps

• Install the RiskOS™ Integration Skill to give your assistant guided, best-practice integration logic.
• Explore the RiskOS™ API Reference to see the endpoints the MCP Server exposes.
• Move from Sandbox to Production by switching your client's base URL from /sandbox to /prod.