Connect AI assistants (MCP)

Connect your AI assistant to Sleak, then choose its workspace and Read or Edit access. The assistant can only use the permissions of your Sleak account.

Members can connect assistants while the workspace allows MCP access. Owners and Admins can turn it off.

https://api.sleak.ai/mcp

ConnectCopy Anchor Link

ClaudeCopy Anchor Link

The button opens Claude's Add custom connector dialog with Sleak filled in.

1. Click Continue.
2. Check the detected settings.
3. Click Continue.
4. Under OAuth client, choose Register automatically. Sleak doesn't support Use Claude's published identity.
5. Click Add.

Without the button, open Customize → Connectors in Claude, click + Add and then Add custom connector, and enter Sleak and the address above.

In Claude Team and Enterprise, an Owner adds the connector for the whole organization. They use this button or Organization settings → Connectors. Each member then clicks Connect next to it under Customize → Connectors.

Anthropic's guide: Custom connectors using remote MCP

Claude CodeCopy Anchor Link

Install the Sleak plugin. It brings the connection and skills that show Claude how Sleak works. You need Claude Code v2.1.275 or later:

/plugin install sleak-app --marketplace sleak-ai/sleak-claude-plugin

This command connects only the server, without the plugin:

claude mcp add --transport http sleak https://api.sleak.ai/mcp

Anthropic's guide: Connect Claude Code to tools via MCP

ChatGPTCopy Anchor Link

1. In ChatGPT, open Plugins.
2. Choose + → Add custom MCP server.
3. Enter Sleak as the name.
4. Paste the address above under Connection.
5. Choose OAuth as the authentication.
6. Confirm with I understand and want to continue.
7. Click Create as a plugin.
8. Install the new plugin.

Your ChatGPT plan and the rules of your ChatGPT workspace decide whether you may add your own MCP servers.

OpenAI's guide: Add custom MCP server

Microsoft CopilotCopy Anchor Link

Sleak connects to agents you build in Microsoft Copilot Studio.

1. Open your Copilot Studio agent's Tools page.
2. Choose Add a tool → New tool → Model Context Protocol.
3. Enter Sleak as Server name.
4. Describe the use of Sleak under Server description.
5. Paste the address above as Server URL.
6. Choose OAuth 2.0 as the authentication.
7. Choose Dynamic discovery as the type.
8. Click Create.
9. Click Next.
10. Click Create a new connection.
11. Sign in to Sleak.
12. Click Add to agent.

Keep the tool on End user credentials, as it is by default. Each person then connects with their own Sleak account. With Maker-provided credentials, everyone who uses the agent acts as you in Sleak.

The data policies of your Power Platform environment decide whether you may add MCP servers. You can publish the agent to Microsoft Teams and Microsoft 365 Copilot.

These don't work with Sleak:

• Connectors in Microsoft 365 Copilot that an admin creates in the Microsoft 365 admin center. They need a client registered in advance, and Sleak doesn't support this yet.
• The Copilot app for consumers. It can't add MCP servers of your own.

Microsoft's guide: Connect your agent to an existing MCP server

LangdockCopy Anchor Link

1. In Langdock, open Plugins in the sidebar.
2. Click Create. If a menu opens, choose Integration, then Connect remote MCP.
3. Paste the address above as the Server URL.
4. Choose OAuth 2.0 (Dynamic Client Registration) as the authentication.
5. Click Create and connect.
6. Sign in to Sleak.
7. Click List Server Features.
8. Select the tools.
9. Click Save.

You need the permission Create integrations in Langdock. Without it, a Langdock admin adds Sleak for you.

Langdock's guide: MCP integrations

Allow access in SleakCopy Anchor Link

The assistant opens Sleak in your browser the first time it reaches Sleak.

1. Sign in as usual. A workspace that needs another sign-in shows the button Sign in with …, for example with Microsoft.
2. Choose the Workspace the assistant may reach.
3. Choose the Access: Read or Edit.
4. Click Allow.

A workspace with MCP access switched off shows MCP access is off and can't be chosen. Deny connects nothing.

What the assistant can doCopy Anchor Link

• It sees and changes only what your role allows. See Roles.
• Every change comes with a link where you check the result in Sleak.
• When a persona is published without a banner, Sleak adds one. When a program is activated without a cover, Sleak adds one.
• The assistant shows analytics and program progress without names if your workspace anonymises names in the analytics. See Compliance.
• The assistant shows the leaderboard without names if names are anonymous in Sleak. See Compliance.

Where the data goesCopy Anchor Link

Your contract with the AI provider governs what happens to the data there. Sleak's terms don't apply there. Check before you connect whether your rules allow this provider for data from Sleak. Switch MCP access off if they don't.

DisconnectCopy Anchor Link

1. Open Settings → Account → Connected apps.
2. Click Disconnect next to the app.
3. Confirm the disconnection.

The app loses access at once. The next time it connects, Sleak asks for the workspace and access again.

Switch MCP access off for the workspaceCopy Anchor Link

1. Open Settings → Workspace → MCP & API.
2. Switch MCP access off.
3. Confirm the change.

Every connected app of the workspace loses access at once, and nobody can connect a new one. MCP access is on by default. Below the switch you see every connected app with the number of people, and disconnect an app for everyone.

Good to knowCopy Anchor Link

• A connected app loses access at once when its person leaves the workspace.
• A new role applies at once to the person's connected apps too.
• A connection never reaches more than one workspace. For a second workspace, connect the assistant a second time.

Related articlesCopy Anchor Link

• MCP & API
• Compliance
• Roles