Connect Channels to Claude Code
Use Claude Code's HTTP MCP connection with a public OAuth client for Channels. You need Claude Code installed and permission to manage OAuth clients in your Cloud Project.
If Channels is already connected in your project, keep that server and go to verification. For a separate test connection, choose a distinct server name and use it in every command below.
1. Select your Project and enable Channels
Open Cloud Projects 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.
If you opened inspection details, use Back to list → Switch Projects, or close the manager when the intended Project is already active. Create a Project if needed.
Open Enabled services. Continue if Channels is listed; otherwise choose Enable service → Channels and confirm it appears. Keep this Project selected. Service enablement does not establish host authorization.
2. Register a public client
Open OAuth → Overview. If needed, choose Set up OAuth, enter Channels for Claude Code, complete the consent information and save. Preserve an existing configuration.
Open OAuth → Clients → Create client. Name it Channels for Claude Code, choose Native, leave JavaScript origins empty, and register:
http://localhost:43220/callback
Use the same port in the command below. If that port is occupied, choose another available port and change both the registered callback and command. Keep localhost and the /callback path exactly as shown.
This example follows the current Claude Code callback contract. Version 2.1.229 used 127.0.0.1; current versions use localhost. Check claude --version and use a current version before following this example.
Create the client and copy its client ID. This public client does not need a client secret. If access is denied, use Copy access request, send it to the Project owner with your Account and membership identity, and use Check access again after the owner resolves it.
3. Add the HTTP server
In a terminal in the project where you use Claude Code, replace YOUR_CLIENT_ID with the new public client ID and run:
claude mcp add --transport http --scope local --client-id YOUR_CLIENT_ID --callback-port 43220 socra-channels https://channels.socra.cloud/mcp
The local scope keeps this configuration tied to that project. If socra-channels already exists, use a distinct name in the add, login and verification commands instead of replacing the existing connection.
Check the recorded server configuration:
claude mcp get socra-channels
Confirm the HTTP URL, public client ID and callback port. Do not add authorization headers or a client secret to this public-client setup. See Claude Code's preconfigured OAuth guidance for its supported options.
4. Authorize your Account
From the same project directory, run:
claude mcp login socra-channels
Follow the Socra sign-in in your browser, choose the Account you use in Channels and approve access. Wait for Claude Code to confirm the connection. If the browser does not open, follow the terminal's sign-in instructions; keep callback URLs and authorization codes private.
If sign-in is interrupted, return to the same server and retry login after resolving its reported error. Check the exact client ID, callback hostname/port/path and enabled Channels service. Keep the Project, client and working server configurations.
5. Verify a real read
Start a Claude Code session in the same project. Use /mcp to check that the socra-channels server is connected and Channels List is available. Preserve your existing tool approval rules.
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 actual 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 the tool is unavailable, check the selected server and its connection in /mcp. If a call is denied, retain its error, confirm the authorized Account and enabled service in the client's Project, and ask the owner to resolve access before retrying.