Doorman

com.withdoormanPublished by withdoorman.comOfficial publisherv0.1.0Updated Oct 24, 2026

Spam, pitch and fraud screening for website forms. Sign up, wire forms, test and review.

VerifiedStreamable HTTPWeb executableDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Doorman screens website form submissions for spam, pitches and fraud, and lets an assistant set up forms, test them and review held submissions.

What you can do
Read Doorman's integration docs and check account, plan and monthly usage with the whoami tool, or create an account and first form with an API key via signup after asking for the user's email. List, create and update form endpoints, including context, destinations, thresholds, watch mode and allow/block lists. Get ready-to-paste integration snippets for platforms such as html, react, fetch, nextjs, express, python, ruby and elixir. Judge a sample message against a form's settings for free, and send a test delivery to email, Slack or webhook destinations. List recent submissions with verdicts, filter held ones awaiting review, and label a submission real or spam.
When to use it
Useful when a site has contact, demo, checkout or comment forms that attract spam and you want an assistant to wire them up, verify delivery and triage held submissions without leaving the conversation.
Requirements
Remote endpoint at withdoorman.com over streamable HTTP. An Authorization header with a Bearer Doorman API key is optional: without it, the docs and signup tools still work, and signup returns a key. Signup needs the user's email address, and they receive an email to set a dashboard password.
Before you install
The Authorization header carries a secret API key; the signup tool returns an api_key that should be stored in the project's local secrets. Signup creates a real account and first form for the user, so confirm their email first. Labeling a submission real can deliver a message that was held or dropped, and test deliveries send real messages to the form's email, Slack or webhook destinations. Contacting support attaches account context such as plan, forms and recent errors, though not keys.

Installation

In SourceWeft

  1. Open Doorman in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.withdoorman%2Fdoorman/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "doorman": {
      "type": "http",
      "url": "https://withdoorman.com/mcp"
    }
  }
}

Tools

12

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.

Takes no parameters.

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).

Parametersmodeemailrequiredsite_urlrequiredform_namesite_contextrequired

doorman_whoami

Account, plan and this month's usage.

Parametersapi_key

doorman_list_forms

List the account's forms with their action URLs and settings.

Parametersapi_key

doorman_create_form

Create another form endpoint (one per distinct form on the site: contact, demo request, checkout, comments).

Parameterskindnamerequiredapi_keyemail_toslack_urlwebhook_urlredirect_urlsite_context

doorman_update_form

Change a form's settings: context, destinations, thresholds, watch mode, allow/block lists.

Parameterskindmodenameapi_keyform_idrequiredemail_toslack_urlallow_listblock_listdeliver_atdrop_belowwebhook_url+3 more

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.

Parametersapi_keyform_idrequiredplatformrequired

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).

Parametersemailapi_keyform_idrequiredmessagerequired

doorman_send_test_delivery

Send a sample delivery to the form's email/Slack/webhook destinations and report whether each one worked.

Parametersapi_keyform_idrequired

doorman_list_submissions

Recent submissions with their verdicts. Use review=true for held ones waiting for a human.

Parameterslimitroutereviewapi_keyform_id

doorman_label_submission

Mark a submission real (delivers it if it was held or dropped) or spam.

Parameterslabelrequiredapi_keysubmission_idrequired

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.

Parameterserrorapi_keymessagerequiredcategory

Version history

1
  1. v0.1.0LatestOct 1, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.