Connect an AI assistant
Use an AI application that supports Sqquid’s MCP requirements. You need a Sqquid sign-in and access to an Account; you do not need an API key.
If you need Account access, ask an Administrator to add you in Settings > Users.
Server address
Section titled “Server address”https://mcp.sqquid.com/mcpUse the full address, including /mcp, without a trailing slash.
Connect
Section titled “Connect”- Open your AI application’s MCP or connector settings and add a remote MCP server.
- Enter Sqquid as the name and the server address above.
- Start the connection and sign in to Sqquid in the browser.
- Check the AI application name and address on the approval screen.
- Select the Sqquid Account, review the permissions, and select Allow access.
- Return to the AI application.
Each authorization is tied to the Account you select. To use a different Account, authorize again and choose that Account.
Verify the connection
Section titled “Verify the connection”Ask the assistant:
Which Sqquid Account are you connected to?
It should call account_whoami. Check the returned user, Organization, and Account before requesting any changes.
Then try a read-only task:
Check my Sqquid setup and explain the next required step. Do not make changes.
See Common workflows for other requests.
Complete a browser action
Section titled “Complete a browser action”A tool may open a browser page for provider authorization or subscription checkout. Complete that action yourself, then return to the assistant and tell it to continue.
The assistant must resume the same tool with the same arguments and request state. If the request expires, start it again. See Permissions and approvals.
Disconnect
Section titled “Disconnect”Use your AI application’s revocation control when available. Removing a saved connector may only remove its local configuration; it does not confirm that Sqquid authorization ended.
Sqquid does not yet have a screen for managing authorized AI assistants. Contact help@sqquid.com if you need help revoking or confirming access. Do not send access tokens or Connection credentials.