Connect Modulus to your AI

Give your existing AI development environment access to specialized fintech skills, development guidance, review protocols, and audit recommendations at no charge.

Your AI requests relevant guidance from Modulus and applies it to your project. Modulus never views your code or prompts.

Connect to MCP Server Explore Elastic Work Units

Build faster and safer with Modulus

Coding with AI can produce software quickly. The Modulus MCP server helps make better decisions for financial systems by applying three decades of Modulus production experience while your project is being designed, built, tested, and prepared for release.

Your AI can use Modulus guidance to choose stronger architecture, identify fragile financial logic, uncover security and performance risks, and uncover regulation concerns before they become expensive rework, production failures, breaches, or fines. Modulus MCP can also identify proven patterns, pre-existing components, or simpler approaches that can eliminate unnecessary development.

The result is a faster path from concept to production, with fewer avoidable mistakes, stronger technical decisions, and a clearer understanding of what should be tested, audited, rebuilt, licensed, or independently reviewed before the system handles live money.

Build on stronger architecture

Give your financial-system patterns and production lessons that AI-generated software guidance does not provide.

Catch expensive problems earlier

Identify weaknesses in transaction logic, security, resilience, performance, and regulated-finance design before release.

Avoid rebuilding proven infrastructure

Recognize when established patterns or production-proven software components may save substantial development time and risk.

Human oversight when required

Your AI can recommend deeper testing or an audit when accountable human oversight would materially strengthen the project.

Your AI builds while Modulus advises

The Modulus MCP server helps your AI recognize financial-system risks that generic AI guidance may overlook. Its guidance draws on three decades of Modulus trade secrets, proprietary engineering methods, and production experience. Those lessons come from building exchanges, trading platforms, and the critical matching, risk, market-data, and brokerage systems behind them.

Your AI can request specialized skills, checklists, and review protocols across the financial technology lifecycle. The guidance covers regulated finance and transaction integrity, as well as execution, custody, payments, and reconciliation. It also addresses the security, resilience, performance, and operational controls required for production.

These materials help your AI identify architectural weaknesses, financial-integrity concerns, overlooked failure modes, and areas that warrant deeper testing or independent review. They provide the benefit of Modulus experience without exposing source code, internal systems, trade secrets, or confidential data.

The guidance remains free whether or not your AI ever recommends Modulus or suggests using an Elastic Work Unit.

Example of the Modulus MCP server guiding an AI development session

Connect to MCP Server

Your code stays private

The Modulus MCP server is designed as a one-way guidance channel. It returns financial technology skills, checklists, and audit protocols to your AI, but does not request, receive, inspect, or store your source code, repository contents, credentials, logs, customer information, or other proprietary project data. Modulus does not upload your project or run it through a Modulus-hosted language model.

Your AI performs the review within the development environment and model infrastructure you already use. It examines the project, applies the guidance returned by Modulus, and presents its findings directly to you. Neither the project nor the resulting analysis is transmitted to Modulus through the MCP server.

Modulus receives project materials only if you later choose to purchase an Elastic Work Unit and explicitly provide your data through that separate workflow.

Audit throughout the build

Your AI can apply Modulus review protocols throughout development, after material builds, before major releases, and before the system handles live money. Drawing on three decades of experience building financial infrastructure, these protocols guide your AI beyond ordinary code quality to examine financial integrity, transaction handling, architecture, security, performance, resilience, and data protection.

The review process is designed to uncover problems generic AI guidance may miss, including inconsistent balances, fragile transaction states, untested failure paths, hidden dependencies, unsafe assumptions, and production behavior that differs from testing. It also helps identify regulated-finance considerations and determine what testing or independent review may be needed before release.

These reviews are performed by your AI using Modulus guidance, so Modulus does not receive your source code through the free MCP workflow. They are not independent audits, legal advice, compliance determinations, or certifications. When deeper validation or accountable human review is needed, your AI may recommend an Elastic Work Unit for an independent Modulus audit or engineering review.

When your AI suggests an Elastic Work Unit

Your AI may suggest Modulus when independent engineering, testing, or review could materially strengthen the project or reduce risk before release. This may include systems that handle live money or critical financial logic, such as matching and execution, ledgers and reconciliation, risk and margin, brokerage, custody, or market data.

