# Using Foxora as an MCP server

Enable the Foxora MCP server surface, choose exposed capabilities and authentication, add it to the client, then test discovery and one bounded call.

![Using Foxora as an MCP server 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. Enable the Foxora MCP server surface.
3. Choose exposed capabilities and authentication.
4. Add it to the client.
5. Test discovery and one bounded call.
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.

## Client configuration shape

Use the URL shown by **Settings → MCP Server**. A client configuration follows this shape:

```json
{
  "mcpServers": {
    "foxora": {
      "url": "<foxora-engine-url>/mcp"
    }
  }
}
```

Foxora shows the exact exposed tool list beside the configuration. Review that list in the client before approving calls.


## 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.