You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MCP per person: each colleague's own Notion account
#2015
An MCP binding in Vstorm AgenticOS speaks through one of two accounts:
The organization's account (account: organization) names one of the organization's connections and answers for everybody, on every surface.
Each person's own account (account: personal) names a catalog service instead of a connection. Whoever talks to the agent connects their own Notion under MCP servers → You, and the agent calls Notion as them: in the dashboard, in a direct message and in a channel.
The account is the author of the current message, not of the thread. If Ania asks in #ops, the answer comes from her Notion; if Bartek asks in the same thread, it comes from his, or he is asked to connect one. Notion's own audit log then shows who did what, which a shared service account cannot.
Some consequences:
Where nobody is talking (an API key, the website widget, a schedule, a trigger), there is no account to use. The run continues without that server, and the agent is told which service is missing so it can say so.
In the dashboard chat, a person who has not connected the service gets a connect card when the agent needs it, and the same run continues once they connect.
allowed_tools on the binding is the administrator's ceiling; a person's own connection can narrow it further.
One agent binds each service once. An agent that needs both a shared handbook Notion and each person's own is two agents, or the same server connected twice under two names.
Question: for tools like Notion, GitHub or Jira, should a company agent act through one service account or through each person's own login? What decided it for your team?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
An MCP binding in Vstorm AgenticOS speaks through one of two accounts:
account: organization) names one of the organization's connections and answers for everybody, on every surface.account: personal) names a catalog service instead of a connection. Whoever talks to the agent connects their own Notion under MCP servers → You, and the agent calls Notion as them: in the dashboard, in a direct message and in a channel.The account is the author of the current message, not of the thread. If Ania asks in
#ops, the answer comes from her Notion; if Bartek asks in the same thread, it comes from his, or he is asked to connect one. Notion's own audit log then shows who did what, which a shared service account cannot.Some consequences:
allowed_toolson the binding is the administrator's ceiling; a person's own connection can narrow it further.Details: MCP: whose account a binding speaks through
Question: for tools like Notion, GitHub or Jira, should a company agent act through one service account or through each person's own login? What decided it for your team?
All reactions