Work with InfiniteWatch through your AI browser.

Start here with your browser assistant

A compatible browser assistant can discover InfiniteWatch tools on this website or on the app's sign-in page. Ask it to use a tool; when access is needed, it can offer you the MCP's authorization link.

1. Open this website or the app in a browser with WebMCP support.
2. Ask your assistant to use an InfiniteWatch tool. Protected tools provide an authorization link.
3. Follow that link in the same browser tab. Sign in and choose the organization you want to authorize.
4. Return to the originating page and continue with your assistant. It can rediscover the tools and retry your request.

Your existing sign-in can be reused during authorization. There is no extra connection button in the dashboard, and operations are never automatically replayed after sign-in.

The same MCP, through your website or a connector

Explore insights, find supporting examples and ask questions about your organization through the InfiniteWatch MCP. The website SDK reads its tool catalog and sends requests to the same server used by remote MCP connectors.

The MCP's OAuth authorizes tool use for the organization you choose. You can complete that authorization from this website without opening a dashboard first. Website and app connections are separate; ask your assistant to disconnect a connection when you no longer need it.

For a remote MCP connection, use https://mcp.infinitewatch.ai/mcp with the Streamable HTTP transport. The server provides its current tool catalog; protected operations require OAuth authorization.

The machine-readable connection details describe this endpoint and the website SDK. This descriptor is a discovery convention, not a WebMCP standard or an authorization grant.

Bring your existing MCP to your website

Add the InfiniteWatch SDK script and configure your MCP URL. The same script can run across your pages and use the catalog your MCP exposes. Your existing MCP remains the source of tools and business logic.

• Public MCPs: use tools without an OAuth sign-in when the server allows public access.
• Protected MCPs: reuse the server's OAuth flow when a tool needs access. The assistant offers the user an authorization link; the script adds no connection controls.

The SDK uses MCP Streamable HTTP. Your website and MCP must allow the browser connection, including the appropriate CORS and content security settings. Tool use also requires a browser and agent with WebMCP support.

Finding the page and using its tools

An assistant may find this explanation through web search. A browser with WebMCP support can also discover the tools registered here. Ordinary web search or page fetching does not run the SDK, attach an MCP connector or start OAuth. Website tools require a compatible browser and agent, with the relevant page open and any required authorization completed.

Support depends on the specific ChatGPT, Claude or other agent environment you use. A direct MCP connector is a separate setup that can use the same server without an open website page. Publishing tools does not guarantee that an assistant will discover or recommend your business.