MCP Server vs Integration: Choose in Insulin

Notion, Atlassian and ClickUp each offer a named integration and an MCP server. Which to connect depends on who owns the agent, not on the protocol.

Shirley Guo
Shirley Guo
Oct 28, 2026 ·

Updated November 12, 2026: An admin can now connect an MCP server for the whole organization, and organization agents can use it; this post used to say no organization agent could reach one, so its advice and both tables are corrected.

Connect a named integration when its page offers the level the agent needs and its documented tools cover the job, and an MCP server when you need the server’s own tools or the provider has no organization path: both routes can now serve an organization agent. An admin can connect a custom MCP server for the whole organization, and the organization agents an admin adds it to use it with the account the admin signed in with. For a shared agent, that account, not the protocol, is the first thing to settle.

The question comes up because the two lists overlap. The MCP catalog under Settings → Integration offers 77 pre-configured servers, and Notion, Asana, Atlassian, ClickUp and Stripe sit in it beside their own named integrations. Below are the four criteria that decide between them, each route judged on all four, and which reader should pick which.

Two decisions hide inside “MCP server vs integration”

The route you connect by and the protocol behind it are separate decisions, and only the first one is yours. The route is where you connect: a provider’s named card (organization-wide, or under User Integrations for yourself), or Add MCP server under Custom MCP Servers, where Who can use this connection? offers Only me or, to an admin, Organization. The protocol is how the workspace talks to the provider once connected.

Picking the named card does not mean picking “not MCP”. The integrations overview says an integration served by its provider’s own MCP server, such as Datadog, “gives an agent that server’s tools instead”, and those can differ from the tool list on its page. So the real choice is about ownership, tools, where people ask and how access is judged. Whether MCP sits underneath is a detail of each integration.

The four criteria, both routes

CriterionNamed integrationCustom MCP server
Who can own itOrganization, user, or both, per the page’s Org-Level vs User-Level note. Atlassian, ClickUp, Mailchimp, Monday and Google Calendar are user-level onlyOnly me for anyone; Organization when an admin connects it. One connection per provider for each person, plus one for the organization
Which agents can use itOrganization agents through an org-level connection; the built-in assistant and your personal agents through a user-level oneOrganization agents an admin adds it to, through Organization; the built-in assistant and your personal agents, through Only me
Which tools arriveThe built-in tools its page documents, or the provider’s MCP tools where the integration is served that wayEvery tool the server exposes, asked for again each time work starts, so the set changes when the provider changes it
How access levels judge each toolBy the integration’s own definition: each action is marked Read-only or MutatingBy the tool’s name; a name not recognised as a read counts as a change
Where people can askSlack, through the assistant, only if the connection is yours; organization channels only if it is the organization’sThe same: Slack, through the assistant, only on Only me; organization channels only on Organization, through an organization agent
Sign-in and removalAn API key, OAuth app or service account at org level, per page; org-level cards re-check their credential when you open the settings pageOAuth (PKCE) only, so a server offering only a static API key can’t connect; an Organization connection uses the account the admin signed in with, and only an admin can disconnect it; Disconnect does not revoke access at the provider

Who owns the agent, and whose account backs it

An organization agent can use only org-level connections, and a custom MCP server can now be one: an admin connects it for the organization, and the organization agents the admin adds it to use the account the admin signed in with. The agents documentation says org-level agents “cannot access user-level integrations,” and that this includes a custom MCP server: “an org admin can connect one for the whole organization, at the Organization level, so org agents can use it.”

That account is the real decision. When an admin picks Organization, the MCP page says Fours warns that every member can use the server through the org agents an admin adds it to, and that those agents can read, and with Edit or Full access change, the data of that account. Its advice: “Sign in with a shared company account, not a personal one.” The Organization card shows who connected it and when, every member sees it, and only an admin can disconnect it. Editing isn’t supported, so moving it to another account means disconnecting it and connecting it again, a step worth adding to any handover beside transferring ownership of AI agents before someone moves on.

A named integration’s organization path does the same job on the credential its page names. Notion has both paths: an org-level connection through a Notion internal integration token, shown as Notion (API Key), which reads the pages and databases you share with that integration; and a personal one through OAuth. Atlassian and ClickUp are user-level only as named integrations, so a shared agent for Jira, Confluence or ClickUp now goes through an Organization MCP connection: the catalog’s steps let an admin choose Organization for a catalog server, and the only server the MCP page excludes is Fours’ own.

Fours’ own MCP server is that exception. It is built in for the organization, so Add MCP server offers it only as Only me; an org admin adds the built-in connection to an organization agent, where it is listed as Fours MCP with a fixed Edit badge.

For personal agents and the assistant, both routes are open. If you connect Notion both ways, Notion’s page says the user-level connection takes precedence.

Which tools does the agent need?

Compare the integration page’s tool list with what the provider’s MCP server offers, and expect the second to move. A named integration’s page lists its built-in tools; Notion’s groups them as pages, databases, queries, blocks, comments, and search and users. A custom MCP server brings “all tools that the server exposes”, and the workspace asks for them again each time it starts work.

That cuts both ways. The MCP route picks up a provider’s new tools without anyone touching the workspace, which suits exploratory work by one person. It also means a tool an agent relied on last month can be renamed or withdrawn by the provider. For an agent whose instructions name specific actions, the documented list is the steadier base.

Either way, check rather than assume. Every agent can list the actions an integration supports for its current access level and turn, so “which Notion tools can you call?” answers the question for that agent, today.

Where will people ask it?

