Agent-ready websites

Give agents a safe way to understand and improve a Flax site.

Use the standard MCP endpoint, site-scoped discovery, and OAuth consent to let an agent read a site and prepare reviewable drafts. The owner stays in control of every change.

Open agent config Read the connection guide

Site-scoped by default

When a user names a site, start at that exact origin and follow its advertised MCP endpoint.

OAuth in the owner’s browser

Agents never need a password, magic code, or pasted access token.

Draft before publish

Changes are validated and previewed for the owner before deployment.

Start here

One canonical configuration for every client

Point an MCP client at the account endpoint for account-level work. For a named website, inspect that site’s /.well-known/mcp.json first.

Agent configurationDiscovery, schemas, MCP, preview, and support links.Hosted MCP endpointThe OAuth-capable account-level MCP server.Model recipesSchema-aware model patch patterns for Flax tooling.Prompt recipesCopy-ready prompts for reviews, drafts, and insights.

Quick start

Connect with MCP

The client owns the OAuth redirect, state, PKCE challenge, and token storage. Flax only receives the resulting authorized MCP request.

hermes mcp add flax --url https://agents.flaxsites.com/mcp --auth oauth
hermes mcp login flax

Install the Hermes profile

Client distributions and hosted connection

Install Flax for your agent

Install a Flax distribution for Codex or Hermes from GitHub, or connect another MCP-compatible client directly to the hosted endpoint.

Codex pluginInstall the Flax plugin for OpenAI Codex from GitHub.Hermes profileInstall the Flax profile for Hermes from GitHub.Hosted MCP connectionConnect any compatible client to the OAuth-capable endpoint.

Prompt recipes

Start with a good brief

Open the machine-readable recipes

Review a site

Review my Flax site at https://example.com. Read the current model and model hash, then identify the three highest-impact improvements. Do not change anything yet.

Prepare a focused update

For my Flax site at https://example.com, propose a focused update to the homepage headline using the existing brand voice. Read the current model first, explain the exact changes, validate them, and create a preview draft only after I confirm. Never publish.

Review performance

Review growth opportunities for my Flax site at https://example.com. Use the available aggregate performance data and the site model. Recommend the next three experiments; do not make changes yet.

Replace the example URL with the user’s site. Ask for confirmation before any draft, and never ask for credentials in chat.