Connect an AI assistant

Use Claude, ChatGPT, Gemini or another assistant you already pay for, and let it fill your SoftSolz workspace: draft the blog post, build the form, raise the invoice, read the submissions.

What it does

The assistant keeps using its own model and its own credits. SoftSolz gives it a set of tools, one per action in your services, and it calls them on your behalf. You decide which workspace it may act on and exactly which permissions it holds, and you can cut it off at any time.

This is different from the built-in AI Assistant panel, which runs inside SoftSolz on your plan's AI credits. Connected apps run outside, in the assistant's own app.

Connect an assistant

  1. Open Developers in SoftSolz and copy the address shown in step 1 of the Connected AI apps card. It is https://app.softsolz.uk/mcp.
  2. In the assistant, find where custom connectors (sometimes called MCP servers) are added. In Claude it is Settings → Connectors → Add custom connector; other assistants keep it in their own settings, and some only offer it on certain plans. Paste the address.
  3. The assistant sends you to SoftSolz. Sign in if asked.
  4. Pick the workspace. Your Sandbox is chosen for you, which is the safe choice while you try things out.
  5. Tick the permissions and press Allow access. You are sent back to the assistant, ready to go.

You need the Connected apps permission in the workspace. Owners, admins and managers have it; ask an admin if the screen says your role cannot connect apps.

Choosing permissions

The consent screen lists every service, with its permissions grouped underneath. Only the read permissions the assistant asked for are ticked to start with; everything else starts unticked. Select all and Read only buttons set them in one go. Anything that can change data carries a Can change data badge, so you can see at a glance what you are handing over.

Working with it

Ask in plain words: "Write a 600-word post about spring offers and save it as a draft in SoftSolz", "Create a contact form with name, email and message", "Which invoices are overdue?". The assistant drafts, then calls the matching SoftSolz tool. Anything it creates appears in the workspace straight away for you to review.

Publishing, sending and paying are still deliberate steps. Give the assistant read and create permissions first, and keep the destructive ones for when you trust the setup.

Videos: with the AI Creative Studio permissions, ask "Make a 20 second launch video for this product". The assistant writes the scenes, SoftSolz builds the video in one of its templates with a voice-over and music, and you get a link to watch and download it.

Agencies connect once, to the agency workspace. With Launchpad permissions the assistant can set up clients, edit their websites, add what their chatbot should know and fetch claim links, for every client you manage, without a separate connection per client. It can never reach a client that is not yours. Everything else about running clients lives in the Agency portal.

Sending files

You can ask the assistant to add images, videos, PDFs and Word, PowerPoint or Excel files: "Make a launch image and attach it to a LinkedIn post", "Add this deck to my knowledge base", "Use this photo as the blog cover". It works for Social, Blogs, Website Builder, Knowledge Hub, Tasks and AI Creative Studio product photos.

Every file is checked before it can be used. Programs, SVG images, old .doc/.ppt/.xls files, Office files with macros and PDFs with scripts are refused. A file sent by one connection can only be used by that same connection, in that workspace, for 24 hours.

See and disconnect

Developers → Connected AI apps shows every connection in the workspace: which app, the address it returns to, whether it works on the live workspace or the sandbox, which permissions it holds, who connected it, and when it was last used. The app name is chosen by whoever built the app, so check the return address before you trust a name. Press Disconnect to remove it. Access stops immediately, and the assistant has to go through the consent screen again to come back.

Admins receive an in-app notification and an email whenever an app is connected or disconnected. Every action a connected app takes is written to the audit log against the member who connected it.

Staying safe

Test it step by step

You need an account with an AI assistant that can add custom connectors (MCP servers), for example Claude. Do the whole test in your sandbox, so nothing real changes.

  1. Prepare the sandbox. Switch to your sandbox with the Sandbox switch in the workspace menu. Open Marketplace and install Forms there if it is not installed yet. Services that are not installed in the workspace you pick stay locked on the consent screen.
  2. Check your role. You need the Connected apps permission. Owners, admins and managers have it.
  3. Add the connector. In the assistant, add a custom connector with the address https://app.softsolz.uk/mcp (it is also on the Connected AI apps card in Developers).
  4. Approve it. The assistant opens SoftSolz. Sign in, check the app name and the return address, keep your Sandbox workspace selected, tick View forms and submissions and Manage forms, and press Allow access. You land back in the assistant.
  5. Ask who it is connected to. Ask "Which SoftSolz workspace are you connected to?". It should answer that it is your sandbox.
  6. Make something. Ask "Create a SoftSolz form called Test contact with name, email and message fields". Success: the form appears in Forms in your sandbox.
  7. See the connection. Open Developers and find the Connected AI apps card. The app is listed with Sandbox, the access you gave, your name and a recent Last used time. The workspace audit log shows the form it created.
  8. Disconnect. Press Disconnect on the row and confirm. Ask the assistant to list your forms: it can no longer reach SoftSolz until you connect it again.
  9. For developers. An API key works on the same address, which is a quick way to check what tools a key can see. Create a key in the sandbox under Developers (New API key), then:
    curl -X POST https://app.softsolz.uk/mcp \
      -H "Authorization: Bearer sk_test_your_key" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}}'
    The reply names the workspace, says "environment": "sandbox" and lists the key's scopes. Send "method":"tools/list" instead to see every tool the key can use. See the Connected apps developer guide and the MCP guide.

If something goes wrong

What you seeWhat it means
Your role in this workspace cannot connect apps.Your role lacks the Connected apps permission in the workspace you picked. Ask an admin, or pick another workspace.
A service is greyed out on the consent screenIt is not installed in that workspace, or your own role does not hold that permission. Install it, then connect again.
The assistant says it has no tool for what you askedYou did not tick that permission. Connect again and tick it; the new connection replaces the old one.
Connection refused or Incomplete requestThe assistant sent an address SoftSolz does not accept, for example a return address the app never registered. Go back to the assistant and start the connection again.
Connect this MCP server with OAuth, or send a SoftSolz API key as a Bearer token. (unauthorized)The connection was disconnected or its access ran out. Connect again from the assistant.