Connected in Minutes: Claude, ChatGPT and Any MCP Client
Point your AI assistant at your Smartico MCP endpoint and sign in with your back-office account, or use an access token for scripts and command-line tools. There is nothing to install.
Three Steps to Connect
- 1Switch it onAsk your account manager to enable MCP for your label and confirm your endpoint. It looks like
https://aichat-api<N>.smartico.ai/mcp. - 2Choose who gets accessAn administrator sets an MCP access profile for each back-office user. New users start with no access.
- 3Connect and askAdd the endpoint to your assistant, sign in with Smartico or use an access token, and ask your first question.
Watch the Setup
A real setup in Claude: add Smartico as a custom connector, paste the MCP link, sign in with Smartico and choose the labels. The Smartico tools are ready at once.
- Add a connector. In Claude: Settings, Connectors, Add.
- Paste the link. Claude finds the Smartico sign-in by itself.
- Sign in. Choose the labels Claude may use, then approve.
- Ready. Every tool asks for your OK before it runs.
Sign In With Smartico
Add the endpoint to your assistant as a connector and choose Sign in with Smartico. A Smartico page opens: log in with your back-office account, choose the labels to grant and approve.
- No token to copy or store.
- Changes are recorded under your own name.
- Works in Claude, ChatGPT, Cursor, Windsurf and Gemini.
- In ChatGPT, add a custom connector under Settings, Apps & Connectors. Some plans need Developer mode for custom connectors.
- Name
- Smartico
- Address
https://aichat-api<N>.smartico.ai/mcp- Authentication
- OAuth
Access Tokens for Scripts and Tools
For tools that cannot sign in, create a named token under MCP, Access tokens: choose its access profile and labels, and copy it. It is shown in full only once.
- Claude Code connects with a single command.
- Cursor and other MCP clients take the token in their MCP configuration.
- Create a token for each tool, integration or teammate, and deactivate any of them at once.
- Treat a token like a password.
claude mcp add --transport http smartico \
https://aichat-api<N>.smartico.ai/mcp \
--header "Authorization: Bearer <token>"Your Own Code
The same endpoint is a standard JSON-RPC 2.0 API, so scripts and integrations can call the tools directly.
- Each request stands alone: there is no session to open first.
- Add the
x-mcp-mode: jsonheader to get the results as JSON. - Changes made with a token are recorded under a dedicated AI/API user.
- If your account uses an IP allowlist, MCP requests follow it. For ChatGPT, add the connector IP addresses that OpenAI publishes.
curl -X POST https://aichat-api<N>.smartico.ai/mcp \
-H "Authorization: Bearer <token>" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "x-mcp-mode: json" \
-d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'FAQ
Your endpoint is https://aichat-api<N>.smartico.ai/mcp, where N is the number of your Smartico environment. Your account manager confirms it when MCP is switched on for your label.
Ask your account manager to enable MCP on your label and confirm your endpoint, then connect your assistant with Sign in with Smartico or an access token. Not a Smartico client yet? Book a demo and we will show it to you live.
Not for assistants that support sign-in, such as Claude and ChatGPT: they use Sign in with Smartico. Tokens are for tools that cannot sign in, such as Claude Code, scripts and integrations.







