Connect Channels to Claude
Connect Claude to the hosted Channels MCP server using your own OAuth client. You need access to custom connectors in Claude and permission to manage OAuth clients in your Cloud Project.
Claude's Free plan allows one custom connector. If you already have a working custom connector, preserve it. A disabled Add custom connector control may be consistent with that limit, but the control alone does not confirm the cause for your account. Ask your Claude workspace owner or Claude support about availability and continue only when the custom-connector form is available. Claude's connector instructions document the limit and setup sequence.
1. Start a custom connector
In Claude, open Customize → Connectors → Add → Add custom connector. Name it Socra Channels and enter:
https://channels.socra.cloud/mcp
Choose Continue. Review the discovered authentication settings, then choose Continue again. Under Authentication, choose Sign in now. Under OAuth client, choose Use your own OAuth client. Keep the form open while you prepare the client.
For an organization-managed connector, ask its owner to add it through Organization settings → Connectors → Add → Custom → Web. Each member then connects individually. If the intended connection already exists, use it rather than replacing it. Claude's connector instructions explain the available controls and owner requirements.
2. Select your Project and enable Channels
Open Cloud Projects in another tab and choose your Account. Use Manage Cloud Projects → Switch Projects to search for and select your Project. The manager closes; confirm the active Project in Switch Cloud Project.
Create a Project if needed. If you opened inspection details, use Back to list → Switch Projects, or close the manager when the intended Project is already active.
Open Enabled services. Continue if Channels is listed; otherwise choose Enable service → Channels and confirm it appears. Keep this Project selected. Enabled service state does not establish that Claude is authorized.
3. Register the OAuth client
Open OAuth → Overview. If needed, choose Set up OAuth, enter Channels for Claude, complete the consent information and save. Preserve an existing configuration.
Open OAuth → Clients → Create client. Name it Channels for Claude, choose Web, leave JavaScript origins empty, and register this exact Redirect URL:
https://claude.ai/api/mcp/auth_callback
This is Claude's documented hosted callback. There is no final slash. Compare the callback shown in your connector before continuing.
Create the client and copy its client ID. Choose Create client secret, then copy the one-time secret into Claude's client-secret field. Keep it private; do not put it in a chat or screenshot. Close the secret dialog after the handoff.
If permission is denied, use Copy access request and send it to the Project owner with your Account and membership identity. Use Check access again after access is resolved. Permission to create a client does not imply permission to create its secret.
4. Authorize your Account
Return to the existing connector form and enter the client ID and secret. Keep discovered endpoints and leave fixed request headers empty. Finish adding the connector, then connect when prompted. Sign into Socra, choose the Account you use in Channels, and approve access.
If interrupted, return to that connection. Check its client ID, exact registered callback and enabled Channels service before retrying an error. Keep the Project and client; do not replace a working connection as a diagnostic step.
5. Verify a real read
Start a new Claude conversation. Use the conversation's + → Connectors controls to enable Socra Channels. Enable Channels List in its tool controls and review any tool approval.
Send:
Use Socra Channels to make exactly one channels_list tool call with limit 1. Do not read messages or send, create, update or delete anything. Report whether the call succeeded. An empty list is valid.
Inspect the tool execution: channels_list must run with limit: 1 and return a result. An empty list is valid. An answer without tool execution does not verify the connection.
If no tool runs, check the conversation's connector toggle and tool controls. If a call fails, retain its error and check the authorized Account and enabled service in the client's Project. Ask the Account or Project owner to resolve denied access before retrying.