Agent setup
Connect your AI coding agent to Doorman, then let it wire up your forms, choose where submissions go and run a test, straight from your editor or terminal.
The prompt works with any agent: it points it at /llms.txt. Your agent asks you one question, the email for real submissions.
Pick your agent
Select an agent for step-by-step setup instructions.
- AnthropicClaude Code Anthropic's coding agent for the terminal, IDEs and desktop. Reads your codebase, edits files and runs commands. View guide
- OpenAICodex OpenAI's coding agent as a terminal CLI, an IDE extension and a desktop app. View guide
- AnysphereCursor AI code editor built on VS Code, with an agent that edits across files and runs commands. View guide
- GitHubGitHub Copilot Copilot's agent mode in VS Code and other editors, with native MCP support. View guide
- WindsurfWindsurf Agentic code editor whose Cascade agent plans and makes multi-file changes. View guide
- GoogleGemini CLI Google's open-source agent for the terminal, with MCP and built-in tools. View guide
- Open sourceOpenCode Open-source terminal agent that works with many model providers. View guide
- ClineCline Open-source coding agent that runs as a VS Code extension. View guide
- Any agentAnything else Any agent that can make HTTP requests can follow /llms.txt: no MCP needed. View guide
Compare agents
Where each one runs and how it connects to Doorman.
| Agent | Terminal | IDE | Extension | Setup by prompt | Doorman MCP | Config |
|---|---|---|---|---|---|---|
| Claude Code | – | claude mcp add | ||||
| Codex | – | ~/.codex/config.toml | ||||
| Cursor | – | – | .cursor/mcp.json | |||
| GitHub Copilot | – | .vscode/mcp.json | ||||
| Windsurf | – | – | ~/.codeium/windsurf/mcp_config.json | |||
| Gemini CLI | – | – | ~/.gemini/settings.json | |||
| OpenCode | – | – | opencode.json | |||
| Cline | – | – | Cline → MCP Servers → Configure |
Every agent here can set Doorman up from the prompt alone. MCP gives it Doorman's tools directly: sign up, configure forms, get install code, run tests, review held submissions.
What your agent will do
- Find your forms and read what your business sells from the README or site copy.
- Ask you one question: which email should get real submissions.
- Create your account with one API call, or use the key you give it. You get an email to confirm and set a password.
- Wire it in: the form's action URL for a static site, or a
/v1/checkcall in your backend handler. - Store the key as
DOORMAN_KEYin.env, gitignored, never committed. - Prove it works: one genuine enquiry delivered and one pitch dropped, both free test submissions.
› Add Doorman spam protection to this project's forms. Follow https://withdoorman.com/llms.txt ✓ Read the setup guide ✓ Found 1 form: index.html "Get a quote" ? Which email should get real submissions? owner@brightpath.co ✓ Created account and form ✓ Pointed the form at Doorman, added d.js ✓ Saved DOORMAN_KEY to .env (gitignored) ✓ Test: genuine enquiry → delivered ✓ Test: SEO pitch → dropped
Safe by default
Your key stays in .env
The prompt tells your agent to store the key as DOORMAN_KEY in a gitignored .env and never commit it. Revoke any key in Settings.
You confirm the account
An agent sign-up emails you a link to confirm and set a password. Until then the account has 100 checks and no email forwarding.
No surprises in your inbox
Doorman only emails addresses that confirmed they want submissions, so an agent can't point forwarding at someone else.
One sentence to your agent
Or set it up yourself in two minutes. Free for your first 1,000 checks every month.