nintact MCP server

Read from the package source without running it. The installed server may list more.

• add_knowledge

  Facts the AI may state in replies. Anything not written here is left as a [placeholder] for a human instead of being guessed. Adding entries is the highest-leverage way to improve drafts.

• approve_draftwrite action

  Sends a real email to the person who wrote in. CONFIRM WITH THE USER FIRST. Pass `body` to replace the text before sending; the original draft is kept. Pass `to` when the submission carried no email address.

• check_deliverability

  Resolve a domain's live SPF, DKIM, DMARC and MX and say whether mail sent as that domain reaches Gmail today. NO API KEY NEEDED. Use this whenever a user is building or fixing a site with a contact form, before assuming their mail works \u2014 form mail failing silently is the normal case, not the exception. The reply includes a next_step describing both ways to fix it.

• create_formwrite action

  Create a form and get paste-ready snippets. The one-line script tag renders the whole form; the form id is public and safe in client-side code. Submissions are classified and answered with an AI-written draft that a human approves.

• create_inbound_addresswrite action

  Issues an address to forward existing mail to. Mail sent there is classified and drafted exactly like a form submission. Omit `address` to have one generated.

• delete_formwrite action

  Permanently deletes the form AND every message, draft and reply received through it. Confirm with the user first. To stop receiving without losing data, use update_form with is_active:false.

• delete_inbound_addresswrite action

  Stops accepting mail at that address. Messages already received are kept.

• delete_knowledgewrite action

  Removes it permanently.

• design_form

  Turn a plain-language description into form fields, purpose, a success screen and a visual theme. NOTHING IS SAVED \u2014 this returns a proposal to show the user. Save it with create_form or update_form. Pass form_id to rewrite an existing form instead of designing a new one.

• duplicate_form

  Copy a form's fields, theme, success screen and logo into a new form with its own id. Messages received by the original are NOT copied. Useful for per-branch or per-campaign forms.

• get_form

  A form with its fields, success screen and paste-ready snippets. Accepts the uuid or the public id.

• get_message

  A message, the current draft awaiting approval, every earlier draft, replies already sent, and any attachments (with short-lived signed URLs). Photos attached to a submission are read by the model when the draft is written.

• get_organization

  Company name, industry, signature and extra instructions \u2014 all of it feeds every reply draft.

• get_sending_domain

  By default replies go out from nintact's shared, authenticated domain and the customer needs no DNS. This shows whether the workspace has switched to its own domain, and which DNS records are still missing.

• get_usage

  Draft count against the plan limit. Reaching the limit never stops form submissions \u2014 messages keep arriving and are stored; only draft generation pauses.

• list_forms

  Every form in this organization, with its endpoint URL.

• list_inbound_addresses

  Addresses that accept forwarded mail. Forward an existing info@ here to run it through nintact.

• list_knowledge

  What the AI is allowed to use as fact when writing replies.

• list_messages

  Messages received through forms or forwarded email, newest first. Each carries a category (estimate_request, question, complaint, sales, spam, other) and a one-line summary.

• regenerate_draft

  Produce a new draft for a message. Earlier drafts are kept as previous versions. Optionally say how to change it, e.g. "shorter, and do not mention price".

• remove_form_logowrite action

  Deletes the stored image and clears it from the form.

• remove_sending_domainwrite action

  Goes back to sending from the shared nintact domain. Receiving and history are untouched.

• scan_site_for_knowledge

  Reads the organisation's own website (top page plus pricing / about / FAQ pages) and proposes facts that replies can be grounded on: service area, pricing, lead times, opening hours. Nothing is saved \u2014 review the items and create the ones worth keeping with create_knowledge_item. Use this right after setting up a workspace so the very first reply already sounds like the company.

• set_form_logo

  Fetches a public https image and shows it above the form. PNG, JPEG, WebP or GIF under 2MB. SVG is refused on purpose \u2014 it can carry scripts, and this image is loaded on other people's sites. Adjust the displayed size with update_form's logo_width.

• set_sending_domain

  Business plan and above. Registers a domain the organisation owns and returns the DNS records to add. Replies keep going out from the shared domain until verification succeeds, so nothing breaks in between.

• transfer_workspacewrite action

  Moves the whole workspace to another person: they become the owner and billing switches to them. Use this at the end of a build \u2014 you set the form up, then hand it to the business that will answer the inquiries. The embed code does not change, so the site keeps working. They receive a link by email and the transfer completes when they open it.

• update_draftwrite action

  Save an edited subject or body. The model's original text is preserved separately \u2014 the difference is what teaches nintact this company's voice.

• update_formwrite action

  Change any part of a form: name, purpose, fields, notification targets, allowed origins, success screen, visual theme and CSS, or turn it off. Passing `fields` replaces the whole list.

• update_knowledgewrite action

  Change the text, or set is_active:false to stop using it without deleting it.

• update_message_statuswrite action

  Move a message out of the way, or put a wrongly-filed one back. Sending a reply is done with approve_draft, not by setting a status.

• update_organizationwrite action

  `ai_instructions` is appended to every draft prompt \u2014 use it for house rules (e.g. "always say prices exclude tax", "never promise a delivery date"). `reply_to_email` is where replies from customers land.

• verify_sending_domain

  Asks the mail provider to re-check the DNS. Returns pending while records have not propagated yet.

• Code scan2 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 14 days ago15/15
• Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10

Safety score

82/100

higher than 70% of 916 Email servers

Tools

32

the typical Email server has 7

Tools that change things

44%

typical: 25%. Fewer write tools means less an agent can break

Downloads a week

57

more than 40% of 235 Email servers with a package

nintact: common questions

Is nintact MCP server safe?

Mostly: it is graded B (82/100). Read the nintact safety report

How do I install nintact?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does nintact need an API key?

Yes. The registry entry asks for NINTACT_API_KEY.

Is nintact maintained?

The last commit was 47 days ago (2026-09-18). The latest release is v0.5.2.

What can I use instead of nintact?

Servers from other publishers that do the same job: e2a — email for AI agents MCP server, Outlook MCP server and Imap MCP server. Compare all nintact alternatives.

How does nintact compare with other Email MCP servers?

safety score 82/100 (higher than 70% of 916 Email servers); tools 32 (the typical Email server has 7); tools that change things 44% (typical: 25%. Fewer write tools means less an agent can break). Full comparison.