Skip to main content
Nudgen supports Personal Access Tokens (PATs) for the REST API and OAuth connections for its MCP server. Use the method that matches your client.

​
Why this matters

You can connect Nudgen to scripts, internal tools, and AI agents without sharing a dashboard session. PAT requests use your account’s active workspace. OAuth MCP connections are bound to the workspace you approve during sign-in. Workspace permissions and rate limits still apply.

​
Create an API key

  1. Open get.nudgen.net.
  2. Go to Settings -> API Keys.
  3. Create a Personal Access Token.
  4. Copy the token once and store it securely.
Use the token in the standard bearer header:

​
REST API

Use the REST API when you want conventional HTTP endpoints for contacts, campaigns, brand settings, and AI draft generation.
Common endpoints include:

​
MCP server

Use MCP when an AI agent can call tools directly instead of hand-coding REST requests. The MCP endpoint is:
The server card is available at:
MCP uses browser-based OAuth sign-in, with a selected workspace and requested scopes. A PAT does not authenticate the MCP endpoint. The same connection can search nearby businesses and import those with a public email into contacts. Agent-created campaigns are drafts, and each MCP campaign launch requires separate browser approval. See the MCP setup guide.

​
Safety notes

  • Treat PATs like passwords.
  • Revoke tokens from Settings -> API Keys when they are no longer needed.
  • Campaign launch endpoints can send real email when the worker processes the queue.
  • Use future scheduledAt values for tests when you do not want to send immediately.