Agents and MCP
Agent access
Choose remote MCP, browser-native WebMCP, or the REST API to give an agent read-only access to published lawn-care content.
Choose an interface
Lawn Care Center exposes one published content catalog through three interfaces.
- Remote MCP is the best default for an MCP-compatible assistant, IDE, or agent runtime.
- WebMCP lets a supported browser agent use tools while it is on lawncare.center.
- REST API works for applications that want direct JSON responses.
All three interfaces search the same general articles, state guides, and city guides. Drafts are excluded.
What an agent can do
An agent can search with text and structured filters, retrieve one full document, and inspect the taxonomy of topics, tags, seasons, content kinds, states, and cities.
Every operation is read-only. The interfaces cannot publish content, change the site, access user data, or open arbitrary URLs.
Retrieval approach
Search uses deterministic weighted lexical ranking over titles, keywords, topics, normalized tags, summaries, headings, and article text. Structured filters run before ranking.
The current catalog does not use vector RAG. The corpus is small and well labeled. We will add hybrid retrieval only if real queries show repeatable semantic misses that simpler ranking changes cannot fix.
Start connecting
Use Connect with MCP for an MCP client. Use the API overview when you need HTTP endpoints or an OpenAPI document.