Eden MCP

Connect Eden to n8n

Drive Eden from n8n with a personal access token. Watch a Notion database, Google Sheet, or any trigger and auto-schedule posts into Eden — a hands-off way to replace Buffer.

·6 min read

n8n can talk to Eden through the same connection your AI assistant uses — but because n8n runs on a server, you authenticate with a personal access token instead of signing in through a browser. Once it's connected, an n8n workflow can watch a Notion database (or a sheet, a form, anything n8n triggers on) and schedule the matching posts straight into Eden. It's the clean way to replace Buffer with your own pipeline.

This is different from connecting Claude, Cursor, or ChatGPT, which sign in through a browser. n8n runs unattended on a server, so it authenticates with a personal access token instead. Give the token read + write access so n8n can schedule and save on your behalf — a read-only token can only read your workspace.

What you'll need

  • An Eden account with scheduling set up (connect your social accounts first).
  • n8n (cloud or self-hosted) with the MCP Client Tool node available.
  • A trigger source — a Notion database, Google Sheet, Airtable, a form, whatever you already plan content in.

Step 1 — Generate a personal access token in Eden

  1. 01

    Open Settings → Integrations → API access

    In Eden, click your avatar, choose Settings, then Integrations. Find the API access card (the one mentioning n8n, Zapier, and Make).

  2. 02

    Generate a Read & write token

    Give it a name like n8n, leave the scope on Read & write (this is required for scheduling and saving — a read-only token can only read your workspace), and click Generate token.

  3. 03

    Copy it now

    Copy the eden_pat_… value immediately. It's shown once — Eden stores only a hashed version and can never show it again. Paste it somewhere safe for the next step.

Step 2 — Add Eden as an MCP server in n8n

  1. 01

    Add an MCP Client Tool node

    In your workflow, add the MCP Client Tool node. (In an AI-agent workflow it attaches to the Agent node as a tool; you can also use the standalone MCP Client node to call a specific tool directly.)

  2. 02

    Point it at Eden's endpoint

    Set the endpoint / server URL to:

    https://mcp.eden.so/mcp
    

    Choose HTTP Streamable as the transport if n8n offers the choice (SSE also works).

  3. 03

    Authenticate with Bearer Auth

    Set the authentication to Bearer and paste your eden_pat_… token as the value. That's the only credential Eden needs — no client ID, secret, or OAuth sign-in.

  4. 04

    Confirm the tools load

    Save the node and let n8n list the available tools. You should see Eden's tools, including eden_list_schedules, eden_schedule_post, and eden_create_scheduling_draft.

Step 3 — Build the "watch Notion → schedule" flow

The classic pipeline has three parts:

  1. 01

    Trigger on your content source

    Use n8n's Notion Trigger (or Sheets, Airtable, etc.) to fire when a row is added or a status property changes — for example, when a page's Status becomes Ready to schedule.

  2. 02

    Look up your schedule (optional but recommended)

    Call eden_list_schedules once to get your schedule's connected accounts, timezone, and the next free queue slots. Use this to decide the platforms and timing.

  3. 03

    Schedule the post

    Call eden_schedule_post with the row's content. At minimum:

    {
      "text": "Your post text, line breaks preserved",
      "platforms": ["twitter", "linkedin"],
      "scheduledAtIso": "2026-06-25T14:00:00Z"
    }
    

    Map text from the Notion property and scheduledAtIso from a date field (or omit the time and let Eden drop it into the next free slot). Prefer eden_create_scheduling_draft instead if you want posts to land as drafts for a human to review before they go out.

What Eden can do through the connection

A read + write token unlocks Eden's full tool set in n8n. Beyond scheduling, you can:

  • Posts — schedule, publish now, save as a draft, reschedule or edit a queued post, add or change its auto first-comment, and cancel one.
  • Notes (documents) — create a note, rewrite it, or append to it (great for an ongoing "log" or "ideas" doc).
  • Boards — create a board, rename it, trash it (soft/restorable), and save links or indexed social posts onto it.
  • Read — list workspaces, boards, schedules and queued posts; read notes, cards, and creator research.

The model picks the right tool from your instruction — you don't wire each one by hand. (There's no folder creation, hard delete, or creator/list mutation.)

A few things to know

  • Time must be a real timestamp. The scheduling tools take epoch milliseconds (scheduledFor) or an ISO timestamp (scheduledAtIso), not natural language. Convert your Notion date field in n8n before passing it.
  • Text-only works for X, Threads, LinkedIn, and Substack notes. Instagram and TikTok require hosted media — n8n must give Eden a publicly reachable image/video URL (not a local file path).
  • Threads. For an X or Threads thread, pass segments (one entry per post). If you pass long text with no segments, Eden auto-splits it to fit the platform limit.
  • Scope matters. If you used a read-only token by mistake, eden_schedule_post returns a permission error. Generate a Read & write token and swap it in.

Managing or revoking the token

Open Settings → Integrations → API access any time to see your tokens (name, scope, last used) and Revoke the n8n one. Revoking is immediate — the workflow stops being able to reach Eden the moment you click it. Generate a fresh token to reconnect.

Where to go next

Still stuck?

Email us. A real person reads every message.

Tell us what you tried and where you got stuck. We answer within one business day.

[email protected]