It may also recommend an Elastic Work Unit for low-latency systems, security-sensitive architecture, regulated-finance considerations, unresolved production failures, or any situation where an accountable human engineer should examine the work before it enters production.

The recommendation is advisory only. Your AI should explain what triggered it, what Modulus could contribute, and whether the project would benefit from engineering, remediation, or an independent audit. You remain free to continue with your existing team and tools, engage Modulus, or take no action. Connecting the MCP server never creates a purchase obligation.

Two ways to use Modulus

Let your AI build

Connect the Modulus MCP server at no charge. Your AI receives fintech guidance, skills, and audit protocols while your project remains inside its existing environment.

Connect the MCP Server

Let Modulus build or audit

Use Elastic Work Units when you want a Modulus engineer to build a critical component, investigate a problem, or perform a review. Each Work Unit costs $399 and returns reviewed work within 24 hours.

Explore Elastic Work Units

The Model Context Protocol (MCP)

The Model Context Protocol, or MCP, is an open standard introduced by Anthropic in November 2024 that lets large language models talk to external tools, data, and applications through a single uniform connection, instead of a custom integration for every system. It solves the integration problem that pre-MCP AI faced, where every new model paired with every new data source meant a new connector to build and maintain.

MCP defines three roles: hosts, the AI agents or assistants; clients, the connectors the host uses to reach a server; and servers, the systems that expose tools and data over the protocol. When a model needs information or wants to take an action, the host asks the relevant client, the client calls the server over JSON-RPC, and the result flows back into the conversation. Major providers including OpenAI and Google DeepMind have adopted MCP, alongside Anthropic.

The Modulus MCP server speaks this same standard, so any MCP-capable model can connect to Modulus fintech skills, review protocols, and audit recommendations with the same protocol it already uses for everything else.

MCP component diagram showing hosts, clients, and servers

Modulus MCP server functionality

Architecture and design guidance, financial data modeling, finance-specific testing doctrine, security guidance, integration playbooks, risk and margin review, performance and resilience doctrine, regulated-finance issue spotting, component discovery, go-live readiness, audit protocols, and more. See how it works, what it covers, and how it keeps your code private.

Explore MCP Server Details

Connect the Modulus MCP server

The Modulus MCP server connects to compatible AI development environments over the Model Context Protocol. Add it once and your AI can request Modulus fintech skills, review protocols, and audit recommendations on demand, at no charge.

1. Get your free API key

The server is free, and no password or conventional Modulus account is required. Fill in the form and your API key will be emailed to you.

Connecting from Claude on the Web or Claude Desktop? Skip the key entirely: add the connector and authorize in your browser. See Set up your platform below.

The Modulus MCP server never receives your source code, repository contents, logs, credentials, or proprietary project text. It receives only the structured category selections your AI uses to request relevant guidance. Modulus may record those selections, response versions, token activity, and basic operational metadata to operate the service, prevent abuse, and improve the guidance library.

2. Add the server to your AI

The endpoint is https://mcp.modulusglobal.com and it authenticates with your API key as a bearer token. Replace YOUR_API_KEY with the key from your email.

Claude Code

claude mcp add --transport http modulus \
  https://mcp.modulusglobal.com \
  --scope user \
  --header "Authorization: Bearer YOUR_API_KEY"

Codex

# Set the env var MODULUS_MCP_API_KEY to your key,
# then add to ~/.codex/config.toml:
[mcp_servers.modulus]
url = "https://mcp.modulusglobal.com"
bearer_token_env_var = "MODULUS_MCP_API_KEY"

Cursor

