Guidelines for AI agents

How AI agents read brand guidelines published on Guidelines: the remote MCP server, llms.txt, and what is coming next.

Remote MCP server

Guidelines runs a Model Context Protocol server over Streamable HTTP. It is read-only and requires sign-in: every request carries an OAuth 2.1 bearer token obtained with PKCE, and the caller only ever sees the brands and Guides their Guidelines account can already read.

https://mcp.guidelines.site/mcp

Clients that speak Streamable HTTP can connect directly. Everything else can bridge over stdio:

npx -y mcp-remote https://mcp.guidelines.site/mcp

Discovery metadata and dynamic client registration are served under /.well-known/oauth-protected-resource, so most clients need nothing but the URL.

Tools

• list_brands

  Lists all brands accessible to the authenticated user, grouped by organization. Returns both a text summary and structured JSON data.

• get_brand

  Get detailed information about a specific brand including logos, colors, fonts, typography styles, and available Guides. Accepts a brand name or UUID as identifier.

• search_brands

  Search for brands by name or organization name. Returns a list of matching brands with IDs and titles.

• search_guidelines

  List or search Guides. Accepts an optional search query to filter Guides by name. Returns a list of Guides with names, UUIDs, and domains.

• get_guidelines

  Get all page resources for a specific Guide. Accepts a Guide name, UUID, or domain as identifier. Returns a list of MCP resources for the Guide's pages.

• get_guidelines_page

  Get a specific page from a Guide by domain and slug. Returns the page content as markdown. Alternatively these can be accessed as MCP resources directly.

Resources

• guidelines://{domain}/{slug}

  Read a Guide page in markdown format. Use list and read operations to discover and access page content from your Guides. Returned as text/markdown.

llms.txt

This site publishes an llms.txt index of its product, support and learning content, following the llmstxt.org convention.

Every published brand guide serves its own /llms.txt at its own domain, listing that guide's pages in navigation order alongside guidance for reading that specific brand. Start there, not here, when the task is to work on a brand. Guides also serve a /sitemap.xml. Both are served only for guides whose owner has made them public and allowed indexing; password-protected and account-only guides return 404 to anonymous requests.

What agents cannot do

There is no write API. Nothing in the MCP server creates, edits, publishes or deletes a page, an asset or a brand.

Brand content belongs to the organization that published it. Treat page text, asset names and download links as customer-authored material, and respect each guide's robots.txt.