Skip to content
Back

Privacy policy

Version 1.9.3 · 2026-11-17

This policy describes which data OnlyMCP processes, for what purpose, and what rights you have. It follows the Swiss Data Protection Act (revFADP) and, where applicable, the EU General Data Protection Regulation (GDPR).

Controller

Francesco Palazzo, contact details in the legal notice.

What OnlyMCP is

OnlyMCP is a cloud workspace for AI coding agents. You connect your own MCP client (for example Claude Code, Codex or Antigravity) to OnlyMCP through a single endpoint and get your skills, agent definitions and structured memory synced across devices. What your AI client does with that content is outside OnlyMCP. See the AI notice.

Data processed

Account data: email address, name, password as a hash (the password itself is never stored), and which versions of the terms of service and of this privacy policy you accepted, and when.

Sign-in data: sessions with IP address and user agent. When signing in via GitHub or Google, additionally the identity confirmed by that provider.

Device and API tokens: for access through your MCP client, only a SHA-256 hash of the token is stored, never the token itself. On first use, the OnlyMCP CLI creates a random identifier (a UUID, not derived from any data of your computer), keeps it in a file on your computer and sends it to OnlyMCP, which stores it with your device in the Sessions and devices list so that signing in again from the same computer stays the same device and does not create a new one. The CLI also sends the name of your computer and, where it can be read, its model; OnlyMCP stores them as the device's name and platform in the same list, and only you see them.

Your content: the skill files, agent definitions and memory files (Markdown with frontmatter and wiki-links) you create in OnlyMCP. They reside exclusively in the database (Postgres), never on a filesystem. So that the search also finds a memory file by its meaning, OnlyMCP computes a numeric fingerprint of each memory file on its own servers, with a language model that runs there, and stores it beside the file. No text goes to an outside service for this, and the fingerprint is deleted with the file.

History and trash: OnlyMCP keeps a history of the changes to your content, and deleted content stays in the trash for a while. See the sections Content in a team, History of your content and Trash below.

Event log: a list of what was read, searched, listed, changed, moved or deleted in your account and of what happened to your MCP connections. Entries arise in three ways:

  • Calls your clients make through OnlyMCP's hosted MCP endpoint (with a token or an OAuth authorization): access to memory files, skills and agents, showing, creating, changing and deleting your attached MCP connections, and calls to tools, resources and prompts of an attached third-party MCP server. A call to a third-party server is also recorded when that server does not answer.
  • The API that the dashboard and the local npm server use. Only these operations are recorded there: opening a memory file, saving memory, skills, skill files and agents, and the loading of an agent definition by the npm server.
  • OnlyMCP's own checks of your connections: every successful discovery of a connection's tools that you or a client trigger, and a failed regular health check, which is recorded only when a connection fails that worked before.

An entry holds the kind of operation, its target, the device or access route (not always present) and the time. The target is the name or path of the content or connection, for a search the search query (cut to 200 characters), for a tool of a third-party MCP server its name in the form connection/tool, for a resource its address in the form connection/address (which the third-party server supplies and which may itself name something, such as a repository or a file path), and for a prompt its name in the form connection/name. For hosted calls the device is the value mcp-http. When a memory file is saved through the API it is web in the dashboard, the name of your computer for the local npm server, and for the import upload the label sent along with it; otherwise it stays empty. The arguments of a call and its results are not stored: neither the content a client reads or writes, nor what a third-party tool returns, nor an IP address or a user agent.

Not recorded are rejected or invalid calls, a deletion that deleted nothing, and the list and connection messages of the MCP protocol itself. Through the API, nothing is recorded beyond what is named above, such as deleting, moving, listing and searching.

If a client repeats the same read action on the same target through the hosted endpoint within 30 seconds, this results in one entry. Read actions are reading, searching and listing, looking up a tool schema, reading a resource and fetching a prompt. A tool call to a third-party MCP server counts as a read action only if that server marks the tool as read-only and the server comes from OnlyMCP's built-in list. Everything else is always an entry of its own: writing, deleting, moving, changes to connections, OnlyMCP's own checks, the loading of an agent, and everything recorded through the API.

