Integrations

Zed's agent with the Notix tools.

Zed's agent takes MCP servers as context servers that it starts locally. Add notix-mcp as one, with the command npx -y notix-mcp and your key in NOTIX_API_KEY, then use the agent to send a test or write the email code for your app.

The send

Send an email from Zed.

What the context server runs

command: npx
args:    -y notix-mcp
env:     NOTIX_API_KEY=<your Notix API key>

Paste into the tool

Add email sending with Notix (npm package notix-js, docs at https://usenotix.dev/docs).
Send from a server-side route only, reading the key from the NOTIX_API_KEY
environment variable. Never put the key in client code. Add a function that sends the password reset email.

The from address must be on a domain you have verified in Notix. Step by step: Connect your AI.

The app it builds

Ask for a server-side send, with the key in the environment.

When Zed's agent writes the email code for your app, ask for it in a server route or server function that reads NOTIX_API_KEY from the environment. A key in client code is public the moment the app is deployed.

The from address must be on a domain you have verified in Notix. Until it is, check sends with the Notix-Dry-Run: true header, which sends nothing.

MCP

Give Zed the Notix tools.

Notix hosts an MCP server at https://app.usenotix.dev/api/mcp. Add the local runner in Zed's context server settings with the command above. The local runner shows every tool and leaves refusals to the API, so use a sending key.

Ask for a dry run first: Notix checks the send and sends nothing. A Live key sends from one verified domain, asks for approval before a send to more than 50 people by default, and cannot delete anything or change billing.

The local runner, as the Notix MCP README gives it

{
  "mcpServers": {
    "notix": {
      "command": "npx",
      "args": ["-y", "notix-mcp"],
      "env": { "NOTIX_API_KEY": "your_key" }
    }
  }
}

FAQ

Questions, answered.

Where should the email code go?

In a server route or server function that reads NOTIX_API_KEY from the environment. Code that runs in the browser cannot hold the key safely, so ask for the send on the server and call that route from the page.

Can the AI send to real people by mistake?

Not by surprise. A Live key sends only from the one domain you chose, stops for the day at its daily limit (500 to start), and waits for your approval before a send to more people than its Ask me first number (50 to start). You can pause the key at any time, and every call is in the audit log.

Is there a local MCP server as well as the hosted one?

Yes. The notix-mcp package runs the same tools on your own machine with npx -y notix-mcp and the key in NOTIX_API_KEY. The hosted address https://app.usenotix.dev/api/mcp is the supported path for Live keys, because it shows a key only the tools it may use.

The free plan does not ask for a card.

Docs