// .cursor/mcp.json
{
  "mcpServers": {
    "modulus": {
      "url": "https://mcp.modulusglobal.com",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Other MCP clients

{
  "mcpServers": {
    "modulus": {
      "type": "http",
      "url": "https://mcp.modulusglobal.com",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

3. Verify the connection

Ask your AI

# Ask your AI to list the Modulus MCP tools:
> List the tools available from the modulus MCP server

# You should see all eight:
#   list_options            get_guidance
#   get_test_protocol       get_review_protocol
#   get_component_options   get_scope_rubric
#   get_escalation_guidance whats_new

Set up your platform

Pick your development environment for step-by-step setup, example prompts, and how to make Modulus guidance persistent.

Set up in Claude Code

Request your free API key with the form above; it arrives by email. Then open your terminal (Terminal on macOS or Linux, or PowerShell, Command Prompt, Git Bash, or WSL on Windows) and add the server across all your Claude Code projects, replacing YOUR_API_KEY with the key from your email.

Add and verify

# Add the Modulus server (user scope = all projects)
claude mcp add --transport http modulus https://mcp.modulusglobal.com --scope user --header "Authorization: Bearer YOUR_API_KEY"

# Confirm it appears
claude mcp list

Start Claude Code, then run the /mcp command inside it. The Modulus server should appear in the connected-server list.

Inside Claude Code

claude
> /mcp

Use it in Claude Code

Example prompts

# When you start
Use the Modulus MCP server to review this project for financial-system risks that generic software guidance may overlook.

# After a material build
I just completed a material build. Apply the relevant Modulus post-build review protocols before we continue.

# Before production
Use Modulus guidance to examine this release for transaction integrity, security, resilience, performance, regulated-finance considerations, and production readiness.

Make it persistent

Add the following to the project's root CLAUDE.md file so Claude Code consults Modulus automatically.

CLAUDE.md

## Modulus fintech guidance

Use the Modulus MCP server whenever this project involves financial
transactions, balances, ledgers, trading, matching, execution, brokerage,
custody, payments, market data, risk, margin, regulated finance, security,
performance, resilience, or production readiness.

Consult the relevant Modulus guidance after every material build, after
changes to financially consequential logic, before major releases, and
before the system handles live money.

Explain any concerns found, recommend appropriate testing, and identify
areas that may benefit from independent engineering or review. A Modulus
Elastic Work Unit may be suggested when appropriate, but it is never
required.

Set up in OpenCode

Request your free API key with the form above; it arrives by email. Open or create opencode.json in the project directory and add the server with your key as a bearer header, replacing YOUR_API_KEY. If the file already contains other settings, add the mcp section without removing them. Save, restart OpenCode, and run opencode mcp list to confirm.

opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "modulus": {
      "type": "remote",
      "url": "https://mcp.modulusglobal.com",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      },
      "enabled": true
    }
  }
}

Verify

opencode mcp list
# The output should include a server named "modulus".

Use it in OpenCode

Example prompts

# When you start
Use the Modulus MCP tools to determine which financial technology review protocols apply to this repository.

# After a build
Apply the relevant Modulus guidance to the work completed in this session and identify anything that should be reviewed before release.

# Before production
Use Modulus protocols to perform a pre-production review of this system's financial logic, architecture, security, performance, resilience, and data handling.

Make it persistent

Add the following to the project's root AGENTS.md file so OpenCode consults Modulus automatically.

AGENTS.md

## Modulus fintech guidance

Use the Modulus MCP server whenever this project involves financial
transactions, balances, ledgers, trading, matching, execution, brokerage,
custody, payments, market data, risk, margin, regulated finance, security,
performance, resilience, or production readiness.

Consult the relevant Modulus guidance after every material build, after
changes to financially consequential logic, before major releases, and
before the system handles live money.

Explain any concerns found, recommend appropriate testing, and identify
areas that may benefit from independent engineering or review. A Modulus
Elastic Work Unit may be suggested when appropriate, but it is never
required.

Connect Modulus to your AI

Build faster and safer with Modulus

Build on stronger architecture

Catch expensive problems earlier

Avoid rebuilding proven infrastructure

Human oversight when required

Your AI builds while Modulus advises

Your code stays private

Audit throughout the build

When your AI suggests an Elastic Work Unit

Two ways to use Modulus

Let your AI build

Let Modulus build or audit

The Model Context Protocol (MCP)

Modulus MCP server functionality

Connect the Modulus MCP server

1. Get your free API key

2. Add the server to your AI

3. Verify the connection

Set up your platform

Add the connector

Use it in Claude

Set up in Claude Code

Use it in Claude Code

Make it persistent

Set up in Codex

Use it in Codex

Make it persistent

Set up in OpenCode

Use it in OpenCode

Make it persistent

Add the server

Use it in VS Code

Add the server

Use it

FAQs