Surface and Your AI Agents
Two directions: agents that drive Surface through MCP, and AI agents that read your website.
Agents That Drive Surface
Claude, Codex, Cursor, Windsurf, Grok, your own: any MCP client reads and writes your workspace through one HTTP endpoint.
Agents That Read Your Site
Answer engines are a traffic source. AI referrals arrive split out by engine, with a lead score attached.
Agents Driving Surface
One endpoint, https://app.withsurface.com/mcp, Streamable HTTP, 128 tools. No
local process, no Docker, no per-client SDK.
| Client | Page |
|---|---|
| Claude Desktop, Claude Code, claude.ai | Claude |
| OpenAI Codex | Codex |
| Grok | Grok |
| Cursor, Windsurf, custom clients | Other clients |
Exact config is in API setup.
Two Rules That Apply to Every Client
Scope is the credential, not the client. A key or OAuth connection belongs
to one environment and cannot reach another. ?tools=
changes what your agent loads, never what it is permitted to touch.
Read-only is one parameter. ?readonly=1 strips every write and admin tool,
whatever the credential could otherwise do.
https://app.withsurface.com/mcp?tools=insights&readonly=1Agents Reading Your Site
- Traffic analytics breaks out AI referrals: a human who clicked through from ChatGPT, Perplexity, Claude or Gemini, tagged by engine with an average lead score attached.
- AI Visibility measures whether you appear in the answers those engines give, per prompt and per model.
- Campaign Agents draft the material that closes the gaps, as artifacts you review before they publish.
Reading These Docs with an Agent
| What | URL |
|---|---|
| Index of every page, in Markdown | /llms.txt |
| The whole site as one file | /llms-full.txt |
| Any single page as Markdown | append .md to its URL |
Every page also links to its Markdown version with
<link rel="alternate" type="text/markdown">.
Point your agent at /llms-full.txt for the docs and
Surface MCP for the workspace.