Using This Website with AI Agents

This website is built to be usable by AI agents, not just people. It exposes a small set of WebMCP tools (Web Model Context Protocol) that let an AI assistant understand each page and take safe, public actions — like searching the blog, summarizing an article, or opening the join flow. This page explains what's available and how to connect it from a browser or from Claude Desktop.

First, the key distinction

There are two related but different things, and it helps to know which is which:

• WebMCP (what this site uses): tools registered inside the web page for an AI agent that is looking at the page. It's an emerging web standard — the W3C Web Machine Learning CG explainer and Chrome's WebMCP docs define a navigator.modelContext / document.modelContext API. The tools live at the page; you need a WebMCP-capable browser (or a bridge) that "sees" the page to call them.
• MCP servers (what Claude Desktop connects to): Claude Desktop and Claude don't browse the web themselves — they connect to MCP servers listed in a config file. So to use this site's tools from Claude Desktop, you either run a bridge that exposes the page's WebMCP tools to Claude as an MCP server, or you run a dedicated MCP server for the same capabilities.

What this site exposes

The stable tools are also published, machine-readable, at /.well-known/webmcp. Read-only tools never change anything; the rest perform a public action (e.g., navigation).

• getPageContext (Every page, read-only) — A short summary of the current page: title, purpose, and primary action.
• openJoinFlow (Every page) — Opens the membership signup/checkout (Join Tech Savvy — $97/mo).
• getMembershipInfo (Home, read-only) — What the $97/month membership includes.
• getFaqAnswers (Home, read-only) — Answers to common questions about membership, Ambrose AI, pricing, and eligibility.
• searchPosts (Blog index, read-only) — Search blog posts by keyword or tag. Input: { query }.
• getArticleSummary (Blog post, read-only) — A summary of the current article.
• getArticleFaqs (Blog post, read-only) — The FAQs from the current article.
• getAvailableTools (This page, read-only) — Lists the WebMCP tools this site exposes.

Option A — A WebMCP-capable browser (native, no setup)

The simplest path. This site registers its tools with the native WebMCP API exactly as the standard describes — a tool descriptor with a name, description, JSON-Schema inputs, and an execute() handler that returns a content array, scoped to an AbortController and torn down on page hide. A browser that implements WebMCP can then discover and call those tools while you're on the page:

• Microsoft Edge 147+ — native support, on by default.
• Chrome 149+ — via the WebMCP origin trial (production), or locally by enabling chrome://flags/#enable-webmcp-testing.

Then just ask the browser's built-in AI assistant to, for example, "search the blog for Medicare AI" or "summarize this article" — it calls the tools directly. (Tools run visibly in the tab and are gated by the tools Permissions-Policy; nothing runs headless.)

Option B — Claude Desktop, via the webmcp.dev bridge

Claude Desktop connects to MCP servers, not to a web page — so to reach this site's live in-page tools you run the open-source webmcp.dev bridge (repo), a local MCP server that relays a browser tab's WebMCP tools to any MCP client.

1. In Claude Desktop, open Settings → Developer → Edit Config (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS) and add:

{
  "mcpServers": {
    "webmcp": {
      "command": "npx",
      "args": ["-y", "@jason.today/webmcp@latest", "--mcp"]
    }
  }
}

2. Restart Claude Desktop. The bridge generates a WebMCP token.
3. Open this site with the webmcp.dev widget enabled, and paste the token into the widget. Claude Desktop can now call this page's tools — searchPosts, getArticleSummary, getFaqAnswers, and the rest.

Note: this path needs the small webmcp.dev widget loaded on the site (it provides window.mcp, which our tools already register to). It's off by default — ask us to enable it.

Option C — A dedicated remote MCP server (no browser needed)

The most robust path for headless or programmatic use: a hosted MCP server (Streamable HTTP) that mirrors these capabilities from the site's content and sitemap. You add its URL as a Custom Connector in claude.ai or Claude Desktop and the tools appear directly — no browser tab, no bridge, no token. This is what makes the tools show up in Claude's connector list. We can stand one up on Cloudflare on request — get in touch.

Questions?

Want the starter MCP server, or help connecting this to your own agent? Email admin@techsavvyinsurance.com.