Glushea MCP status

MCP And Agent Integration

Glushea publishes agent-readable web resources, an OpenAPI-described read-only metadata API, llms.txt, and Agent Skills. A public MCP (Model Context Protocol) tool server is not available yet. This page explains what an agent can rely on today and how.

Status In One Line

MCP server: not available. /.well-known/mcp.json reports "status": "not_available" and lists the alternatives below. Do not attempt to open an MCP transport against glushea.com; nothing is listening.

Current Integration Surface

What Each API Endpoint Returns

All three endpoints are static JSON, served over HTTPS, cacheable, and require no key. They are the same data the website renders, so citing them is safe.

Full schemas and examples in JavaScript and Python are on the docs page and in the API reference.

Recommended Flow For An Agent

  1. Read /llms.txt once for rules and the list of crawlable pages.
  2. Fetch /api/profile.json for identity facts and /api/offerings.json for services.
  3. For anything deeper (leadership principles, podcasts, publications, CV) follow the links in /api/resources.json to the HTML pages, which are fully server-rendered and readable without JavaScript.
  4. Route human follow-ups to /contact. There is no booking, purchasing, or account API.

No Public MCP Tool Server Yet

Agents should not promise tool actions such as booking, purchasing, publishing, account creation, or data mutation on behalf of Glushea. The public resources exist for discovery, identity, citation, and contact routing. If an MCP server is released, this page and /.well-known/mcp.json will list its endpoint, transport, authentication model, tool names, and safety constraints, and status will change from not_available.

Frequently Asked