Skip to main content
Any client that supports remote MCP over HTTPS and the OAuth flow below can use brightplace Connect. The Claude, ChatGPT, and 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.
  • OAuth Authorization Code with PKCE and compatible client registration. All tool calls require a signed-in brightplace identity; anonymous clients can discover tools but cannot use them.

​
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:
  1. Choose OAuth and complete the brightplace sign-in and consent flow. If your client cannot complete OAuth, use a supported client instead.
  2. 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:
Check your client’s documentation for the precise field names and where the config file lives. See Usage for the full tool flow, and Errors & Troubleshooting if a connection or tool call fails.