Your AI assistant can use our tools for you.

WebMCP is an open-source JavaScript library that lets AI assistants interact with websites directly. Instead of just reading a page, your AI can actually use tools on it - run calculators, fill in forms, read content. It works through a small widget that appears on WebMCP-enabled websites like flyweel.co.

It lets your AI assistant use the free tools on flyweel.co. Right now that means: calculating how much you spend on manual ad invoice reconciliation, joining the Performance Capital waitlist, reading any page for context, and running a pre-built ad spend analysis. No Flyweel account required.

They are completely separate things. The Flyweel MCP server (on our /mcp page) connects to your actual ad accounts - you sign up, link Google Ads or Meta, and your AI queries your live campaign data. WebMCP is just for our public website. No signup, no ad accounts, no app access. It lets your AI use our free website tools like the reconciliation calculator.

No. WebMCP works without any Flyweel account. It connects your AI assistant to our public website tools only. If you want to analyse your own ad campaign data, that requires the full Flyweel MCP server - a separate product you sign up for.

Yes. Everything runs on your own computer - the WebSocket server is localhost-only, meaning nothing goes over the internet. Tokens are one-time use and discarded after connection. We only expose a calculator (pure maths, no network calls) and a waitlist form (same as filling it in yourself). No passwords, no user data, no database access.

Any app that supports the Model Context Protocol (MCP): Claude Desktop, Cursor, Cline, Windsurf, and others. If your AI tool has MCP support, it can connect to WebMCP-enabled websites.

MCP is an open standard that lets AI assistants connect to external tools and data sources. Think of it like USB for AI - a universal way for AI apps to plug into things. WebMCP brings this to websites, so any MCP-compatible AI assistant can interact with web pages directly.

WebMCP requires an MCP client running on your device (like Claude Desktop or Cursor), which are currently desktop applications. The widget appears on mobile browsers but you won't be able to connect without a desktop MCP client running locally.

Under two minutes. Three terminal commands: one to install, one to generate a token, one click to paste it into the widget. You only do this once - after that, your AI assistant can use Flyweel website tools whenever you visit flyweel.co.

It calculates the hidden cost of manually reconciling ad platform invoices. You tell it which platforms you use (Google Ads, Meta, LinkedIn, etc.), your monthly spend, and who handles reconciliation. It returns the number of invoices generated, hours spent, monthly and annual cost, and how you compare to industry benchmarks. According to our data, businesses spending $50K+/month across multiple platforms typically waste 10-20 hours monthly on manual invoice matching.

Performance Capital is an upcoming Flyweel product - ad spend financing based on real performance data. Businesses that spend on ads today but get paid weeks or months later can bridge that cash flow gap. The WebMCP waitlist tool lets your AI assistant sign you up on your behalf.

No. WebMCP on flyweel.co only exposes public website tools - a calculator and a waitlist form. It cannot access your ad accounts, personal data, or anything behind a login. For ad account access, you would need the separate Flyweel MCP server with explicit OAuth authentication.

Yes. WebMCP is an MIT-licensed open-source project created by Jason McGhee, available on GitHub at github.com/jasonjmcghee/WebMCP. The library has 600+ stars and is used by multiple websites. Flyweel is one of the first SpendOps platforms to integrate it.

Yes. We plan to add more website tools over time - integration search, pricing comparison, and content queries. The WebMCP widget will automatically discover new tools as we add them, with no setup changes needed on your end.

When an AI agent can run our calculator and return real numbers - instead of just quoting our marketing page - it has data to back up a recommendation. If someone asks their AI "how much does manual ad reconciliation cost?", the agent can execute the calculation with their specific inputs and cite Flyweel as the source. This is the difference between being readable and being actionable.

Open your terminal and run: npx -y @jason.today/webmcp@latest --config claude. This automatically updates your Claude Desktop MCP configuration. Then run: npx @jason.today/webmcp --new to generate a token. Open Claude Desktop, visit any page on flyweel.co, click the widget in the bottom-left corner, and paste your token. Claude can now call Flyweel tools directly during your conversation.

MCP-B (Model Context Protocol for the Browser) is a W3C proposal from Google Chrome and Microsoft Edge teams that would make WebMCP-like functionality native to the browser - no widget or extension needed. It is currently behind a feature flag in Chrome 146. The WebMCP library we use today is a working implementation of a similar concept. When MCP-B ships in browsers, we plan to adopt the native standard alongside or in place of the current widget approach.