Doorman
Doorman keeps sales pitches, bots, fake sign-ups and card testers out of website forms, with no captcha.
What it can do
- Doorman Docs: Read how Doorman works and how to integrate it (the same text as /llms.txt). Call this first if you haven't used Doorman before.
- Doorman Signup: Create a Doorman account for the user with a first form and an API key. Ask the user for their email first. They'll get an email to set a dashboard password. Creates the account's firs
- Doorman Whoami: Account, plan and this month's usage.
What data it sees
Do you need an account
No: the server works without sign-in
Doorman keeps sales pitches, bots, fake sign-ups and card testers out of website forms, with no captcha. Each submission is judged in about 100 ms and every drop comes with the sentence that gave it away, rescuable in one click.
This server lets a coding agent do the whole setup: create the account, create a form endpoint per form on the site, fetch the install snippet for the stack (HTML, React, Next.js, Express, Python, Ruby, Elixir, Webflow, Framer), send test submissions, check delivery to email, Slack or a webhook, and review or relabel held submissions later.
No key needed to start: doorman_signup creates an account and returns an API key; pass it as api_key to the other tools. Already have one? Get it from https://withdoorman.com/app#/settings.
Docs: https://withdoorman.com/docs · Agent guide: https://withdoorman.com/llms.txt
How to connect
How to connect Doorman to Claude
The server address to paste into Claude settings:
https://doorman--withdoorman.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Doorman to ChatGPT
The server address to paste into ChatGPT settings:
https://doorman--withdoorman.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Doorman to Cursor
The server address to paste into Cursor settings:
https://doorman--withdoorman.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (12)
Raw names from tools/list. Only developers need these.
| doorman_docs | Read how Doorman works and how to integrate it (the same text as /llms.txt). Call this first if you haven't used Doorman before. |
| doorman_signup | Create a Doorman account for the user with a first form and an API key. Ask the user for their email first. They'll get an email to set a dashboard password. Creates the account's first form too and returns its id and action URL, plus the api_key (store it as DOORMAN_KEY in the project's local secrets file, never commit it). Only for new users: if they already have an account, ask for a key instead. Until the user clicks the confirmation link in that email, nothing is emailed to them (100 checks; Slack and webhooks work). |
| doorman_whoami | Account, plan and this month's usage. |
| doorman_list_forms | List the account's forms with their action URLs and settings. |
| doorman_create_form | Create another form endpoint (one per distinct form on the site: contact, demo request, checkout, comments). |
| doorman_update_form | Change a form's settings: context, destinations, thresholds, watch mode, allow/block lists. |
| doorman_get_install_snippet | Get ready-to-paste integration code for a form on a given platform. Use 'html' for static sites, 'react' for SPA client components, and 'fetch' (plain fetch with timeout and fallback: Workers, Node, Next, Deno), 'nextjs', 'express', 'python', 'ruby' or 'elixir' when the form already posts to the project's own backend. |
| doorman_test_submission | Judge a sample message against a form's settings. Free, not forwarded, not counted. Use it to show the user Doorman working after setup (try one genuine enquiry and one sales pitch). |
| doorman_send_test_delivery | Send a sample delivery to the form's email/Slack/webhook destinations and report whether each one worked. |
| doorman_list_submissions | Recent submissions with their verdicts. Use review=true for held ones waiting for a human. |
| doorman_label_submission | Mark a submission real (delivers it if it was held or dropped) or spam. |
| doorman_contact_support | Stuck, or something isn't working? Send the problem straight to Doorman's founder, with the error you hit. Your account context (plan, forms, recent errors, never keys) is attached, and the reply goes to the account email. Use it instead of guessing at a fix. |