# Overview

Understand MCP clients, servers, transports, advertised capabilities, configuration, approval boundaries, and the difference from Composio plugins.

![MCP in Foxora v5.0.3](/docs/images/v5.0.3/settings/mcp-server.webp)

## Where this lives

Open **Settings → MCP Server**.

Model Context Protocol connects Foxora to external tool and resource servers. Foxora can consume configured MCP servers and can expose supported Foxora capabilities to an MCP client.

> **Safety:** An MCP server can run code or access external systems with its own privileges. Trust the publisher, pin configuration where possible, and never place secrets in arguments or prompts.

## Steps

1. Open **Settings → MCP Server**.
2. Understand MCP clients, servers, transports, advertised capabilities, configuration, approval boundaries, and the difference from Composio plugins.
3. Use **Settings → MCP Server** to enable or inspect Foxora’s MCP endpoint and exposed capabilities. For external MCP servers, configure the trusted transport and credentials through the supported tool or plugin flow.
4. **Confirm the result.** Call one read-only tool with controlled input, inspect its result and server logs, then verify disconnecting the server removes those capabilities from new work.

## Choose the right path

- Use local stdio for a server installed on this device.
- Use remote transport for an authenticated managed endpoint.
- Use a Composio plugin when the target SaaS application is already supported.


## Confirm it worked

- Call one read-only tool with controlled input, inspect its result and server logs, then verify disconnecting the server removes those capabilities from new work.
- The screen, command, file, run, or destination named in this guide reflects the expected state.