SimPilot
DocumentationExamplesAPI Reference
Sign in

Search Documentation

Find pages across the documentation

Getting Started

IntroductionQuickstartHow It Works

Core Concepts

AI AgentSimulation WorkflowEngineering PipelineKnowledge BaseArchitecture

Features

OverviewChat InterfaceCanvas & ArtifactsSharing & CollaborationExports & ReportsVoice InputMulti-Model AIProjectsTemplates & WorkflowsFile UploadsDeep ResearchWeb SearchCode ExecutionImage GenerationMCP ConnectorsInteractive DashboardsParallel ExecutionURL RetrievalFreeCAD CADSimulationsTemplatesConvergence Monitoring

Simulation

OverviewSupported TypesMesh GenerationError RecoveryBatch & SweepsResults Comparison

Studies & Analysis

OverviewDOE & Parametric SweepsOptimizationComparison

Validation & Reviews

OverviewBaselines & VersioningEngineering ReviewsRegulatory Compliance

3D Viewer

OverviewVisualization ToolsKeyboard Shortcuts

Enterprise

OverviewAdmin PanelOrganizationsKnowledge ManagementMethod Packs

Account

Getting StartedSettingsBilling

Examples

OverviewAerodynamicsPipe FlowHeat TransferStructural
  1. Docs
  2. Features
  3. MCP Connectors

MCP Connectors

Extend SimPilot with external tools via the Model Context Protocol.

MCP (Model Context Protocol) Connectors let you extend SimPilot's capabilities by connecting to external tool servers. Each connector provides additional tools that the AI can invoke during conversations, enabling integration with company APIs, geometry software, custom solvers, and more.

What is MCP?

The Model Context Protocol is an open standard for connecting AI assistants to external tools and data sources. An MCP server exposes a set of tools (functions the AI can call) and optionally resources (data the AI can read). SimPilot acts as an MCP client, discovering and invoking these tools on your behalf.

Setting up a connector

Open connector settings

Navigate to Settings > Connectors (or go directly to /settings/connectors).

Add a new connector

Click Add Connector and provide the MCP server URL. SimPilot supports two transport protocols:
  • HTTP -- Standard request/response over HTTPS
  • SSE (Server-Sent Events) -- Streaming transport for long-running tools

Authenticate

If the server requires authentication, SimPilot uses OAuth 2.1 with PKCE. You will be redirected to the server's authorization page to grant access. Tokens are stored securely and refreshed automatically.

Review available tools

Once connected, SimPilot displays the list of tools the server provides along with their descriptions. You can enable or disable individual tools.

Using connectors in chat

Once a connector is set up, its tools appear in the connector dropdown in the chat input area. Toggle connectors on or off per conversation to control which external tools the AI can access.
When a connector is active, the AI can invoke its tools just like built-in SimPilot tools. For example, if you connect a geometry tool server, the AI might call its export_geometry tool to retrieve a mesh directly from your geometry system.
Tool discovery
The AI automatically discovers what each connector tool does by reading its description and parameter schema. You do not need to teach the AI how to use your custom tools -- just describe what you want to accomplish.

Connector scope

Connectors can be configured at two levels:
ScopeDescription
Per-userOnly you can see and use this connector. Ideal for personal API keys or development servers.
GlobalAvailable to all users in the workspace. Set up by administrators for shared company tools.

Example use cases

Authentication

MCP Connectors use OAuth 2.1 with PKCE (Proof Key for Code Exchange) for secure authentication:
  • No client secrets are stored in the browser
  • Tokens are scoped to the minimum required permissions
  • Automatic token refresh keeps sessions alive without re-authentication
  • Revoke access at any time from the connector settings page
Security considerations
Only connect to MCP servers you trust. Each connector's tools can read data from and write data to the connected system. Review the tool list and permissions before enabling a connector in production conversations.

Built-in connectors

SimPilot ships with the following built-in connectors, ready to enable from the connector settings page:
ConnectorDescription
Paper SearchSearch academic papers across multiple repositories
Semantic ScholarQuery the Semantic Scholar academic graph for papers, authors, and citations
Wolfram AlphaComputational intelligence for math, physics, and engineering queries
Materials ProjectAccess materials science data -- crystal structures, properties, and phase diagrams
OnshapeConnect to Onshape CAD for geometry export and model inspection
FreeCADInterface with FreeCAD for parametric geometry and mesh export
JiraTrack simulation tasks, link results to Jira issues, and update ticket status
LinearManage engineering workflows and link simulation runs to Linear issues

Requirements

  • The MCP server must be reachable over HTTPS from SimPilot's infrastructure
  • The server must implement the MCP specification (tool listing, tool invocation, and optionally resource listing)
  • OAuth 2.1 is required for authenticated servers; unauthenticated servers are supported for internal/development use
PreviousImage GenerationNextInteractive Dashboards

On this page

What is MCP?Setting up a connectorUsing connectors in chatConnector scopeExample use casesAuthenticationBuilt-in connectorsRequirements