<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3636689&amp;fmt=gif">
Skip to content
English
Contact Support Customer portal
  • There are no suggestions because the search field is empty.

Connecting your AI assistant to Chainels

Connect Claude, Microsoft Copilot, or ChatGPT to your Chainels community with the Chainels MCP server.

You can connect AI assistants such as Claude, Microsoft Copilot, and ChatGPT to your Chainels community using the Chainels MCP server. Once connected, your assistant can read and act on your Chainels data — messages, events, bookings, and services — on your behalf.

Note: The Chainels MCP server is currently in beta. The available tools and their behaviour may change. Need help? Contact Chainels support.

The assistant acts on your behalf. When connected, it uses your Chainels account and permissions: it can read what you can read and post what you can post. Always review any message, event, or booking before you confirm it.

What can you do with it?

You can ask your assistant to work with your community data in plain language. For example: "Summarize this week's messages in my community and draft a reply to the most urgent one."

Your assistant can help with:

    • Messages & timeline — read, draft, post, and edit messages
    • Events & questions — create and manage them
    • Bookings — browse bookable services and time slots, and view reservations
    • Context — look up your user, communities, and channels
Before you start

All assistants connect to the same server URL: https://mcp.chainels.com/mcp

    • Claude — no preparation needed. Claude registers itself automatically; you only sign in to Chainels.
    • Microsoft Copilot and ChatGPT — you first need to create an OAuth client in the Chainels developer portal to get a Client ID and Client Secret.

Creating your OAuth client (Copilot and ChatGPT only)

    1. Go to www.chainels.com/developer
    2. Create a new OAuth client of type Authorization Code
    3. Leave the redirect URI blank for now — you'll add your client's callback URL once it is shown during setup
    4. Note your Client ID and Client Secret

Some clients also ask for these OAuth endpoints:

    • Authorization: https://www.chainels.com/oauth/authorize
    • Token: https://www.chainels.com/oauth/access_token
    • JWKS: https://www.chainels.com/oauth/jwks.json

Note: For now you have to accept all scopes when authorizing. This may be narrowed down to per-use-case scopes in a later release.

Connecting Claude
    1. Open Claude and go to Settings → Connectors
    2. Click Add custom connector
    3. In Remote MCP server URL, paste https://mcp.chainels.com/mcp
    4. Click Add
    5. A popup opens — sign in to Chainels with your account
    6. Approve the requested access (accept all scopes)
    7. The connector now shows as connected. Open a chat and ask "Who am I?" to confirm

You don't need to change anything under Advanced settings — Claude doesn't require a Client ID or Secret for Chainels.

Connecting Microsoft Copilot (Copilot Studio)

This connects a Microsoft 365 Copilot agent built in Copilot Studio to the Chainels MCP server. Make sure you have created your Client ID and Client Secret first (see Before you start).

    1. Go to copilotstudio.microsoft.com and open (or create) your agent
    2. In the left sidebar, click Tools
    3. Click + Add a tool → New tool, then choose Model Context Protocol (MCP)
    4. Enter the server details: a name (e.g. Chainels MCP), the server URL https://mcp.chainels.com/mcp, and authentication type OAuth 2.0
    5. Copilot Studio shows three OAuth 2.0 options. Choose "Manual" — Chainels does not support automatic client registration, so Dynamic discovery and Dynamic will fail
    6. Fill in the Manual fields: your Client ID and Client Secret, Authorization URL https://www.chainels.com/oauth/authorize, Token URL and Refresh URL https://www.chainels.com/oauth/access_token, and accept all scopes
    7. Click Create. Copilot Studio shows a callback URL — copy it and add it as a redirect URI on your OAuth client at www.chainels.com/developer, then click Next
    8. Sign in to Chainels in the popup and approve access
    9. Toggle on the tools you want, click Add to agent, then Save
    10. Test by asking "Who am I?" — it should return your Chainels username
Connecting ChatGPT

Custom MCP connectors require Developer Mode, which a workspace admin or owner needs to enable (available on ChatGPT Business, Enterprise, and Edu, as well as Plus, Pro, and Team). You also need your Client ID and Client Secret (see Before you start).

Admin (one-time):

    1. Open Workspace Settings
    2. Go to Permissions & Roles → Connected Data
    3. Enable Developer Mode / custom MCP connectors

Connect:

    1. Go to Settings → Connectors
    2. Click Add custom connector
    3. Paste the server URL: https://mcp.chainels.com/mcp
    4. Choose OAuth as the authentication type
    5. Enter your Client ID and Client Secret
    6. Click Connect, sign in to Chainels, and approve access (accept all scopes)
    7. Enable the tools you want, then ask "Who am I?" to confirm
Testing your connection

Ask your assistant: "Who am I?" If it replies with your Chainels username, the connection works.

Trying it out safely first

Want to test before connecting to production? Use the Chainels demo environment. The setup steps are identical — just swap in these values:

    • MCP server URL: https://mcp.demo.chainels.com/mcp
    • Developer portal: demo.chainels.com/developer
    • Authorization: https://demo.chainels.com/oauth/authorize
    • Token: https://demo.chainels.com/oauth/access_token
    • JWKS: https://demo.chainels.com/oauth/jwks.json

Note: You need a separate Chainels account and OAuth client on the demo environment — production credentials don't work on demo.

Troubleshooting
    • 401 Unauthorized during setup — the callback/redirect URL is not whitelisted. Copy the redirect URL shown by your client and add it to your OAuth client at www.chainels.com/developer.
    • 401 Unauthorized after setup — wrong Client ID/Secret or an expired token. Re-enter your credentials in the connection settings.
    • invalid_scope — a requested scope isn't allowed on your OAuth client. Check the allowed scopes in the developer portal.
    • The tools list is empty — wrong server URL. Confirm it is exactly https://mcp.chainels.com/mcp (including the /mcp path).
    • A tool disappeared or behaves differently — this can happen during the beta. Re-check the tool list in your client.

Still stuck? Contact Chainels support.