> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP tools

> Review MCP server and tool references, prepare input and approval policies, and track the separate discovery and execution requirements.

An MCP server describes tools exposed by an external service. Review the server and each intended action separately: knowing an endpoint does not tell you which data its tools can access or change.

<Note>
  Server configuration can be saved, but **Test Connection** is disabled and server tool discovery returns an unavailable result. This guide does not establish live discovery, runtime approval enforcement, or MCP tool execution.
</Note>

## Prepare the server and tools

<Steps>
  <Step title="Review and save the server">
    Follow [MCP servers](/agents-platform/configure/integrations/mcp-servers) to review its operator, endpoint, transport, and credential reference. Record the resulting server ID.
  </Step>

  <Step title="Document the intended actions">
    Obtain the tool names, descriptions, and input schemas from the server operator. Identify read and write actions separately. Keep discovery verification pending; do not present a manually copied schema as a successful connection test.
  </Step>

  <Step title="Review approval intent">
    The tool contract includes `approval_policy` values `require_approval_all`, `require_approval_per_tool`, and `auto_approve_all`. Decide which actions should require confirmation, but verify enforcement separately when execution is released.
  </Step>

  <Step title="Inspect agent references">
    Custom server references belong in `conversation_config.agent.prompt.mcp_server_ids`. Preserve the intended list in a complete [agent draft](/agents-platform/deploy/versioning) and read it back. Selecting a server in the dashboard's **Tools > MCP** list currently opens its details; it does not save an attachment.
  </Step>
</Steps>

## Tool-level contract

The MCP tool shape includes `type: "mcp"`, `integration_type`, `mcp_server_id`, `mcp_server_name`, `mcp_tool_name`, and `mcp_tool_description`. It can also describe `parameters`, `mcp_input_schema`, and `input_overrides`.

These fields describe a tool configuration. They do not make tool-management endpoints available to personal API keys, and they do not create a functioning server connection. Use the [tool overview](/agents-platform/configure/tools/overview) for the current management restriction.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does saving an approval policy display a confirmation?" id="faq-mcp-tools-approval">
    Not by itself. A stored policy is authoring intent. Runtime confirmation and enforcement need separate verification when the execution path is available.
  </Accordion>

  <Accordion title="Are native MCP references the same as custom server IDs?" id="faq-mcp-tools-native">
    The agent schema separates `mcp_server_ids` from `native_mcp_server_ids`. Use the identifier required by the relevant [integration workflow](/agents-platform/configure/integrations/overview), rather than moving IDs between these lists.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.