Connect with MCP

Server URL

The production MCP endpoint is:

https://lawncare.center/mcp

It uses stateless Streamable HTTP. No API key is required because the tools only return content that is already public.

Client configuration

Clients use different settings screens, but the underlying configuration is:

{
  "mcpServers": {
    "lawn-care-center": {
      "url": "https://lawncare.center/mcp"
    }
  }
}

Restart or reconnect the client after saving the server. Tool discovery should return search_lawn_care, get_lawn_care_content, and list_lawn_care_taxonomy.

A useful first prompt

Ask the connected agent:

Search Lawn Care Center for fall overseeding advice, then open the most relevant article and cite its sources.

The agent should search first, retrieve the selected content path, and preserve the canonical article URL in its answer.

Access and limits

The endpoint is anonymous and read-only. Production currently limits MCP traffic to 60 requests per minute per IP address. A client that sends an Origin header must use an allowed origin. Server-to-server clients generally omit that header.

If tool discovery fails, confirm that the client supports remote Streamable HTTP MCP servers and that it can reach the HTTPS endpoint.