Add an MCP server

By the end of this page you will have connected an MCP server and enabled the tools you want your agents to use.

Prerequisites

A project created (Create your first project).
Owner, Admin, or Developer role.

The wizard

From the Tools registry, open the MCP Servers tab and click Add MCP Server. The wizard header shows Step {n} of {total} with the current step name. The steps are:

Choose → Configure → Connect → Review Tools → Done

ℹ️

Choosing a template with OAuth2 authentication follows a different path — see OAuth servers. This page covers the None / API Key / Bearer Token / Custom Headers flow.

Steps

Choose a template (or set up manually)

The first step invites you to “Choose a template to get started quickly, or set up manually.” Pick a pre-configured template from the catalog to pre-fill the URL and auth, or click Manual Setup to enter everything yourself.

The Choose step showing template cards and the Manual Setup option

Configure the server

Fill in the connection details:

Field	Notes
Server URL (required)	Must start with `http://` or `https://`. Example: `https://mcp.example.com/v1`.
Server Name (required)	A human-readable name, e.g. `GitHub MCP`.
Short Name (required)	Auto-derived from the name and editable. At least 2 characters; must start with a letter and contain only lowercase letters, numbers, and hyphens. Used in tool keys: `mcp.{'{'}shortName{'}'}.<tool_name>`.
Authentication Method	None, API Key, Bearer Token, or Custom Headers (see below).
Description (optional)	e.g. `GitHub operations via MCP`.
Execution Location	Auto (Platform decides), Local (Platform), or Remote (Executor).

If you choose Remote (Executor), also pick a Target Executor. If none are registered, you’ll see “No remote executors registered. Add an executor in Project Settings → Executors.”

Remote execution is how you connect an MCP server that only exists inside your own network — discovery, testing and every tool call travel through the executor. See MCP servers on a remote executor.

The Configure step with URL, name, short name, authentication, and execution location fields

Authentication fields depend on the method:

Method	Fields
None	—
Bearer Token	Token (e.g. `ghp_xxxxxxxxxxxx`)
API Key	API Key Header Name (e.g. `X-API-Key`) and API Key Value
Custom Headers	One or more header name / value rows (Add Header)

💡

When a template provides credential help, expand How to get your credentials for provider-specific instructions and an Open provider settings → link.

Click Connect to continue.

Connect

qRaptor connects to the server (“Connecting to MCP server…”) and discovers its tools. If it fails, you’ll see Connection failed with the error and options to go Back or Retry.

Review the discovered tools

The wizard lists every discovered tool: “{serverName} ({serverUrl}) — {n} tools discovered.” All tools are enabled by default.

For each tool you can:

Enable / disable it with the toggle.
Expand inputSchema to inspect its input schema.
Set its Category — Function, Data Pull, or Action (qRaptor suggests one from the tool’s name).
Mark HIL (requires approval) — recommended for Action tools.
Click ▶ Test to try the tool before saving.

The Review Tools step listing discovered tools with enable toggles, category, HIL, and test controls

💡

The wizard’s own guidance: “All tools enabled by default. Disable tools you don’t need.” and “Mark ACTION tools as HIL (requires approval) for safety.”

The footer shows “{enabled} of {total} tools enabled.” Click Save Server (enabled once at least one tool is on).

Done

You’ll see MCP Server Added! confirming the server “connected with {n} tools ({enabled} enabled, {disabled} disabled).” Choose View Server Details or Back to Tools.

What happens next

Enabled MCP tools are now available to agents — they appear in the Tools Call node picker and can be attached to AI Agents. To change which tools are enabled, re-discover tools, or edit the connection, see Manage a server.

Common issues

“Must be a valid URL starting with http:// or https://” — fix the Server URL.
Short name rejected — it must start with a letter and use only lowercase letters, numbers, and hyphens (min 2 chars).
Connection failed — check the URL and credentials; for a private server, set Execution Location to Remote and pick an executor.
Can’t save — at least one tool must be enabled.