The log exists so that you can follow in the activity view what your clients have done; only you see it there. It is deleted after 90 days, earlier together with your account.

Audit log: administrative and security-relevant actions on your account, with the IP address they came from.

OAuth authorizations: when you connect a chat client such as Claude.ai or ChatGPT through OAuth, the client's registration, your consent and the tokens issued to it.

Billing data: when a paid plan is used, the data required for that. See the third parties section below.

MCP connections: when you attach third-party MCP servers, we store the name, address, transport and the list of capabilities found there. A credential you store for it, and the OAuth tokens you obtain when you authorize it, are kept encrypted (AES-256-GCM), decrypted only immediately before a call and never returned to any client; of a stored credential only the last four characters are visible. The content flowing through such a connection is not stored - it is passed through. For each access route of the hosted endpoint (a token or an OAuth authorization) we also store the short names (prefixes such as github) and the internal identifiers of the MCP connections of your account and your teams that this client could see when it fetched its tool list, in any state, and when the last addition was made, but nothing else from the request: no tool names, no arguments, no IP address. This list only grows, nothing is removed, until the account is deleted, and it is deleted with the account. It serves only to protect a block that you set in your client: connection_call and connection_tool_schema reach only a connection that was newly added after this client's most recent fetch. A tool that your client already knows is called by it directly, and there the approvals and blocks of your client apply.

Newsletter: the entry for your subscription only if you subscribe; in addition, a single timestamp on your account, see the newsletter section below.

Contact form: only if you use it, see the contact form section below.

Audience measurement: data about how the public pages are used and how the tutorial videos are played, on our own server and without cookies, see the Audience measurement section below.

  • Performance of contract: operating the platform, syncing your content, the history and the trash of your content, billing, and the record of which versions of these documents you accepted.
  • Legitimate interest: security, abuse prevention, troubleshooting, technical logs, answering messages sent through the contact form, and measuring how the public pages are used, and a few tips by email on getting started in the first week after you sign up, which you can switch off at any time in the email settings.
  • Consent: the newsletter, if you subscribe to it.
  • Legal obligation: retention of billing-relevant data.

Newsletter

OnlyMCP sends its newsletter only to addresses that asked for it and confirmed that request (double opt-in). After you subscribe, whether on the website, during registration, in your account settings or by answering Yes to the one-time question on your first visit to the dashboard, you receive an email with a confirmation link, and no newsletter is sent to that address until you click it.

What is stored: your email address, the language you chose, where you subscribed, the wording of the consent you gave and the IP address you gave it from, the times of subscribing, confirming and unsubscribing, and for each mailing whether it was delivered. Three failed deliveries in a row end the subscription.

The one-time question: on your first visit to the dashboard, OnlyMCP asks you once whether you would like the newsletter, provided your email address is confirmed and you have no newsletter entry yet. If you answer, Yes or No, OnlyMCP stores a single timestamp on your account: when you answered, so that the question does not come back. It does not say how you answered and holds no other content. If you do not answer, nothing is stored and the question appears again. If you answer Yes, the double opt-in begins as described above, with the wording of the consent shown with the question. The timestamp is deleted with your account, even if you never subscribe to the newsletter. It is stored on the basis of the legitimate interest in not asking you the same thing repeatedly.

Purpose and legal basis: sending the newsletter, on the basis of your consent; keeping the record of that consent, on the basis of the legitimate interest in being able to prove it, also after you withdraw it.

Unsubscribing: every newsletter contains a link that unsubscribes you with one click, and email programs that support it offer the same through the List-Unsubscribe header. You may also withdraw your consent at any time by writing to the address in the legal notice.

Retention: the entry is kept while you are subscribed. A subscription that is never confirmed stays pending and receives nothing further. After you unsubscribe, the entry stays as the record of the consent you gave and withdrew. Your email address and IP address remain in it for 3 years after you unsubscribe; then the address is replaced by a one-way hash and the IP address is removed: the record remains, your address does not. Subscribing again later starts a new double opt-in.

