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

# MCP and custom integrations

> Add remote HTTP MCP servers, local command MCP servers, API-key integrations, and environment variables safely.

Custom MCP integrations let Strawberry connect to tools that are not built into the app.

Open `strawberry://settings/integrations`, then use **Add MCP**.

## MCP server types

### HTTP MCP servers

HTTP MCP servers run remotely or locally and communicate over HTTP, SSE, or Streamable HTTP.

You provide:

* Name
* Server URL
* Optional API key
* Optional OAuth sign-in when supported

### Command MCP servers

Command MCP servers run as local subprocesses that communicate over stdin and stdout.

You provide:

* Name
* Full command line
* Optional environment variables

Example command shape:

```bash theme={null}
npx -y @modelcontextprotocol/server-filesystem /path/to/folder
```

## Environment variables

Command MCPs can receive environment variables. Use them for API keys or configuration the server needs. Values are encrypted at rest.

## Security

Only add MCP servers you trust.

<Warning>
  Command MCPs run as local processes with your system permissions. Strawberry does not verify
  third-party MCP servers for you.
</Warning>

## Best practices

* Prefer official vendor MCP servers when available.
* Read the server documentation before adding it.
* Scope local filesystem MCPs to the narrowest folder that solves the task.
* Avoid putting long-lived secrets into untrusted tools.
* Disable or remove custom MCPs when a project ends.