Home / Prompt library
For vibecodersPick your tool, copy the prompt, paste it into the chat. Your agent wires up real email sending against Mektup's REST API - no docs tab-switching, no guessing at request shapes.
Every prompt below assumes you've got a Mektup API key (free, no card - app.usemektup.com → API keys) and a domain registered in Mektup. If you haven't done that part yet, ask your agent to do that first with the setup prompt below, then come back for the platform-specific one.
For an agent with MCP support (Claude Code, Cursor, Claude Desktop) - it can do the whole thing, including reading back the DNS records to add.
Connect Mektup's MCP server (https://mcp.usemektup.com/mcp) as a remote MCP server, or if that's not supported, tell me and I'll paste an API key instead. Then:
1. Register my domain {yourdomain.com} with create_domain.
2. Show me the exact DNS records it returns so I can add them.
3. After I confirm they're added, call verify_domain.
4. Create a mailbox called hello@{yourdomain.com}.
5. Send a test email from it to me so I can confirm it works.
Lovable projects run on Supabase edge functions or the built-in backend - this keeps the API key server-side, never in the browser.
Add a contact form to this app that sends real email through Mektup. Requirements:
- Create a Supabase edge function (or use the built-in backend) that receives {name, email, message} and POSTs to https://api.usemektup.com/v1/emails with header Authorization: Bearer MEKTUP_API_KEY (env var, never expose it client-side) and JSON body { "from": "hello@{yourdomain.com}", "to": "{yourinbox}@{yourdomain.com}", "replyTo": the submitter's email, "subject": "New contact form message", "html": a formatted version of the message }.
- Build the form UI in the app's existing design system, POST to the edge function, show a success/error state.
- Add MEKTUP_API_KEY as a secret, don't hardcode it.
For an existing codebase - points the agent at the right file conventions instead of guessing.
Add a server-side function to send email via Mektup, matching this project's existing API route / backend conventions. It should:
- Accept {to, subject, html, replyTo?}.
- POST to https://api.usemektup.com/v1/emails with Authorization: Bearer process.env.MEKTUP_API_KEY, Content-Type: application/json, body { from: "hello@{yourdomain.com}", to, subject, html, replyTo }.
- Throw/return a clear error if the response isn't ok - log the response body for debugging.
- Add MEKTUP_API_KEY to .env.example (no real value) and to whatever secrets file this project already uses.
Then wire it into {describe where you want it called from - a contact form, a signup confirmation, etc}.
These often generate a single-file or serverless-first app - this prompt is explicit about not leaking the key to the browser.
Add email sending to this app using Mektup (a REST email API). Important: the API key must only ever be used server-side (a serverless function / API route), never in client-side JavaScript. Server-side function: POST https://api.usemektup.com/v1/emails Headers: Authorization: Bearer, Content-Type: application/json Body: { "from": "hello@{yourdomain.com}", "to": "recipient@example.com", "subject": "...", "html": "...", "replyTo": "optional" } Wire this up so the frontend calls my own backend endpoint (not Mektup directly), and my backend calls Mektup with the key from an environment variable.
No-code automation - a plain HTTP-request-node recipe instead of a code prompt.
HTTP Request node config:
Method: POST
URL: https://api.usemektup.com/v1/emails
Headers: Authorization: Bearer {{MEKTUP_API_KEY}}, Content-Type: application/json
Body (JSON):
{
"from": "hello@{yourdomain.com}",
"to": "{{recipient}}",
"subject": "{{subject}}",
"html": "{{body}}"
}
Response 202 = queued for delivery. Check messageId in the response to log/track it.
Yes. Every prompt on this page tells your AI agent exactly which endpoint to call, what headers and body shape to use, and where to put the API key - the same information a human developer would need, just phrased for an agent. Paste it in, the agent writes the integration code.
You need a Mektup API key for the code to actually send mail, but the prompt itself works either way - the agent will write correct code and just need a key filled in as an environment variable afterward. Sign up free at app.usemektup.com, no credit card required.
Yes. The prompts describe a plain REST API call - any AI coding assistant that can write an HTTP request (ChatGPT, Gemini, Windsurf, Cline, whatever comes next) can use the same prompt text.