Skip to main content
If your tool is not listed, you can still connect it. Onsomble works with any tool that supports the Model Context Protocol (MCP), which is a growing list of chat apps, editors, and terminals. The steps below are the general shape; the pages for Claude, OpenAI, and the others show the exact click-paths for those tools. The connection is one address:

Connect with sign-in

Most tools let you add a remote MCP server and sign in through the browser, so no keys change hands.
1

Open the MCP settings

Find your tool’s connector or MCP settings. It may be called connectors, integrations, tools, or MCP servers.
2

Add a custom server

Add a custom or remote server, paste the address above, and name it Onsomble. If the tool asks for a transport, choose HTTP (sometimes labelled Streamable HTTP).
3

Sign in and approve

When the tool asks for authentication, sign in to Onsomble in the browser that opens and approve access.

Connect with an API key

Some tools, and most scripts, cannot open a browser to sign in. For those, authenticate with an Onsomble API key sent as a header. Create one in Settings → Account → API Keys: see the API overview. Keys start with ons_ and are shown once at creation. Add the server the same way, then set an HTTP header on it:
Keep the key out of anything you commit or share. Store it in an environment variable or your tool’s secret store, not in a file that goes into version control.

Use it

Name Onsomble in your first message and name the Site you mean. A few to start with are on the overview. To make the tool read the results like an analyst, install the Onsomble skills alongside the connection. Onsomble MCP can read results and, with the required permissions, change Clients, Sites, scan configuration and schedules. Starting a Scan uses scan allowance. Review and approve changes and scan runs before your assistant carries them out. In automated setups, keep confirmation enabled for write actions. For background on the protocol itself, see the Model Context Protocol docs.