SendToMP

SendToMP lets your website visitors send verified messages directly to their Member of Parliament or a member of the House of Lords. Every message goes through a double opt-in confirmation flow, so only genuine constituents can contact their representatives.

Built by a former parliamentary assistant who understands how MP offices process inbound correspondence, SendToMP is designed to produce messages that get read and acted upon.

Every feature is available to everyone. There is no paid tier, no licence key, no message quota, and nothing is held back.

How it works:

1. A visitor fills in your form with their name, email address, postcode, and message.
2. SendToMP looks up their MP from the postcode, or lets them search for a Peer by name.
3. A confirmation email is sent to the visitor to verify their identity.
4. The visitor clicks through and confirms on your site. Only then is the message sent.
5. The MP or Peer receives a properly formatted email and can reply to the constituent directly.

Form plugin support:

• Gravity Forms
• WPForms
• Contact Form 7
• A webhook / REST API endpoint for custom integrations

Key features:

• Double opt-in confirmation, so a message is only ever sent by the person whose inbox it came from
• Postcode-based MP lookup against the UK Parliament Members API
• House of Lords member search and selection
• Configurable email templates with merge tags
• Submission logging with delivery status tracking
• Rate limiting and anti-spam protection, per email address, per IP, and per postcode
• Address overrides, for when a member’s published address is wrong or missing
• Email delivery through your existing SMTP plugin, your own SMTP server, or Brevo
• A copy-and-paste privacy notice describing exactly what the plugin stores and sends

A note on data. The constituent’s postcode is sent to the UK Parliament Members API in order to identify their representative. Nothing else leaves your site for that lookup: not their name, not their email address, and not their message. If you configure Brevo as your email provider, the message is sent to Brevo for delivery. See the External services section below for the detail.

External services

This plugin relies on one external service to function, and optionally on a second if you choose it as your email provider.

1. UK Parliament Members API (required)

The plugin uses the UK Parliament Members API to work out which MP or Peer represents a constituent, and to obtain the contact address that Parliament publishes for that member. The plugin cannot do this locally: the mapping from postcode to constituency to sitting member changes with boundary reviews, by-elections and appointments, and only Parliament publishes it. No account or API key is required, and the plugin sends no credentials.

Data sent, and when it is sent:

• When a visitor uses the “Find my MP” preview on your form, their postcode is sent, so the matched MP can be shown before they submit.
• When a visitor submits the form, their postcode is sent, to resolve the member the message will go to.
• When an administrator searches for a member by name in the plugin’s admin screens, the search text is sent.
• Once a member has been identified, the plugin requests that member’s public profile and published contact details using their Parliament member ID.

The constituent’s name, email address, and message content are never sent to Parliament. Responses are cached in your site’s transients so the same postcode is not looked up repeatedly.

Service: UK Parliament Members API, https://members-api.parliament.uk/ Terms of use (Open Parliament Licence): https://www.parliament.uk/site-information/copyright-parliament/open-parliament-licence/ Privacy policy: https://www.parliament.uk/site-information/data-protection/

2. Brevo (optional)

Brevo is one of the email delivery providers you may choose on the Email Delivery tab. It is only contacted if you select it and enter your own Brevo API key. If you use your existing SMTP plugin, your own SMTP server, or the WordPress default mailer instead, the plugin never contacts Brevo.

Data sent, and when it is sent: when Brevo is the selected provider, each outgoing email is sent to Brevo’s transactional email API at the moment it is delivered. That includes the recipient’s address, the constituent’s name and email address as the reply-to, the subject, and the message body. This applies both to the confirmation email sent to the constituent and to the message delivered to the MP or Peer.

Service: Brevo, https://www.brevo.com/ Terms of use: https://www.brevo.com/legal/termsofuse/ Privacy policy: https://www.brevo.com/legal/privacypolicy/

The plugin contacts no other external service. It sends no analytics, usage data, or telemetry anywhere.