AdvocateMCP
Connect your agent to verified local SMB AI agents so users can discover shops, ask questions, book services, and complete transactions from one MCP layer.
Overview
com.advocatemcp/advocate is an MCP server for the Grow phase that lets agents discover, query, book, and transact with verified local SMB AI agents over streamable HTTP.
What is this MCP server?
- Discover local businesses through a unified MCP remote endpoint
- Query verified SMB AI agents instead of scraping static listings
- Support booking and transactional flows agent-side
- Streamable HTTP remote at https://api.advocatemcp.com/mcp
- Open GitHub repository (advocatemcp) for integration reference
- MCP registry version 1.0.0 (com.advocatemcp/advocate)
- Remote endpoint https://api.advocatemcp.com/mcp (streamable-http)
- GitHub source at github.com/cameronjmcewan-dev/advocatemcp
Community signal: 1 GitHub stars.
What problem does it solve?
Local commerce features usually mean brittle per-merchant integrations, so your agent cannot reliably help users find and complete actions with real businesses.
Who is it for?
Solo builders running local marketplaces, service marketplaces, or AI concierges who need a single MCP bridge to many SMB agents.
Skip if: Products with no local or transactional component, or teams that only need static business directories without live agent-backed booking.
What do I get? / Deliverables
You register one AdvocateMCP remote so your agent orchestrates discovery, Q&A, booking, and transactions against verified SMB agent endpoints.
- Agent-driven local business discovery results
- Queryable SMB agent responses for hours, services, or inventory-style questions
- Booking or transaction handoffs initiated from MCP tool invocations
Recommended MCP Servers
Journey fit
Local discovery and booking loops matter once you are driving usage and retention for marketplaces, agents, or vertical SaaS—not when you are still sketching wireframes. Lifecycle covers ongoing customer actions—find a business, query inventory or hours, book, and pay—which AdvocateMCP exposes as agent-callable capabilities.
How it compares
SMB agent orchestration MCP, not a maps API wrapper or a single-store Shopify skill.
Common Questions / FAQ
Who is com.advocatemcp/advocate for?
Indie developers building local discovery, booking, or agent-commerce experiences who want one MCP remote instead of bespoke integrations per business.
When should I use com.advocatemcp/advocate?
Use it in grow and operate flows when customers must find verified local businesses, interact with SMB AI agents, book, or transact from your product.
How do I add com.advocatemcp/advocate to my agent?
Add the streamable-http MCP remote https://api.advocatemcp.com/mcp with server name com.advocatemcp/advocate in your agent MCP settings per the registry schema.