# Add a custom MCP tool

Use MCP to connect another tool service required by your workspace. Open **Resource Center → Tools → Custom tools** and select the creation action to open the MCP form.

## Prepare connection information

Ask the service maintainer for its URL, transport, exact tool name, and authentication method. **MCP Tool Name must exactly match the name exposed by the service.** It is not the friendly display name you choose in MOI.

## Complete the form

| Field | Value |
| --- | --- |
| Name (required) | A readable name for your team |
| Description (required) | Capability, applicable tasks, inputs, and outputs |
| URL (required) | The MCP service endpoint |
| MCP Tool Name (required) | The exact service-defined tool name |
| Transport | SSE or streaming HTTP, as supported by the service |
| Authentication | The method required by the service |

## Choose authentication

Selecting an authentication method reveals the corresponding fields. Fill only those required by the service.

| Method | Use when |
| --- | --- |
| None | The service explicitly requires no authentication |
| Bearer Token | The service supplies a bearer token |
| API Key | The service requires a key under a specified key name |
| Basic | The service requires a username and password |
| Custom Headers | The service requires custom request-header names and values |

The current OAuth 2.0 option is unavailable. Do not treat it as a supported setup flow. Enter credentials only in the corresponding configuration fields, not in descriptions or conversation prompts.

## Save and validate

Submit, then check the custom-tool list and configuration details. [Bind the tool](bind-tools.md) to the target agent and test a small query. For a tool-not-found error, check **MCP Tool Name** first. For connection failures, check the URL, transport, authentication, and network.

This form creates a connection; the MCP service determines the operations it exposes.