MCP
Connect Claude, ChatGPT or Cursor to your workspace via the Model Context Protocol and manage authorized clients
SimpliServ provides an MCP server (Model Context Protocol). With it you connect AI clients like Claude, ChatGPT or Cursor directly to your workspace – the assistants can then read data and (after confirmation) perform actions.
Connect a client
Claude
Add a custom connector, sign in via OAuth and set tool permissions – with screenshots.
ChatGPT
Enable developer mode, create the plugin and sign in via OAuth – with screenshots.
For Cursor and other MCP clients the server URL is all you need – see Other clients.
You'll find the MCP connector in the connector hub under Administration → Organisation → Connectors in the Developers category. Sign-in runs via OAuth – no API key is needed.
How the connection works
Your MCP server has a fixed address – identical for every workspace:
https://api.simpliserv.app/api/v1/mcpThe client signs in via OAuth 2.1, you confirm the consent screen (/oauth/authorize) once with your workspace user, and after that the tools are available in the client.
A connected client inherits your user's roles and permissions – it sees and may do only what you see and may do. Every write operation is confirmed before execution, and you can revoke any client at any time (see below).
If you belong to several workspaces, a connected client always works with your default workspace – switching as you would in the web interface is not possible. Access to other workspaces is ruled out: your membership is checked on every request.
Other clients
Any MCP-capable client works with the same URL and OAuth. In Cursor, for example, go to Settings → MCP → Add new MCP server, enter the URL, choose OAuth as the authentication and confirm the consent screen.
Clients without OAuth support (e.g. Cline, Continue) use the mcp-remote bridge:
"simpliserv": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.simpliserv.app/api/v1/mcp"]
}Manage authorized clients
In the MCP connector's Configuration tab, the Authorized OAuth clients card lists all clients you've approved – with Client, first authorized, last used and expiry date.
Via Revoke you disconnect a client immediately: active sessions are ended and all issued access tokens invalidated. As long as no client is connected yet, the card shows "No OAuth clients authorized yet."
Revoke clients you no longer use or don't recognize. Since a client works with your permissions, revoking is the quickest way to end access.
Related topics
Manage connectors
The connector hub: connect, configure and disconnect integrations.
API access & external apps
Issue API keys and connect AI clients via the MCP connector over OAuth.
API
The full REST API reference from the OpenAPI schema.
Users & roles
Control the permissions a connected client inherits.
How is this guide?