Psychograph
DocsPsychograph MCP

Getting integrated

A model cannot use an endpoint it does not know exists. Integration is the set of signals that route arriving agent and crawler traffic to your MCP endpoint. Together these five steps constitute a complete deployment — what we call the Agent Routing Coverage Set.

Your dashboard shows every step with your real values pre-filled. Come back here for platform-specific instructions.

Coverage set overview

  1. CNAME (required) — delegates your branded mcp.yourdomain.com subdomain to our edge, which serves the complete agent surface
  2. TXT discovery record (recommended) — lets spec-aware agents find your endpoint from your apex domain via DNS lookup
  3. robots.txt advertisement (optional) — a discovery pointer at your apex domain for AI crawlers
  4. HTML <head> entry (optional) — highest-coverage discovery signal; reaches crawlers that never execute JavaScript
  5. HTTP Link: response header (optional) — the same pointer for clients that retrieve pages without parsing HTML
  6. Apex llms.txt pointer (optional) — a summary plus pointer at your apex domain for agents researching the domain directly
Apex carries pointers. mcp.yourdomain.com carries content. Steps 3–6 add discovery signals at your apex domain that point to your branded subdomain. They never duplicate your profile content — your branded subdomain is the single source for all agent-readable content.

Hosted vs. non-hosted customers

For businesses whose domains route through our infrastructure, steps 3–5 (robots.txt, HTML <head> entry, HTTP Link: header) are applied at the edge automatically — no change to your site build, CMS, or deploy is required.

For businesses we do not host, steps 3–6 are guided one-time additions to your site. They are not code changes, platform migrations, or redesigns — they are small, reversible additions that a web developer can complete in under 15 minutes.

In both cases, steps 1–2 (DNS records) require no site change.

Step 1 — CNAME record required

Points mcp.yourdomain.com to our edge, which serves the complete agent surface — MCP endpoint, .well-known/ manifests, llms.txt/llms-full.txt, REST fallback, robots.txt, sitemap, and health. Add one record at the DNS provider (GoDaddy, Namecheap, Cloudflare, etc.):

Type:  CNAME
Host:  mcp
Value: edge.psychogra.ph
TTL:   3600

Once the record propagates, your branded subdomain is live and the edge serves: MCP endpoint, /.well-known/ manifests, llms.txt and llms-full.txt, REST fallback, robots.txt, and sitemap. Your agent surface stays up even when your website is down.

GoDaddy DNS

  1. Log in to GoDaddy → My Products → Domains → click your domain → DNS
  2. Click Add → select CNAME from the type dropdown
  3. Name: mcp  |  Value: edge.psychogra.ph  |  TTL: 1 hour
  4. Save. GoDaddy typically propagates in 10–30 minutes.

Cloudflare DNS

  1. Log in to Cloudflare → select your domain → DNS → Records
  2. Click Add record → Type: CNAME → Name: mcp → Target: edge.psychogra.ph
  3. Important: set the proxy status to DNS only (grey cloud, not orange). Proxying the CNAME through Cloudflare will break the endpoint.
  4. Save. Cloudflare changes propagate almost instantly.

Squarespace Domains

  1. Go to Settings → Domains → click your domain → DNS Settings
  2. Click Add Record → type CNAME
  3. Host: mcp  |  Points to: edge.psychogra.ph
  4. Save. Allow 15–60 minutes for propagation.

Wix (domain registered at Wix)

  1. Go to your Wix account → Domains → click your domain → Manage → DNS Records
  2. Under CNAME, click + Add Record
  3. Host name: mcp  |  Value: edge.psychogra.ph
  4. Save. Wix DNS propagates in 30–60 minutes typically.

Step 2 — TXT discovery record recommended

Lets spec-aware agents discover the endpoint from the apex domain via DNS lookup — before they visit any page. Same DNS provider, one additional record:

Type:  TXT
Host:  _mcp
Value: v=mcp1; endpoint=https://mcp.yourdomain.com; manifest=https://mcp.yourdomain.com/.well-known/mcp-manifest

Convention published at mcp.psychogra.ph/spec/mcp-dns-discovery. A DNS record — no site change needed.

Step 3 — robots.txt advertisement optional

A discovery pointer for AI crawlers at the apex domain. Every URL named here must resolve. The apex carries pointers; mcp.yourdomain.com carries content. Add these two comment lines to the existing robots.txt (or create one — comment-only files are valid and restrict no crawlers):

