Connect Your AI Agent to AlchemyLeads

AlchemyLeads is WebMCP-enabled. Connect Claude, Cursor, or any MCP client to this site and your agent can search the blog, pull case studies, and book a strategy call. No screenshots. No guessing. Direct tool calls.

How to Connect in 90 Seconds

  1. Install the WebMCP bridge on your machine: 
    npx -y "@jason.today/webmcp@latest" --config claude

    Replace claude with cursor, cline, or windsurf if you use a different client.

  2. Restart your MCP client.
  3. Ask your AI to generate a WebMCP token, or run npx "@jason.today/webmcp" --new.
  4. Paste the token into the widget at the bottom of this page.
  5. Ask your agent to “list the case studies on AlchemyLeads” or “find the post on agentic RAG.”

Available Tools

search_posts

Search the AlchemyLeads blog by keyword. Returns matching post titles and URLs from the public sitemap.

list_posts

Return every published blog post on alchemyleads.com. Pulled live from the sitemap so the list is always current.

get_post

Fetch the full text of a single blog post by URL. Returns clean prose with HTML stripped.

list_services

List the AlchemyLeads service offerings: No-Retainer SEO, GEO, AEO, Topical Maps, Digital PR, B2B SEO, and the Everysearch™ framework.

get_case_studies

Return structured case study data, including the 3PL eCommerce engagement (8,000+ keywords, 40K to 180K monthly visits, 3x revenue in 12 months).

book_strategy_call

Return the booking URL for an AlchemyLeads strategy call. 45 minutes, no retainer required, your agent can hand the link directly to you.

get_site_info

Structured information about AlchemyLeads: who we serve, what we offer, and how we measure success in the AI search era.

What Is WebMCP?

WebMCP is an emerging standard that lets websites expose structured tools to AI agents. Instead of an agent screenshotting your page and guessing what to click, it reads a list of capabilities and calls them directly. Faster, cheaper, more reliable.

AlchemyLeads implements the open source jasonjmcghee/WebMCP library. Google’s W3C version is in origin trial as of Chrome 149. Both solve the same problem. We support what works today.

Privacy

The token you paste into the widget is one-time use and discarded after registration. No API keys are shared. All tool calls happen client-side through a local WebSocket bridge on your own machine. AlchemyLeads servers see normal HTTP requests, the same as any other visitor.

Questions

If you build something interesting on top of this, we want to hear about it. Reach out.