Connect Eden to Make

This is the automation path, not the AI-assistant connection, which signs in through a browser. Make runs in the cloud, so it authenticates with a personal access token instead. Give the token read + write access so a scenario 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).
• A Make account with the MCP Client app available (currently in open beta).

Step 1 — Generate a personal access token in Eden

1. 01

   Open Settings → Integrations → API access

   In Eden, go to Settings → Integrations and find the API access card.

2. 02

   Generate a Read & write token

   Name it make, keep the scope on Read & write (required for scheduling — read-only can only read your workspace), and click Generate token.

3. 03

   Copy it now

   Copy the eden_pat_… value immediately — it's shown only once. Eden keeps just a hash and can't show it again.

Step 2 — Add the MCP Client module in Make

1. 01

   Add an MCP Client module to your scenario

   Search the module list for MCP Client and add it. Choose the module that executes a selected tool (the deterministic one that runs a specific tool with a JSON request) rather than the AI-driven "execute a task" variant, unless you specifically want an AI to pick the tool.

2. 02

   Create a connection to Eden's server

   When prompted for the server URL, enter:

   https://mcp.eden.so/mcp
   

   For authentication, choose the bearer token option and paste your eden_pat_… token. Make will load Eden's available tools.

3. 03

   Pick the Eden tool

   Choose the tool you want to run — eden_list_schedules to read your accounts and slots, or eden_schedule_post / eden_create_scheduling_draft to write. Make auto-renders the input fields from the tool's schema.

Step 3 — Wire up the flow

1. 01

   Start with your trigger

   Use whatever Make module fits your content source — a Notion/Airtable/Sheets watch, a webhook, or a scheduled trigger.

2. 02

   Map content into eden_schedule_post

   Map the post text and timing into the MCP Client module's fields. A minimal call looks like:

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

   Omit the time to let Eden drop it into the next free queue slot, or use eden_create_scheduling_draft to stage drafts for review instead of publishing.

What Eden can do through the connection

A read + write token isn't limited to scheduling. Eden's tools also let a scenario create notes and append to or rewrite them; create, rename, and trash boards; save links and indexed social posts onto a board; and edit, reschedule, or add a first comment to a queued post — plus all the read tools. See the full list in Connect Eden to n8n. (No folder creation, hard delete, or creator/list mutation.)

A few things to know

• Time is a real timestamp. Use epoch milliseconds (scheduledFor) or an ISO string (scheduledAtIso) — not natural language. Convert any date field in Make first.
• Text-only posts work for X, Threads, LinkedIn, and Substack notes. Instagram and TikTok require hosted media — pass a publicly reachable image/video URL, not a local file.
• Read-only tokens can't schedule. If eden_schedule_post returns a permission error, you're using a read-only token — generate a Read & write one and reconnect.

Managing or revoking the token

In Settings → Integrations → API access you can see each token's name, scope, and last-used time, and Revoke the Make token. Revoking takes effect immediately. Generate a new token to reconnect the scenario.

Where to go next

• Want more control with code-style logic? See connect Eden to n8n.
• Prefer Zapier? See connect Eden to Zapier.
• Learn how Eden queues and publishes: scheduling and publishing.