On this page7 sections
You have probably seen the letters MCP next to Claude, ChatGPT or Gemini. The idea behind them is simple: let your AI assistant work directly in your tools, instead of copying and pasting between two windows.
For a freelancer who does not code, the question is not technical. It comes down to two points: what will the assistant be able to do in my account, and what should I check before connecting it?
MCP in one sentence
The Model Context Protocol is a standard way to connect an AI assistant to a piece of software. The vendor publishes an "MCP server"; your assistant connects to it, with your consent, and can then read your data and, in some cases, act on it.
In practice, instead of exporting a Notion database to paste it into a chat, you ask the assistant to read it. Instead of copying its answer into a Canva design, you ask it to prepare the design.
What an assistant can do in your tools
It all depends on what the vendor exposes. Three levels come up:
- documentation only: the assistant knows the tool better, but does not touch your account;
- read: it looks at your data (pages, bookings, statistics) to answer or summarise;
- read and write: it creates, edits or tidies up for you.
In every case, the assistant never has more rights than your account. If you cannot edit a page, neither can it.
Before connecting: four checks
1. What it can do. This is the point that matters. An assistant that reads can only get its answer wrong; an assistant that writes can get your data wrong. Look for three verbs above all: delete, send (a message, a post) and pay. Stripe lets the assistant move money, with a confirmation; Calendly lets it cancel your meetings.
Then the safeguards. Some vendors document a confirmation before acting (HubSpot, Stripe), admin controls or access limited to part of the account (Airtable, Webflow). Others document none: that is information too.
2. The plan. Many servers are open on every plan, but with caps. At Figma, the free plan and seats without editing rights are limited to 20 calls a month. At ClickUp, Free Forever caps at 100 calls per 24 hours. At Zapier, each successful call uses two tasks from your plan.
3. The official server. A server published by a third party does not commit the vendor. ToolTrim only lists official servers, documented by the vendor itself.
4. The setup. Most servers are "remote": nothing to install, you sign in to your account as with any app. A few run on your computer and need a real technical setup: that is the case for the Google Analytics server.
Three examples from our tool pages
Notion: the most complete
Notion offers an official remote server, on every plan, that you plug in with one click from Claude, ChatGPT or Gemini. The assistant can search and read your pages and databases, create and edit them, and also delete pages, databases and comments. Notion documents admin controls for the workspace.
Two caveats: browserless sign-in (MCP tokens), search across connected sources and unlimited queries are reserved for the Business and Enterprise plans; and workspace guests cannot connect. If you work in a client's workspace as a guest, the assistant will not reach it.
See the Notion MCP server sheet →
Canva: open on the free plan, with limits
Canva's official connector is remote and open to every account, Canva Free included. The assistant can search your designs, create one from a description, edit, upload files and comment; the published tool list includes no deletion. Brand templates, brand kits, autofill and resizing stay on paid plans.
Two things to keep in mind: Canva restricts its connector to a list of assistants (ChatGPT, Claude, Gemini, Cursor, Lovable, Make, Perplexity, Grok), and on a team, the admin must allow it before you can use it.
See the Canva connector sheet →
Calendly: simple, but no documented safeguard
Calendly publishes an official remote server, on every plan, that you plug in with one click from Claude or ChatGPT. The assistant can find your open slots, book a meeting, update your availability… and cancel a meeting.
Calendly documents no confirmation before these actions. A meeting cancelled by mistake shows up on your client's side before it shows up on yours: keep approval in your assistant.
Every server, in the same format
The AI agents section gathers the official MCP servers and skills of the tools ToolTrim follows. Each sheet says what the assistant can do, riskiest first, how to plug it in, the plan and safeguards, the tools the vendor documents and when it was checked.
And when there is no server?
Some tools do not have one yet. As of 16 November 2026, Hotjar and Milanote have no official MCP server; our tool pages say so too, with the date it was checked. In that case, classic automations (Zapier, Make) remain the simplest way to move your data around.
Our verdict
MCP does not change your stack: it changes what your assistant can do with it. Before connecting a tool, check four things on its ToolTrim page: what the assistant can do there (above all delete, send, pay), the safeguards, the plan, and when those facts were checked.
Start with a tool where the assistant reads, then open up writing where a mistake is easy to fix. Notion and Calendly lend themselves to it; keep invoicing and payment tools for later.
Browse the official MCP servers →
These facts come from the vendors' documentation, checked on 16 November 2026. MCP servers change fast: check the current terms before connecting your data.


