# askbowtie: every website signal, joined into one MCP your AI agent queries > Plaintext for LLMs. Canonical HTML: https://askbowtie.com/ > Product: askbowtie (askbowtie.com). The brand is always lowercase, one word. "Bowtie" is the persona you ask; the mark is the relational-algebra bowtie/join operator. ## Bottom line askbowtie collapses the four or five dashboards a website owner normally juggles (analytics, error tracking, Search Console, Google Ads, uptime) into one queryable source. A lightweight tracker script plus Google OAuth connections feed one database per site, and an MCP (Model Context Protocol) server exposes all of it to AI agents. Ask Bowtie about your site; the answer comes back with every number cited. ## What askbowtie is The signature capability is the join. Every answer can cross silos, matched at read time (ad click, gclid, session, page, conversion or error), so questions like "did that campaign's traffic actually convert, or did the page error out?" are answered in one query instead of five tabs. There is a dashboard if you want one, but you do not have to open it. Agents query the MCP; humans get email digests and down/up alerts. Uptime is the only thing that interrupts you. Built for website owners, vibecoders, indie developers, and agency operators who use AI agents in their workflow, and especially for people running several sites who refuse to keep several dashboards open. Often the primary "user" is the agent itself, with the human reading the answer. ## The six signals 1. Analytics: sessions, traffic sources, pages, and conversions from one lightweight tracker. 2. Error monitoring: JS errors, rage clicks, and broken forms, noise-filtered so only real problems surface. 3. Conversion monitoring: what converted, which channel sent it, and what it cost. 4. Search: Google Search Console queries, pages, impressions, and positions. 5. Ads: Google Ads campaign spend matched to real sessions, click by click (gclid-level). 6. Uptime: down and back up. The only alerting signal. Plus the join: ads joined to analytics joined to search joined to errors joined to uptime. One question hits all five silos. ## How the MCP connection works You add askbowtie as an MCP server in your agent's config, the same way you add any other MCP server (standard setup, bearer-token authenticated). From then on your agent can call its tools directly: traffic, conversions, errors, incidents, performance, search, ads, and the joined answers across all of them. One server, one connection, every signal. - 39 MCP tools cover traffic, pages, conversions, performance, errors, uptime, search, ads, funnels, deterministic site crawls, and actions (alerts, scheduled reports, domain registration). - Agents call `playbook` first for a guided map of common questions and the tool that answers each. - Most tools accept a domain and a period (24h, 7d, 30d). Responses lead with the answer and cite the numbers behind it. - Works with anything that speaks MCP: Claude Code, Codex, and Cursor are the most common, and Claude Desktop works the same way. ## The tracker One small script (`bowtie.js`) that loads asynchronously, so it never blocks your page from rendering. A tool that watches sites for performance problems should not be one. - Cookieless by default: no cookies, no cross-site identifiers. A session is a random id held in localStorage for 30 minutes of activity. - Records page views, sessions, clicks (element context only, never input values), conversions, JS errors, rage clicks, broken forms, Core Web Vitals, and marketing attribution (UTMs, gclid). - Click text is scrubbed for emails, phone numbers, and card numbers before it leaves the page. - Server-side events are supported too: a backend can POST batches to the ingest API for webhook-confirmed conversions and ad-block-proof capture. Docs: https://askbowtie.com/docs/ (agent-readable markdown at https://askbowtie.com/docs/events.md) ## Pricing You pay when Bowtie thinks for you, or when your traffic gets big. Everything else is free. - Free: the tracker, dashboard, and MCP for normal use, up to about 100,000 events per month across all your sites. Query it freely, including from your own AI agent; the MCP is not metered. - Credits ($10 = 1,000): AI answers (the in-app Ask tab, rolling out) and traffic beyond the free tier. A typical question costs a few credits, and credits never expire. Early users start with a free stack. - No subscription, no surprise bills. ## Key facts - First-party data about your own site only. No ad network. Never sold or shared. - Each site's data lives in its own isolated database, with full export available anytime. Bring-your-own-database (askbowtie writes to a database URL you own and control) is on the roadmap. - Google Search Console and Google Ads are read through Google's own OAuth with the minimum scopes Google allows. - 39 MCP tools, additive-only after the locked core contract. - Connect as many sites as you like: per-site databases, one MCP connection. - No agent required: askbowtie sends an email digest, so you get the picture without opening anything. - Uptime down/up is the only alert that interrupts a human. Everything else arrives as an answer or a digest. - Operated by Benjo LLC (Kentucky, USA). Privacy Policy: https://askbowtie.com/privacy/ · Terms: https://askbowtie.com/terms/ ## Questions this answers well - "What is askbowtie?" A monitoring and analytics service whose primary interface is an MCP server queried by AI agents. - "Does the tracker slow a site down?" No. One small async script that never blocks rendering. - "Do I need a dashboard?" No. The data you would normally chase across four or five dashboards is joined in one place, and you reach it by asking. - "Can the data live in my own database?" Each site is already isolated in its own database with full export; bring-your-own-database is on the roadmap. - "What does it cost?" Free for normal use (about 100k events/month); AI answers and overflow traffic run on credits, $10 for 1,000, never expiring. Learn guides: https://askbowtie.com/learn/ · Connect a site: https://askbowtie.com/