External access over MCP
Connect Claude, ChatGPT and other MCP-compatible applications to your brand, choose what they may read and change, and remove access whenever you like.
Privacy and analytics
We use necessary technical cookies and, only with your consent, analytics and marketing pixels to improve the website and measure campaigns.
Connect Claude, ChatGPT and other MCP-compatible applications to your brand, choose what they may read and change, and remove access whenever you like.
With MCP (Model Context Protocol), an assistant such as Claude or ChatGPT can look up your brand in Nömad on your behalf: the Genome, the Kit, your work, the calendar. Use it when you want to work on your brand from that application with the same information Nödo has. You choose what it may read, what it may ask to change and for how long.
Settings › MCP.Settings › MCP.The application shows up under Your authorized applications, with the permissions you gave it in this brand.
Each area of the brand can be given for reading and, separately, for changing:
| Permission | What it allows |
|---|---|
| An area on its own (for example Genome, Brand Kit, Works, Calendar, Library) | Read that part of the brand. |
| … · change (for example Calendar · change) | Ask for changes on your behalf. They happen at once or wait for your approval, depending on the brand's agent policy. |
| Publishing · propose | Draft posts and ideas and ask for review. Never publishes: a person decides in Nömad. |
Some areas, such as Plan or Activity, can only be read. Give only what the application needs: you can always add more later.
Only permitted content is shared. Credentials, integration references and internal operational data stay in Nömad.
Your assistant does not see Nömad's internal structure: it receives your brand's context, ready to work with. For example, the brand voice to write like it, the Genome summary, the Kit, your works or your calendar, always within the permissions you gave. It is what you get when you export the brand for AI from the Genome, but live and without copying files.
What an application does with a · change permission depends on the brand's agent policy, in Settings › Nödo, Outside agents:
| Policy | What happens when it asks for a change |
|---|---|
| Read only | Nothing changes, even with the permission. |
| With approval (default) | The change waits. Whoever connected the application gets a notice and decides in Your account › Approvals, with Approve or Decline. If nobody decides, it expires after 24 hours. |
| Direct | The change happens at once. Deleting, disconnecting or removing access still waits for approval. |
Whatever the policy, no application can delete anything for good, publish or schedule on your networks, send campaigns, charge, change plan with a charge or grant important roles. It cannot touch your account or the workspace either. More in Confirmations and Nödo settings.
If you have already connected the application to your account, you can give it access to this brand from here:
Permissions apply only to this brand.
The application can no longer read this brand on your behalf, straight away. Its access to other brands is unchanged. If someone else in the brand connected an application, you see it with Connected by {name} and, as an admin, you can remove its access too.
The technical reference for the MCP server (tools, resources, authorization and limits) is in MCP. If you would rather use the API with tokens or service accounts, start with Tokens and service accounts.
Updated on November 16, 2026