There are two ways to let the AI you already use work with your Plannerly project: connect Plannerly MCP (no code, in beta), or create a Plannerly API key and let an AI coding tool such as Claude Code or Codex use it. Either way the AI acts as you: it can never see or change more than you can in each project.
| Route 1: Plannerly MCP | Route 2: API key | |
|---|---|---|
| Works in | Claude, ChatGPT and other MCP apps | Claude Code, Codex, or your own code |
| Setup | Add a connector, sign in, approve | Create a key, save it safely, point the AI at the API docs |
| Best for | Asking about your projects in chat | Dashboards, reports, automations, bulk changes |
| Status | Beta - type "add me" in the Plannerly chat to join | Available now |
Route 1: Plannerly MCP (beta)
Plannerly MCP connects the AI you already use, such as Claude or ChatGPT, to your Plannerly projects. There's no code: you add Plannerly to your AI app as a connector, and it works with your own access, just like an API key.
It isn't generally available yet. To join the beta, type add me in the Plannerly chat (in the app, click your profile picture and choose Support). Emma will ask whether you'd like to join the Plannerly beta testing community. Until then, Route 2 works today.
Route 2: An API key with Claude Code or Codex
1. Create your API key
- In Plannerly, click your profile picture and choose API keys, or open a project's Settings and choose API at the bottom of the list.
- Click New key and give it a Name you'll recognise, such as "Claude Code - laptop".
- Set an expiry date under Expiration: 7 days, 30 days, 90 days or 1 year. We strongly recommend one rather than No expiration.
- Under Access, choose only what the AI needs. Every key can read the basics - Core is always on (CoreRead). Tick Read for Docs, Scope or Verify to read those modules (DocsRead, ScopeRead, VerifyRead), and tick Write (for example DocsWrite or ScopeWrite) only if you want the AI to change things.
- Click Create key, then Copy the key. You'll only see it once.
A key inherits your roles and permissions in each project, so it never sees more than you do. It also works only with the servers of the data region you created it in (US, EU or Canada).
2. Save the key without pasting it into the chat
Never paste an API key into a chat with an AI - not in Claude, ChatGPT, Claude Code or Codex. Save it in a file only you can read, from your own terminal, so it never appears on screen or in the conversation.
On a Mac or Linux, run this in a terminal window of your own, not inside the AI tool. It asks for the key without showing what you type:
mkdir -p ~/.config/plannerly && read -rs -p "Plannerly API key: " KEY && printf '%s' "$KEY" > ~/.config/plannerly/api-key && chmod 600 ~/.config/plannerly/api-key && unset KEY && echo " saved"3. Tell your AI how to use it
Paste this into Claude Code or Codex:
I want you to work with my Plannerly project through the Plannerly API.
- My API key is saved in ~/.config/plannerly/api-key. Read it from that file inside each command,
for example: curl -H "Authorization: Bearer $(cat ~/.config/plannerly/api-key)" ...
- Never print the key, echo it, copy it into another file, commit it, or put it in a URL.
- The API documentation is at https://api.plannerly.com/external/v2/docs - read it first.
- My account is on the [US / EU / Canada] servers, so use https://api.plannerly.com/external/v2
(US), https://api.eu.plannerly.com/external/v2 (EU) or https://api.ca.plannerly.com/external/v2 (Canada).
- Start by listing my projects, then ask me which one to work on.
- Before you change anything, show me exactly what you're about to change and wait for my OK.4. Things to ask
- "Which tasks in [project] have a team assigned but nobody accountable?"
- "Build me a one-page HTML dashboard of [project]'s requirements and progress, grouped by milestone."
- "List every information requirement due at handover and who owns it."
- More ideas in the Episode 3 replay.
When you're done
Revoke the key in API keys, or let it expire, and remove the saved file: rm ~/.config/plannerly/api-key.
Your data
- The AI acts as you: same roles, same permissions, in the same data region (US, EU or Canada).
- Plannerly does not train AI on your project data. What you share with Claude, ChatGPT or Codex is covered by that provider's own terms.
- API writes are limited to 30 requests a minute per key (invites 10), so a runaway script can't flood a project.
Related
- Episode 3 of How to survive as a BIM Manager: "Surviving ISO 19650 Information Requirements with AI" - watch the replay
- Plannerly API documentation
