Connect n8n, Make or a script with an API key

Most AI apps sign in with PostDaily. Automations and a few apps can't: n8n, Make, your own scripts, Cline and JetBrains AI Assistant. They use an API key and a separate server URL, https://mcp.postdaily.app/key/mcp.

Create a key

1. 1
   Open Settings → AI agents and select API key
2. 2
   Name it, and choose what it can do

   Use a name you'll recognise later, such as "n8n weekly digest". Pick Full access, Drafts only or Read only, and only the workspaces the automation needs.

3. 3
   Choose when it expires

   30 days, 90 days, 1 year or never. A shorter life limits the damage if it leaks.

4. 4
   Copy the key straight away

   It's shown only once. Store it in your automation's credentials or a password manager.

Connect your tool

• URL: https://mcp.postdaily.app/key/mcp
• Header: Authorization: Bearer followed by your key
• Transport: Streamable HTTP
• n8n and Make: use their MCP client step with the three settings above.
• Cline: add a server with type streamableHttp. Without it, Cline uses the older SSE transport, which PostDaily doesn't support.
• JetBrains AI Assistant: it can't sign in to remote servers yet, so it connects through mcp-remote with the key. Settings → AI agents → JetBrains AI has the exact entry to paste.

Good habits for automations

• Give each automation its own key, so revoking one doesn't break the others, and Settings → AI agents shows which one was used last.
• Use Drafts only for anything that writes posts unattended. A person then schedules them in PostDaily after checking them.
• Send an idempotency key with every write. If your workflow retries a step, PostDaily recognises the repeat and doesn't create the post twice.

When a key stops working

A key stops working when it expires, when you revoke it, and when you change or reset your PostDaily password, which revokes every key you created. Create a new one and update your automation.