Giveaways: the newsletter may announce a giveaway of a plan trial. Winners are drawn at random among confirmed subscribers who have an account and no paid plan or running trial; a winner's account receives the trial and the winner is told by email. Nothing is passed on to anyone for the draw; the email to the winner is sent like every other email (see Third parties). The record of a win is deleted with the account.

Contact form

Through the contact form on the website you can write to the operator, whether you have an account or not. The operator reads your message in OnlyMCP's administration area and answers you personally by email; no automatic confirmation is sent to the address you give.

What is stored: the email address you give, the topic you chose, your message, the language of the page and the time, and your account if you are signed in when you send it. To limit abuse, your IP address is also kept as a counter for about an hour, and a one-way hash of your email address for about a day.

Purpose and legal basis: answering your message, on the basis of the legitimate interest in being able to answer enquiries, and, where it concerns your account or your plan, the performance of contract.

Where it is kept: only in OnlyMCP's database, where the operator reads the message in the administration area. The message itself is not sent by email and is not passed on to anyone.

Retention: a message is deleted after 12 months, or earlier if you ask (a message to the address in the legal notice is sufficient). If you delete your account, the messages you sent while signed in are deleted with it, and so are those received under its email address.

Content in a team

If you move a skill, an agent definition or a memory file into a team, the content becomes visible to the members of that team, as far as their rights in the team allow them to view that kind of content (by default they allow it for all members). New memory files whose path lies under a folder shared with a team are stored in that team if you may create memory files there, also when your MCP client creates them. If content is returned from the team, whether by you or by a member who may delete it, it is private again, with the person who created it. The same happens to all content of a team when the team is deleted.

Team audit log: on a plan with this feature, a team keeps a log of what happens in the team: invitations sent and cancelled, members who joined, left or were removed, changes to a member's role or permissions, to the team's name and to its trash period, and connections created, changed or deleted in the team. An entry holds the kind of action, the time, the account that acted, and what it concerned: the invited email address, the member, the name of the connection, or the changed value, such as the new name, the new role or the number of days. No IP address is stored there. Together with the history of the team's content (see below) it is shown to the team's owner and admins in the team's settings under Audit log; the other members do not see it. It exists so that the team can follow who did what in it, on the basis of the performance of contract. An entry is deleted as soon as it is older than 12 months; the whole log is deleted with the team. If you delete your account, your entries stay in the logs of your former teams without the reference to your account and then read "A former member".

History of your content

OnlyMCP keeps a history of every memory file, skill and agent definition, which you can open in the content's view under History. It records changes made in the dashboard and through an MCP client alike.

What is stored: for each change its kind (created, edited, moved, moved into a team or returned from a team, deleted, restored), the time, the account that made it, the team the content belonged to at the time, and the path or name of the content at that time. For a move the old and the new path are in the entry, for a change to a companion file of a skill the path of that file.

