Connect Helios to Claude

Connect Claude to your Premium game server with a custom connector. First create a Helios API key on the correct server. Use a separate key from ChatGPT if you want to manage each assistant's access independently.

1. Add the custom connector

Open Customize → Connectors in Claude. Choose Add connector → Add custom connector, then enter:

Setting	Value
Name	Helios
MCP server URL	https://api.heliosrce.com/mcp

Choose Continue and review the detected authentication. Use OAuth with sign-in enabled. Under OAuth client, choose Use your own OAuth client (or open Advanced settings, depending on the interface), and enter:

OAuth setting	Value
Client ID	helios-claude-pilot
Client secret	Leave blank.

Use the client ID exactly as shown, including pilot, for the Premium beta. It is a public identifier, not your Helios key. Finish adding the connector.

On managed workspaces, an owner or authorized administrator may need to add the connector first. Members then connect individually. If Claude says the URL already exists, use the existing connector rather than creating another one.

2. Connect with your Helios key

1. Find Helios in your connectors and choose Connect if the sign-in flow has not already opened.
2. On the Helios connection page, paste the API key you created in the dashboard.
3. Complete the connection and return to Claude.

This guide uses OAuth. Keep the key out of chat messages and the OAuth client-secret field. The key determines your server and permitted actions.

3. Enable Helios in the conversation

Use the chat's + → Connectors menu to enable Helios. Start with:

Use Helios to show the connected server name and list its kits.
Do not make any changes.

Review any tool-access prompt and confirm the returned server is correct. A key with View kits access can inspect kits; it cannot create, edit, or delete them without the corresponding grants.

Review a change before applying it

Ask Claude to prepare a preview, then check the target server and exact changes. Approve that proposal in the original conversation when you are ready. Claude's connector/tool-access prompt and Helios's approval of a specific change serve different purposes: permitting a tool does not approve every future change.

Kit and bind changes apply to the connected game server. Shop, Battle Pass, and economy settings are shared across its Discord community. Read AI permissions and scope before enabling writes.

If the connection fails

• Authentication fails: check the URL, own OAuth client ID, and blank secret; reconnect with a valid Helios key.
• Helios is not being used: enable the connector for that conversation and explicitly ask Claude to use Helios.
• A tool is denied: check key grants, active Premium, enabled server status, and current Discord management access.
• A key expired or was revoked: create a replacement on the intended server and reconnect. Check uncertain operation results before retrying a write.

See Claude's remote MCP connector guide for current menus and workspace setup, or ChatGPT setup to connect another assistant.