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

# Other Clients

> Add brightplace Connect to any MCP client that supports remote servers.

Any client that can add a remote Model Context Protocol server over HTTPS can
use brightplace Connect. The [Claude](/install/claude),
[ChatGPT](/install/chatgpt), and [Perplexity](/install/perplexity) guides cover
the clients we test against; use this page for everything else.

## What your client needs

* Support for **remote** MCP servers (a server URL), not just local stdio
  servers.
* The ability to reach the public internet over HTTPS.
* Optional: OAuth support, if you want tool calls attributed to a connected
  account. brightplace Connect also works without it; calls are still
  rate-limited and audited by the server.

## Add the server

1. Open your client's connector, integration, or MCP server settings.
2. Add a custom remote MCP server.
3. Enter the endpoint:

```text theme={null}
https://mcp.brightplace.ai/mcp
```

4. Choose the authentication method your client offers. If OAuth is available,
   complete the brightplace consent flow; otherwise use open/no authentication.
5. Save and enable the server for the conversation or workspace where you want
   to use it.

On team, business, or enterprise plans, an administrator may need to add and
share the server before members can use it.

## Configuration reference

Some clients are configured with a JSON file rather than a settings UI. The
exact key names vary by client, but the shape is usually:

```json theme={null}
{
  "mcpServers": {
    "brightplace-connect": {
      "url": "https://mcp.brightplace.ai/mcp"
    }
  }
}
```

Check your client's documentation for the precise field names and where the
config file lives.

See [Usage](/usage) for the full tool flow, and
[Errors & Troubleshooting](/errors-troubleshooting) if a connection or tool
call fails.