KnitKnot

# Manage customer-domain agent interfaces

Read the desired and effective state of Agent feed, customer-domain MCP, and content indexes, and understand when an endpoint is live.

## At a glance

  1. 1. **Open Interfaces**: Check each customer-domain path and its effective status.
  2. 2. **Choose delivery**: An account admin enables the interfaces the team intends to expose.
  3. 3. **Verify live state**: Read Effective and Why before using the endpoint or WebMCP embed.

If your workspace has Agent publishing, open [Content → Interfaces](https://app.knitknot.ai/content/interfaces). This page controls delivery methods for the published Agent Ledger on your customer domain. It is separate from the [authenticated KnitKnot MCP server](/docs/connect-to-ai-tools/) at `mcp.knitknot.ai`, which gives a signed-in client access to its authorized workspace.

## Choose an interface

| Interface | Customer-domain path | What it serves | | --- | --- | --- | | Agent feed | `/agent-feed` | Signed JSON Feed entries for published Agent versions | | Customer-domain MCP | `/mcp` | Read-only tools over published pages and approved-fact snapshots | | Content indexes | `/llms.txt` and `/llms-full.txt` | Indexes of published Agent versions |

An account admin can switch each interface on or off. Other members can read the status, but cannot change the switches. **Enabled** is the requested state; **Effective** says whether the current delivery configuration actually includes the interface. Check the **Why** column when the status is **Reconciling**, **Off**, or **Unavailable**. A switch being on does not make an endpoint live by itself.

The page names origin ownership, Cloudflare prerequisites, signed artifacts, and the current deployment as conditions that must agree before an interface becomes live. If the Cloudflare connection needs attention, open [Settings → Integrations](/docs/connect-workspace-integrations/). Use the effective status before sharing a customer-domain path with an agent or partner.

## WebMCP

The WebMCP section shows a separate, experimental browser interface. When customer-domain MCP is effective and an embed is available, use **Copy WebMCP embed** to get the pinned module. Browser support is experimental; the module does nothing when `navigator.modelContext` is unavailable. The console currently cannot measure WebMCP use separately from `/mcp` calls. Read its status and reason before placing the embed on a page.

For the underlying published content, [read the Agent Ledger](/docs/read-agent-ledger/) in **Content**. To confirm whether Agent versions are being served with your pages, use [Content → Delivery](/docs/check-agent-delivery/). For site access checks and observed bot requests, use [Content → Access](/docs/check-agent-access/) and [Traffic → Agent activity](/docs/read-ai-traffic/).

If customer-domain MCP is effective, [Traffic → Agent tool calls](/docs/read-agent-tool-calls/) shows estimated use of its read-only tools.

Docs navigation
Docs › Guides

Manage customer-domain agent interfaces

Read the desired and effective state of Agent feed, customer-domain MCP, and content indexes, and understand when an endpoint is live.

Updated

At a glance

  1. Open Interfaces

    Check each customer-domain path and its effective status.

  2. Choose delivery

    An account admin enables the interfaces the team intends to expose.

  3. Verify live state

    Read Effective and Why before using the endpoint or WebMCP embed.

If your workspace has Agent publishing, open Content → Interfaces. This page controls delivery methods for the published Agent Ledger on your customer domain. It is separate from the authenticated KnitKnot MCP server at mcp.knitknot.ai, which gives a signed-in client access to its authorized workspace.

Choose an interface

InterfaceCustomer-domain pathWhat it serves
Agent feed/agent-feedSigned JSON Feed entries for published Agent versions
Customer-domain MCP/mcpRead-only tools over published pages and approved-fact snapshots
Content indexes/llms.txt and /llms-full.txtIndexes of published Agent versions

An account admin can switch each interface on or off. Other members can read the status, but cannot change the switches. Enabled is the requested state; Effective says whether the current delivery configuration actually includes the interface. Check the Why column when the status is Reconciling, Off, or Unavailable. A switch being on does not make an endpoint live by itself.

The page names origin ownership, Cloudflare prerequisites, signed artifacts, and the current deployment as conditions that must agree before an interface becomes live. If the Cloudflare connection needs attention, open Settings → Integrations. Use the effective status before sharing a customer-domain path with an agent or partner.

WebMCP

The WebMCP section shows a separate, experimental browser interface. When customer-domain MCP is effective and an embed is available, use Copy WebMCP embed to get the pinned module. Browser support is experimental; the module does nothing when navigator.modelContext is unavailable. The console currently cannot measure WebMCP use separately from /mcp calls. Read its status and reason before placing the embed on a page.

For the underlying published content, read the Agent Ledger in Content. To confirm whether Agent versions are being served with your pages, use Content → Delivery. For site access checks and observed bot requests, use Content → Access and Traffic → Agent activity.

If customer-domain MCP is effective, Traffic → Agent tool calls shows estimated use of its read-only tools.