Connect an AI assistant

Let Claude, ChatGPT, Gemini or any MCP client work inside a SoftSolz workspace with OAuth.

SoftSolz hosts a remote MCP server at https://app.softsolz.uk/mcp. Add that address to an AI assistant, sign in, choose a workspace and tick what the assistant may do. From then on the assistant writes the content with its own model and credits, and calls SoftSolz to create the form, post the article, raise the invoice or read the submissions. No key to copy, no server to run.

Before you start

• Your role needs the Connected apps permission (admins and managers have it by default).
• Install the services you want the assistant to use. Scopes for a service that is not installed stay locked on the consent screen.
• Start with your Sandbox workspace. It has the same services and its own data, so an over-eager prompt can never touch live records.

The address

https://app.softsolz.uk/mcp

The server speaks MCP over Streamable HTTP and advertises OAuth discovery at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/mcp. Clients register themselves with dynamic client registration and use authorization code with PKCE. You never handle a client id or secret by hand.

Claude

In Claude on the web or the desktop app open Settings → Connectors, choose Add custom connector, paste the address and follow the sign-in. Organisation admins can add it once for everyone. In Claude Code:

claude mcp add --transport http softsolz https://app.softsolz.uk/mcp

ChatGPT

Open Settings → Connectors (developer mode may need to be switched on under Advanced), create a connector with the address above, and complete the sign-in. The tools then appear when the connector is enabled in a conversation.

Gemini and other MCP clients

Any client that supports remote MCP servers with OAuth works the same way. Gemini CLI, Cursor and VS Code take a config entry pointing at the address:

{
  "mcpServers": {
    "softsolz": {
      "type": "http",
      "url": "https://app.softsolz.uk/mcp"
    }
  }
}

A server-side integration that already holds an API key can skip OAuth and send the key as a Bearer token to the same address. Test keys reach the sandbox workspace, exactly as on the REST API.

What happens when you connect

1. The assistant opens the SoftSolz consent screen. Sign in if you are not already.
2. Pick the workspace (live or sandbox). The screen names the app and where it will send you back.
3. Tick the permissions. Read scopes are preselected; anything that can change data is marked. You can only grant what your own role holds.
4. Allow. The assistant exchanges a one-time code for an access token that lives an hour and a refresh token that rotates on every use. A reused refresh token revokes the whole connection.

Managing and revoking

Developers → Connected AI apps lists every connection in the workspace: which app, who connected it, which scopes, and when it was last used. Disconnect cuts access immediately; the assistant has to go through consent again to come back. Admins are notified in-app and by email when an app is connected or disconnected, and every action the assistant takes lands in the audit log with the member who connected it.

Errors you may see