All Products
Search
Document Center

:Manage MCP Servers

Last Updated:Sep 17, 2026

When building agentic applications, an Agent often needs to call external tools or access third-party data sources to complete complex tasks. Configuring MCP (Model Context Protocol) servers for a Workspace extends the Agent with standardized tool integration and connects it to a variety of external services. This topic describes how to create, view, edit, and delete MCP servers.

Create and manage MCP servers

  1. Log on to the AgentCore console.

  2. In the left-side navigation pane of the Workspace details page, click Tool Management.

  3. Click Create Tool and configure the following parameters.

    Parameter

    Description

    Tool type

    Required. The type of the tool. MCP: Model Context Protocol tools, which support connecting to remote MCP servers and converting HTTP to MCP. Virtual MCP: reassembles existing MCP tools into a new MCP server to make tool selection more efficient. Coming soon.

    Creation method

    Required. Available when the tool type is MCP. Connect to an MCP server: connects to an existing remote MCP server. HTTP to MCP: converts an HTTP API into an MCP tool.

    Tool name

    Required. The name of the tool.

    Description

    Optional. The description of the tool. Up to 1,000 characters.

    URL

    Required. The endpoint of the MCP server, such as mcp.example.com or 127.0.0.1. Make sure the address is reachable over the network.

    MCP Transport

    Required. The transport protocol used by the MCP server. Valid values: SSE and Streamable HTTP.

  4. Configure authentication.

    Parameter

    Description

    Enable authentication

    Specifies whether to enable authentication for the tool. When it is turned off, the authentication parameters are hidden. When it is turned on, complete the following configurations.

    Authentication method

    Required. The type of credential used for authentication, such as API Key.

    Credential source

    Required. The location where the credential is carried in a request, such as a custom HTTP header.

    Header name

    Required. Must be specified when the credential source is a custom HTTP header. The name of the request header that carries the credential, such as Authorization or X-Api-Key.

    API Key

    Required. The value of the credential. Enter it in the format required by the target service, such as Bearer followed by a space and the key.

  5. Click Create Now to create the tool.

Manage MCP tools

View MCP tool details

Click Details to view the configuration of an MCP tool.

Basic information

Field

Description

Name

The name of the tool.

Connection type

The connection type of the tool, such as remote connection.

Description

The description of the tool. A hyphen (-) is displayed if no description is specified.

MCP configuration

Field

Description

URL

The endpoint of the MCP server.

MCP Transport

The transport protocol used by the MCP server. Valid values: SSE and Streamable HTTP.

Delete an MCP tool

On the overview page, click Delete to delete the MCP tool.

Edit an MCP tool

On the overview page, click Edit Configuration to modify the tool.