# MCP security and troubleshooting

Check process or endpoint reachability, transport logs, authentication, schema compatibility, and capability discovery; keep privileges minimal while isolating the failing layer.

![MCP security and troubleshooting 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. Reproduce the problem once with the smallest safe input and record the exact message, action, and time.
3. Check process or endpoint reachability, transport logs, authentication, schema compatibility, and capability discovery.
4. Keep privileges minimal while isolating the failing layer.
5. Change one reversible condition, then repeat the same test. Preserve logs or exports before any reset.
6. **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.