Slack reaches only the built-in assistant, on the asker’s own connections, so either route works there as long as it is yours; organization channels reach only organization agents, so only an organization connection, named or MCP, works there. A mention of the app in a Slack channel, the agents page says, gets “every tool your connections give it, the MCP servers you connected yourself” included. A custom agent, personal or organization, is not reachable from Slack at all.

Two consequences follow. An org-level Notion token or an Organization MCP connection does not answer in Slack, because the assistant runs on user-scope connections. A personal MCP server does, and everything the assistant answers in a channel is visible to everyone in it, members of another company included in a shared channel. If a question would surface something you would not post there, ask in a direct message.

Inside the workspace, organization channels take organization agents only. A personal connection, MCP or named, never answers there.

How access levels judge each route

Both routes get the same three levels, Read-only, Edit and Full, but they decide differently which tools belong to each. For a built-in tool the integration defines the level: the Actions tab of its Details marks each action Read-only or Mutating, and a mutating one needs Edit, or Full when it removes something. For a server added under Custom MCP Servers, the level is read from the tool’s name, and a name the workspace doesn’t recognise as a read counts as a change.

In practice, Read-only on a custom MCP server keeps the tools whose names look like lookups and drops the rest, including a harmless read with an unusual name. An integration you never narrow runs at Full. And if the levels can’t be read when a turn starts, the assistant runs that turn with every integration at Read-only. The MCP server security checks cover narrowing a third-party server in more depth.

Provider by provider

Each overlapping provider’s catalog server can now serve a shared agent through an Organization MCP connection; a named integration adds a second organization path only where its page offers one.

ProviderNamed integrationIn the MCP catalogWhat that means
NotionOrg-level (internal integration token) and user-level (OAuth)YesOrg token or an Organization MCP connection for a shared agent; OAuth or MCP for your own
AtlassianUser-level onlyYesA shared agent only through an Organization MCP connection; compare tool lists
ClickUpUser-level onlyYesA shared agent only through an Organization MCP connection; compare tool lists
AsanaNot on the user-only listYesCheck its Org-Level vs User-Level note, or connect its MCP server for the organization
StripeYes, with more than one connectionYesCovered in choosing a connection for an AI agent for Stripe

Which reader picks which

The admin building a team agent picks the named integration where it has an org path and its documented tools cover the job, and an Organization MCP connection where it has none, as for Atlassian and ClickUp, signing in with a shared company account rather than their own.

The power user working alone can pick the MCP server with Only me when it exposes something the named integration lacks, then narrows it on each personal agent and remembers that Disconnect leaves the provider’s grant in place.

The reviewer who needs a predictable Read-only agent prefers the named integration, where each action’s level is defined rather than inferred from its name.

Someone who will mostly ask from Slack can use either personal route; what matters there is the channel’s audience, not the protocol.

What neither route settles for you

The workspace decides who gets a connection and how far each agent may go with it; the provider’s side stays yours. After disconnecting a custom MCP server, revoke the grant in the provider’s own app settings. What a sign-in grants, which account an admin signs in with for the organization, which Notion pages are shared with an integration token, and whether a provider renames its MCP tools are decided outside the workspace too.

The integration list on each Insulin agent is where these choices meet: one access level per connection, set for that agent alone.

Sources

Primary sources for the platform rules cited above. Last verified November 12, 2026. Providers change their products, prices and terms without notice — check the source before relying on a detail.

  • Integrations — Fours Doc — Org-level and user-level connectors, with Atlassian, ClickUp, Mailchimp, Monday and Google Calendar user-level only; the MCP connector for yourself or, as an admin, for your whole organization's agents; Connection health on org-level cards, API-key connections only confirmed as present; Agent access levels: Read-only, Edit and Full, Full when never narrowed, an integration served by its provider's own MCP server (such as Datadog) giving that server's tools instead of the documented list, built-in actions marked Read-only or Mutating on the Actions tab, and tools from an MCP server you add yourself judged by their names
  • Integrations MCP (Model Context Protocol) — Fours Doc — MCP server connections at two levels, chosen under Who can use this connection? in the catalog and custom-URL flows: Only me, for that user's own agents and Fours AI chats, or Organization, which only an admin can choose and which the organization agents an admin adds it to use with the account the admin signed in with; Fours' warning that every member can use it through those agents, and to sign in with a shared company account, not a personal one; Organization cards showing who connected them and when, seen by every member and disconnected only by an admin; Fours' own server built in for the organization and offered only as Only me; a catalog of 77 pre-configured servers including Asana, Atlassian, ClickUp, Notion and Stripe, or any custom URL; OAuth (PKCE) only, the server needing OAuth 2.1, so client-credentials or static-API-key servers can't be connected; no separate Verify step; editing not supported; one connection per provider for each user, and one more for the organization; Disconnect not revoking access on the provider side; Fours AI asking the server for its current tools each time it starts work
  • Integrations Notion — Fours Doc — Org-level access through a Notion internal integration token, shown as Notion (API Key), with pages and databases shared with that integration; user-level access through OAuth; user-level taking precedence when both are connected
  • Insulin Agents — Fours Doc — Org-level agents created only by org admins and using only org-level integrations, a custom MCP server an org admin connected at the Organization level included; Fours' own MCP server added to organization agents by an org admin, listed as Fours MCP with a fixed Edit badge; user-level agents using user-level integrations, the system agent user-scope ones; the access table and the Read-only fallback when levels can't be read; an agent listing the actions it may call; Slack: a channel mention getting every tool your connections give the assistant, the MCP servers you connected yourself included, and a channel answer visible to everyone in it

Browse every post on the Insulin Blog

Stay Updated

New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.

Follow Fours on LinkedIn