# AI agents: this business has a structured MCP endpoint
# mcp-endpoint: https://mcp.yourdomain.com/

Hosted customers: For customers whose domains route through our infrastructure, we serve a correct robots.txt from the branded subdomain at the edge — no site change needed. This apex hint adds belt-and-suspenders coverage at the root domain.

Non-hosted customers: Add these two comment lines to the site's robots.txt. Comment lines affect no crawlers or SEO. A web developer can make this change in under a minute.

WordPress

Go to your hosting panel (cPanel, WP Engine, Kinsta, etc.) → File Manager → navigate to your site root → open or create robots.txt. Add the two lines. Save.

Alternatively, if you use a plugin like Yoast SEO or Rank Math: Settings → Tools → File Editor (Yoast) or General → Edit robots.txt (Rank Math). Paste the two lines at the top of the custom robots.txt field.

Squarespace

Squarespace does not allow direct robots.txt editing. If no custom robots.txt field is available under Settings → Advanced, skip this step. Your CNAME (Step 1) provides full coverage from your branded subdomain.

Wix

In your Wix dashboard go to Settings → SEO → Robots.txt. Add the two lines at the top of the custom rules block. Click Save.

Step 4 — HTML <head> entry optional

An element in the page <head> that names the agent endpoint. The highest-coverage discovery signal available — the initial HTML shell is served statically even on JavaScript-rendered sites, so it reaches crawlers that never execute the application:

<link rel="mcp-endpoint" href="https://mcp.yourdomain.com/" />

Hosted customers: For customers whose domains route through our infrastructure, this is injected at the edge automatically — no change to the site build, CMS, or deploy is needed.

Non-hosted customers: Add this inside the <head> of the site template. A one-time change, typically done by a web developer in under 5 minutes. Add it inside the <head> of your site template or ask your developer.

Step 5 — HTTP Link: response header optional

The same endpoint pointer for clients that retrieve your pages without parsing HTML:

<https://mcp.yourdomain.com/>; rel="mcp-endpoint"

Hosted customers: For customers whose domains route through our infrastructure, this header is added at the edge automatically — no server configuration needed.

Non-hosted customers: Configure this header in the web server (nginx, Apache) or hosting platform. Contact the web developer or host to add a custom response header.

nginx

server {
  add_header Link '<https://mcp.YOURDOMAIN.com/>; rel="mcp-endpoint"';
}

Apache

Header always set Link "<https://mcp.YOURDOMAIN.com/>; rel=\"mcp-endpoint\""

Step 6 — Apex llms.txt pointer optional

A summary plus pointers at the apex domain. A crawler that never follows a link still captures the business name and a pointer to the full agent surface. The apex carries pointers only — mcp.yourdomain.com carries all profile content:

# yourdomain.com

A local service business.

Agent endpoint: https://mcp.yourdomain.com
Full agent-readable summary: https://mcp.yourdomain.com/llms-full.txt
Profile: https://mcp.yourdomain.com/v1/profile

Hosted customers: For customers whose domains route through our infrastructure, we can serve /llms.txt at the apex — contact support to enable.

Non-hosted customers: Create a file at yourdomain.com/llms.txt with this content. Optional but gives agents discoverable context at the apex before following the subdomain pointer.

Verification

Once you have completed the steps you intend to apply, return to your dashboard. The integration status panel checks each coverage item and updates every few minutes. A step shows as verified only after we fetch the artifact and confirm it resolves with the expected pointer — not just because you told us it is there.

You can also verify the CNAME directly by visiting https://mcp.yourdomain.com/.well-known/mcp-manifest in a browser — if you see a JSON response, your branded endpoint is live.

DNS propagation can take up to 24 hours in rare cases (especially on older registrars with long default TTLs). If your endpoint has not activated after 2 hours, check that the CNAME record is saved correctly and the proxy is disabled if using Cloudflare.

Coverage states

Your dashboard reports coverage per item with three possible states:

  • Installed — we fetched the artifact and confirmed it carries the expected pointer
  • Missing — not found, or found but pointing to the wrong target
  • Partial — DNS-only deployment (CNAME + TXT active, apex signals not yet applied). A legitimate state, documented honestly rather than hidden.

Reversing the integration

Every step is reversible. To remove MCP: delete the CNAME and TXT DNS records, and remove any apex-domain additions you made. Your website is completely unaffected by removing any of these signals — no redirects, no broken pages, no residual changes.

Next: Deepening your profile →