MCP Servers#

Open MCP Servers to register Model Context Protocol (MCP) integrations so assistants and agents can call external tools. Decide which servers are connected, which tools are enabled, and which tools may run automatically.

Use this page when you need to:

Connect a new MCP server (HTTP, STDIO, or SSE) for Chat or agent workflows.
Verify whether a server is connected and which tools it exposes.
Limit blast radius by enabling only approved tools or auto-execution.
Fix “tool unavailable” or reconnect a failed integration.

From this page you can see connection health, how many tools are enabled versus discovered, and auto-execution settings for each server.

Next: Add an MCP server, enable tools on the server details page, then grant user access in AI Access unless Allow on all virtual keys applies.

MCP Servers overview#

What are MCP tools?#

MCP tools are actions that an assistant or agent can use outside the chat itself. For example, a tool can search a repository, read a document system, create a ticket, query a calendar, or call an internal service.

An MCP server is the connector that provides those tools. After the server is registered, OptScale AI discovers the tools it offers, and administrators decide which tools are enabled and who can use them.

Do I need an MCP server?#

Connecting an MCP server is optional. You may need one if you encounter any of these situations:

“The AI doesn't know what's in our internal system.” Connect that system through an MCP server to make its available data accessible to the AI.
“I keep copying information from another tool into the chat.” Connect the tool so the AI can retrieve the information directly.
“I want the AI to search our internal documentation or data.” Connect the relevant data source through an MCP server.
“I want the AI to perform an action in another system.” An MCP server can provide tools for actions such as creating an issue, querying a database, or retrieving a file.
“The AI has the model, but it doesn't have the tools it needs to complete my task.” Connect an MCP server that provides the required capabilities.

If none of these situations applies to you, you probably don't need to configure an MCP server.

How MCP servers work#

An MCP server registration tells OptScale AI how to reach an external tool provider (URL, transport, authentication). After connection succeeds, the platform discovers tools on that server and lets you control which tools users may call.

Typical setup order:

Add an MCP server and wait for Connected status.
Open MCP server details → TOOLS tab and enable approved tools.
Grant the server to users in AI Access, or enable Allow on all virtual keys during registration.
Verify tool availability in Chat or your agent workflow.

Registering a server alone does not expose tools until they are Enabled on the TOOLS tab and the user has access.

For platform context, see Architecture Overview — MCP in the platform.

MCP server lifecycle#

Before you begin#

Complete these checks before you open the add form:

An organization is selected.
You have the MCP server URL (for HTTP/SSE) or host configuration (for STDIO) and any required credentials.
Outbound network access from OptScale AI to the MCP endpoint is allowed (firewall, proxy, DNS).
You know whether tools should be available to all virtual keys or only assigned users in AI Access.

Next: Add an MCP server, complete after you save, then verify.

The MCP Servers list shows each integration's connection status, tool counts, and row actions. Click a server name to open its details page.

Add an MCP server#

Complete the prerequisites first. For copy-paste values, see the HTTP example. To start from a curated configuration, use Browse MCP presets in the setup path below.

1. Open MCP Servers in the Admin UI.

2. Click + ADD to open the Add MCP Server page.

3. Choose a setup path:

Preset-based MCP server

Use Browse MCP presets when OptScale AI ships a curated configuration for a common integration.

Click + ADD → Browse MCP presets.
Filter or search for the provider (for example calendar, repository, or documentation tools).
Select a preset card and follow inline instructions to populate the form.
Review every pre-filled field and add secrets (tokens, API keys) manually before SAVE.

Review presets before save

Preset configurations may require customization. Confirm MCP server URL, authentication, and headers match your environment.

Manual path

Name — Unique identifier for this server in your organization.
Connection type — Transport the MCP server uses (Streamable HTTP (HTTP), Server-Sent Events (SSE), Standard Input/Output (STDIO)).
MCP server URL — Endpoint URL for HTTP/SSE servers (include scheme and path).
Authentication type — Method required by the MCP server (None, Headers, OAuth 2.0). Provide credentials when prompted.

4. Under Server options, configure operational settings:

Code mode client — Enable for code-oriented MCP client workflows.
Ping available for health check — Enable when the server supports ping; disable for servers that reject ping requests.
Allow on all virtual keys — When on, all organization virtual keys may use this server without per-user assignment in AI Access.
Tool sync interval — How often the platform refreshes the tool list from the MCP server.

5. Click SAVE.

6. Wait until the server row shows Connected status. If status fails, see Troubleshooting and use RECONNECT from the details page after fixing configuration.

Optional actions:

Click CANCEL to return without saving.

Field reference

Connection type — Must match how the MCP server exposes its protocol.
Allow on all virtual keys — Broad access; prefer off and use AI Access assignment for tighter control.
Tool sync interval — Lower values discover new tools faster; higher values reduce polling load.

After you save#

Registration is not complete until tools are enabled and users can reach them:

