Connect MCP
Every client connects to the same URL:- OAuth sign-in for AI assistants and editors. You add the URL, a browser window opens, you sign in to Loice and approve. Nothing to choose, copy or store.
- API key for automations, scripts and your own agents (n8n, Make, a server with no browser). You create a key in the app and send it in a header.
Create an account and start the trial
Do this once, before you connect any client. Every billed tool spends points from your workspace, so a workspace that cannot pay has its billed calls refused (uncharged).1
Create a Loice account
Sign up at app.loice.ai with Continue with Google or a work email
and password. Personal mailboxes (Gmail, Outlook…) are not accepted.
2
Set up your workspace
Answer Tell us about your company — company name and website. The workspace is what a
connection works in and what its calls are billed to.
3
Start the free trial
A new workspace starts with no points. Click Add payment method and start trial under
Settings → Billing — or add a payment method
when your first paid action asks for it. The workspace receives 500 welcome points straight
away for a 14-day trial, and nothing is charged today. Only an Owner or Admin can start the trial. See
Plans and points.
Before you start
- The server is public. Claude and ChatGPT connect from their own cloud, so the URL has to be
reachable from the internet —
https://app.loice.ai/mcpis. - OAuth sign-in uses OAuth 2.1 with PKCE. Clients that identify themselves with a Client ID Metadata Document are shown with their verified domain; others register themselves automatically (dynamic client registration). If a client asks whether to register automatically or use a pre-registered identity, choose register automatically. There is no client ID or secret to enter.
- An API key is created under Settings → API
and sent as
Authorization: Bearer loice_sk_…. Keep it out of files you commit: read it from an environment variable or a secret manager. Never put it in the URL — Loice refuses it there. - Your role decides what it can do. Approving grants every permission your role in that workspace allows; there is nothing to pick. See Workspace and team.
Claude (claude.ai and Claude Desktop)
Custom connectors are available on Free (one connector), Pro, Max, Team and Enterprise plans.1
Add the connector
Open Customize → Connectors, click + Add, choose Add custom connector, name it
If Claude asks how to identify itself to the server, choose Register automatically. Leave
any client ID and secret empty.
Loice, paste the server URL and click Continue.Remote MCP server URL
2
Sign in
Click Connect. Sign in to Loice in the window that opens, and approve.
3
Use it in a chat
In a conversation, click + at the lower left → Connectors and switch Loice on, then
ask for the leads or contacts you need — for example “Find 50 heads of sales at German SaaS
companies with 51–200 employees and save them to a list called DACH Sales”.
On Team and Enterprise plans an Owner adds the connector once under Organization settings →
Connectors (Add, hover Custom, choose Web). Members then open Customize →
Connectors, find Loice marked Custom and click Connect to sign in with their own
account.
ChatGPT
ChatGPT supports OAuth sign-in only.1
Add the server
Open ChatGPT Plugins, click the + button and choose Add custom MCP server. Enter
the name
Loice and a short description. Under Connection, enter the server URL.2
Set authentication
Choose OAuth and leave the client credentials empty — Loice supports dynamic client
registration. Read the risk warning, confirm, and click Create as a plugin.
Connector settings
3
Sign in and use it
Sign in to Loice and approve.
In a new conversation type
@ in the prompt box and select Loice.Account and workspace policies apply to custom MCP servers. If you don’t see Add custom MCP
server, ask a workspace admin to allow it. ChatGPT may ask you to confirm a call before it
runs.
Claude Code
1
Add the server
Terminal
2
Sign in
Start
claude, run /mcp, select loice and follow the browser sign-in.--scope local). Add
--scope user to make it available in every project, or --scope project to share it with your
team through .mcp.json.
Cursor
Servers are configured in~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one
project).
1
Add the server to mcp.json
~/.cursor/mcp.json
2
Enable it and sign in
Open Customize in the sidebar and enable Loice. Sign in to Loice in the browser window
Cursor opens and approve access.
VS Code (GitHub Copilot)
Run MCP: Add Server from the Command Palette and choose HTTP, or write the entry yourself in.vscode/mcp.json (workspace) or in your user configuration (MCP: Open User
Configuration).
1
Add the server
.vscode/mcp.json
2
Start it and sign in
Run MCP: List Servers, pick
loice and choose Start Server. When VS Code prompts you
to sign in, finish the Loice sign-in in the browser.Gemini CLI
Servers are configured in~/.gemini/settings.json. Use httpUrl for a Streamable HTTP server —
a bare url is treated as SSE.
1
Add the server
From the command line:or write the entry yourself:
Terminal
~/.gemini/settings.json
2
Sign in
Start
gemini and run /mcp auth loice. Gemini CLI finds Loice’s sign-in on its own and
registers itself, so no oauth block is needed.MCP Inspector
Use the MCP Inspector to browse and test the tools interactively.1
Start the Inspector
Terminal
2
Choose the transport
Choose Streamable HTTP and enter
https://app.loice.ai/mcp.3
Sign in and connect
Run the OAuth flow from the Inspector’s authentication settings, then connect.
Other clients
Any client that speaks MCP’s Streamable HTTP transport works — n8n, Make, an agent framework or your own code.- OAuth sign-in
- API key
1
Point the client at the server URL
Streamable HTTP
2
Sign in
If the client supports MCP authorization (OAuth 2.1 with PKCE and dynamic client
registration), it offers to sign in. There is no client ID or secret to enter.
mcp-remote.
Disconnect a client
- OAuth sign-in. Every assistant that signed in is listed in the app under MCP → Connected apps. Revoke it to cut it off immediately. Removing the server from the client alone does not revoke its access. A connection also ends when you leave the workspace, when your role no longer allows a permission it holds, or when you change your password.
- API key. A key is listed under Settings → API under its own label. Revoke it there, and every assistant, script or pipeline using it stops working at once.
Troubleshooting
Tools, prices, permissions and errors are described on MCP server.