The text after a change: when content is created, edited or restored, the history also keeps the text as it stands after that change (the memory file, the skill's SKILL.md, or the agent definition; the companion files of a skill are not kept). It stays with the entry for the same 12 months, is visible to the same people as the history, and is deleted with the entry and with the content. At most 50 such versions are kept per content, and their total size per account is limited; the oldest versions are deleted first. These versions do not count towards your plan's storage.

Purpose and legal basis: showing you and, for content in a team, its members what changed, when and by whom, on the basis of the performance of contract.

Who sees it: whoever may see the content itself: you, and for content in a team the members who may see that kind of content. They see the person who acted by name (by email address if that person gave no name); for your own changes it says "You". The entries from the time before content came into a team are not seen by the team's members.

Retention: an entry is deleted as soon as it is older than 12 months; this happens automatically once a day. When content is deleted for good (see Trash), its history is deleted with it.

When an account is deleted: if you delete your account, the history of the content that belongs to you is deleted. In the histories of content that belongs to others, your entries remain, but the reference to your account is removed from them: they then read "A former member". If you only leave a team, your account stays linked to your entries in the history of that team's content, but the other members see "A former member" there as well.

Trash

If you delete a memory file, a skill or an agent definition, it is not deleted at once but moved to the trash, in the dashboard as well as through an MCP client.

What is stored: a complete copy of the deleted content, for a skill with its companion files, together with its path or name, the time of deletion, the account that deleted it, and the date on which the copy is deleted for good.

Purpose and legal basis: so that you can restore deleted content, on the basis of the performance of contract.

How long: 3, 7 or 30 days; the default is 7 days. You set the period for your own content in the settings, and a team sets the period for its content in its own settings. It applies from the moment of deletion: if the setting changes later, content already in the trash keeps its date. Until then the content can be restored: by you as its owner and, for content in a team, by every member who may delete that kind of content. After that it is deleted for good automatically (checked once a day). Whoever deletes it for good in the trash, or empties the trash, deletes it at once. When content is deleted for good, the copy and the content's history are deleted.

Who sees it: whoever could see the content before it was deleted: you, and for content in a team the members who may see that kind of content. They can also view the content of the copy there.

When an account or a team is deleted: if you delete your account, the trash of the content that belongs to you is deleted with it at once. In the trash of content that belongs to others, the reference to your account is removed, as the person who deleted it and as the person who last changed it; the person then counts as a former member there. The reference to your account is also removed from skills and agent definitions of other people that you last changed. If a team is deleted, its content goes back with its trash to the people who created it: what lay in the team's trash then lies in that person's personal trash, with the previous date of deletion for good.

Third parties

OnlyMCP uses the following services. Operation is not possible without them.

  • GitHub and Google only if you choose to sign in with those providers.
  • Stripe for payment processing of the paid plans. Your card data never reaches OnlyMCP's servers, it is processed directly by Stripe. Stripe is a US-based provider; the transfer relies on EU/CH standard contractual clauses. If you delete your account, your subscription at Stripe is ended and your stored payment methods are removed. Invoices and the associated customer data (name, email address, billing address) remain stored at Stripe for the statutory retention period for business records of ten years (Art. 958f of the Swiss Code of Obligations (CO)).
  • Link (Sold through Link, LLC, a Stripe group company) when you buy a plan online. Link is the seller of the order and processes the order data for its own purposes: payment, customer service, order administration, taxes and legal obligations. When you buy, you can create a Link account; it is optional. If you ask Link to delete your data, this also affects the data at Stripe, and the subscriptions you bought through Link end. Link is based in the US; the transfer is necessary to process your order. More in the Link privacy center.
  • Email delivery via mail.exigo.ch (encrypted with STARTTLS) for verification codes, password resets, team invitations and notices about your plan, and for the newsletter if you subscribe to it.
  • Hosting in a Kubernetes cluster on infrastructure located in Europe.

MCP servers you connect yourself are not services OnlyMCP uses, but services you choose. OnlyMCP calls them on your behalf and has no relationship with their operators; their own terms and privacy policies apply. Details are in the third-party notices.

OnlyMCP uses no third-party analytics service and no advertising. How OnlyMCP measures the use of its public pages on its own server is described in the next section.

Audience measurement

OnlyMCP measures how its public pages are used, on its own server and without cookies. Nothing is stored on your device for this, no third party is involved and no data leaves OnlyMCP's own server.

For each page you view we record the page, the time, the language of the page, the website you came from (only its host name, such as google.com), the campaign values in the address (utm_source, utm_medium, utm_campaign), the country and city derived from your IP address with a database kept on our own server, the device class (desktop, phone or tablet), the browser and operating system derived from your browser's user agent, how long the page was visible, and, on the home page, whether its pricing section was in view.

Unique visitors are counted with a short hash of your IP address and user agent, combined with a random value that changes every day and is deleted after that day. Your IP address and user agent are not stored for this measurement. Once the value of the day is deleted, the hash can no longer be traced back to an IP address, and a visit on another day cannot be linked to it.

Crawlers such as search engines and AI bots are counted as daily totals per bot and file, without personal data.

The public MCP server (/api/mcp-public, and /api/mcp for an app that sends no token and does not sign in), which answers questions about OnlyMCP without a sign-in, is counted as daily totals per client app and kind of request. Of the name a client app gives itself, only the entry of a fixed list that it matches is kept. Callers are counted once a day with a hash of the IP address made in the same way as for unique visitors; the hash is deleted after a day and is not stored with the count. To limit abuse, the IP address is also kept as a counter for about an hour. No question, no search text and no answer is stored.

Sign-ups and checkouts add one to a daily counter for the source of the visit that led to them, for example a search engine or an AI assistant. To find that source, the IP address and user agent of the sign-up or checkout request are hashed in the same way and matched with that day's page views; the hash is not stored with the count. The count itself is not linked to your account.

Where your account came from: when you create an account, we keep on it the source found this way for your first visit of that day from outside the site: its kind (for example a search engine or a social network), the domain of the referring site, the campaign name in the link, and the first page of that visit. No IP address, no hash and no full address of the referring page is kept. In the dashboard we may ask you once how you heard about OnlyMCP; if you answer, your answer is kept on your account as well. We use both to learn which channels bring people to OnlyMCP (legitimate interest). Deleting your account deletes them, and the right to object described under Your rights applies.

Signed-in accounts that are active in the dashboard are counted for a live view of the last five minutes, with a hash that changes every day. Each entry is deleted at most 10 minutes after the account's last dashboard request; no name, e-mail address or account number is kept, only a hash that changes every day.

Tutorial videos: when you play a video of the documentation, we record for that play which video it is and the page view it belongs to (and with it the data above), which parts of the video were played and for how long, how far it got, whether it reached the end, and whether it went on from where your browser had stopped before. While the video plays, your browser confirms every 30 seconds that it is still playing, for a live view of who is watching. How far you have watched each video is also kept in your browser, see the cookie notice; that record itself is not sent.

Video plays and your account: if you are signed in and have accepted version 1.8 or a later version of this policy, a play is also linked to your account, so that we can see which accounts watched which videos and improve the videos and the help we give. For this, the request of the play carries your session cookie. Plays made before that acceptance, or while signed out, stay anonymous. Deleting your account removes the link, and the play remains as an anonymous count. The right to object described under Your rights applies to this link as well.

The purpose is to understand how the site is used and to improve it. The legal basis is our legitimate interest. The data is neither sold nor shared, so there is nothing for Global Privacy Control to opt out of. How long the data is kept is described under Retention. Location data: IP Geolocation by DB-IP.

What your AI client does with your content

OnlyMCP itself runs no AI model and holds no AI access tokens. When you fetch your content through your own MCP client, it is sent to whichever AI provider that client uses. OnlyMCP has neither visibility into nor control over that data flow, and is not responsible for it. See the AI notice.

Retention

Your content is kept until your account is deleted; deleted content stays in the trash until its period ends. The audit log is kept for 12 months, the event log for 90 days. The history of your content and the audit log of a team are kept for 12 months as well. The versions of your content that the history keeps go with their entries. Audience measurement data (pageviews, video plays and the daily counters) is kept for 13 months and deleted every night after that; the daily value used to count unique visitors is deleted after its day, the live entries of signed-in accounts at most 10 minutes after the account's last dashboard request. Billing data is kept for as long as statutory retention periods require, for invoices ten years (Art. 958f of the Swiss Code of Obligations (CO)). Newsletter data is kept as described in the newsletter section, messages from the contact form as described in the contact form section. What happens to the history and the trash when an account or a team is deleted is described in the sections History of your content and Trash.

Your rights

You have the right of access, rectification, erasure and restriction of processing, the right to data portability, and the right to object to processing based on legitimate interest. You may withdraw consent at any time. A message to the address in the legal notice is sufficient. OnlyMCP does not make automated individual decisions with legal effect or a comparably significant impact on you.

Right to complain

In Switzerland you may contact the Federal Data Protection and Information Commissioner (FDPIC). In the EU, the data protection authority of your country of residence.

Data security

Transmission is encrypted (TLS) only. Passwords and device/API tokens are stored as hashes only. Access to production data is restricted to the operator of the platform.

Changes

If this policy changes in a way that needs your consent or reduces your rights, renewed consent is requested. Other changes, such as new descriptions of processing based on legitimate interest, are published with a new version and date. The applicable version is shown at the top of this document.