Open the server details page.
Select the TOOLS tab and enable each tool users need. Optionally set Auto-execute and Cost (USD) per tool.
Click SAVE on each modified tool row.
Unless Allow on all virtual keys is on, open AI Access and grant this MCP server to users who need it.
Verify from Chat or your agent client.

Verify MCP server#

Confirm the integration end to end:

MCP Servers list — Row status is Connected.
MCP Servers → click the server name → Overview tab → Details — shows the expected enabled-tool and auto-execute counts after you configure the TOOLS tab.
Details → Tools tab — Required tools show Enabled on.
AI Access — Test users have this MCP server assigned (skip if Allow on all virtual keys is on).
Chat — Start a session that should call an enabled tool and confirm the tool runs or appears as available.

If tools do not appear, wait one Tool sync interval cycle or use RECONNECT, then recheck the TOOLS tab.

Troubleshooting#

Server does not reach Connected status

Verify MCP server URL, Connection type, and Authentication type.
Confirm outbound network access from OptScale AI to the endpoint.
Try disabling Ping available for health check if the server does not support ping.
Click RECONNECT on the details page after correcting configuration.

Connected but no tools listed

Open TOOLS and wait for sync; check Tool sync interval.
Confirm the MCP server exposes tools to the credentials you configured.
Use RECONNECT to force a fresh discovery pass.

Tools enabled but unavailable in Chat

Confirm tools are Enabled on the TOOLS tab and changes were saved.
Assign the server to the user in AI Access, or enable Allow on all virtual keys.
Confirm the user selected the correct organization and has allowed providers for the Chat session.

Auto-execute or cost settings ignored

Save each tool row after editing Auto-execute or Cost (USD).
Confirm the summary line on the TOOLS tab reflects your enabled and auto-execute counts.

MCP server examples#

Example: HTTP MCP server (manual)#

Use this pattern for a remote MCP server reachable over HTTP.

Table 1: Example MCP server — Streamable HTTP
Field	Example value
Name	`github-tools`
Connection type	Streamable HTTP (HTTP)
MCP server URL	`https://mcp.example.com/mcp`
Authentication type	None
Code mode client	Off unless you need code-oriented MCP workflows
Ping available for health check	On if the server supports ping; off otherwise
Allow on all virtual keys	Off when access should be assigned per user in AI Access
Tool sync interval	Default or per your operational needs

After save, open Tools, enable approved tools, and assign the server to test users in AI Access.

MCP server details#

Open a server from the MCP Servers list to review configuration, verify health, and manage tools. Use Reconnect to re-establish the connection or Edit to change configuration.

The page includes two tabs:

Overview — Server configuration and operational information.
Tools — Available tools and tool-specific settings.

Overview tab#

The Overview tab displays the configuration and operational details for the selected MCP server.

The Summary section shows the server identifier, name, connection type, connection details, authentication method, configured request headers, virtual key access settings, and code mode client configuration.

The Details section displays operational information, including ping availability, the tool synchronization interval, the number of enabled tools, and the number of tools configured for automatic execution.

Tools tab#

The Tools tab lists all tools discovered on the selected MCP server and lets you control their availability and execution behavior.

A summary line above the table shows the total number of available tools, how many are enabled, and how many are configured for automatic execution. Use this information to verify the current tool configuration without reviewing every row.

The tools table lists one row for each discovered tool.

Identify a tool by its Tool name. The column displays the tool identifier returned by the MCP server, together with a short description and an Args summary showing the parameter names and expected formats. Click the chevron (>) at the beginning of the row to expand it and view additional details when they are provided by the server.

The Enabled column lets you control whether a tool is available in Chat and other MCP-enabled workflows.

The Auto-execute column lets you control whether a tool can run automatically without requiring separate approval.

The Cost (USD) column lets you specify an optional per-use cost for usage accounting or operational cost tracking.

Click SAVE to apply changes made to the corresponding tool. The button becomes available after you modify the tool configuration.

Enabled tools become available according to the server configuration, virtual key access settings, and AI Access assignments.

Manage MCP servers#

Edit an MCP server#

1. Open the server from the MCP Servers list or its details page.

2. Click EDIT.

3. Update operational settings:

Code mode client
Ping available for health check
Allow on all virtual keys
Tool sync interval

Connection fields Name, Connection type, MCP server URL, authentication are not editable.

4. Click SAVE to apply changes.

Optional actions:

Click CANCEL to discard edits.
Use DELETE to remove the server. See Delete an MCP server.

Changing Allow on all virtual keys or sync settings affects all users who rely on this integration—review the Tools tab after save.

Delete an MCP server#

1. Open the server for editing from the MCP Servers list or details page.

2. Click EDIT, then DELETE on the edit form.

3. Confirm when prompted.

The server and its discovered tools are removed from the organization. Users lose access in Chat and agent workflows until a replacement server is registered and assigned.