Repository navigation
Connect an assistant
Any assistant that connects to a remote MCP server over HTTP with OAuth works with O'So MCP Server. You give it your shop's MCP address, it asks you to sign in to your back office, and an employee approves the connection.
Your shop's MCP address is on the module's configuration page: see Configuration, step 2.
Each link opens the assistant's own documentation, on the page that explains where to paste the address.
| Assistant | Type | Documentation |
|---|---|---|
| Claude (web, desktop, mobile) | Chat | Custom connectors |
| ChatGPT | Chat | Developer mode and MCP apps |
| Le Chat (Mistral) | Chat | Configuring a custom connector |
| Dust | Team chat | Adding an MCP server |
| Claude Code | Command line | Connect Claude Code to tools via MCP |
| Codex (OpenAI) | Command line | Model Context Protocol |
| Gemini CLI (Google) | Command line | MCP servers with Gemini CLI |
| GitHub Copilot CLI | Command line | Adding MCP servers |
| Cursor | Code editor | Model Context Protocol |
| VS Code (GitHub Copilot) | Code editor | Add MCP servers in VS Code |
| Windsurf (Devin Desktop) | Code editor | MCP servers |
| Zed | Code editor | Model Context Protocol |
| n8n Cloud | Automation | MCP Client node |
| n8n self-hosted | Automation | MCP Client node |
| Make | Automation | MCP Client |
If you restricted the return addresses, add your n8n's host name to the list, or the connection is refused:
- In Shop Parameters > MCP server > Access and security, type your n8n's host name (for example
n8n.your-domain.com) in Only allow these return addresses and press Enter. - Click Save.
When the list is empty, every address is accepted and there is nothing to do.
