Privacy Policy
Last updated: June 11, 2026
Summary
MCP Config Builder is designed to be privacy-first. All configuration editing, validation, and state management happens entirely in your browser. No config data — including server names, commands, environment variables, or API keys — is ever sent to any server.
What data do we collect?
We collect minimal data necessary for the operation of the site:
- Anonymous page views — aggregated visit statistics (pages viewed, referring site, browser type). This data is non-personal and used only to understand which features are most useful.
- Ad impressions — served via Google AdSense. Google may use cookies to serve relevant ads. See Google's Privacy Policy for details.
What data do we NOT collect?
- We do not collect or store your MCP configuration data.
- We do not collect server names, commands, arguments, or environment variables.
- We do not collect API keys, tokens, or secrets.
- We do not use analytics cookies or tracking scripts (beyond AdSense).
- We do not have user accounts, logins, or registration.
URL state (shareable links)
The Builder uses URL query parameters to encode your configuration state. This state is stored in the URL fragment and is never transmitted to our server. When you share a builder URL, the recipient's browser decodes the configuration locally — no server is involved.
Third-party services
- Google AdSense — displays contextual ads. AdSense uses cookies and web beacons to serve targeted ads. You can opt out of personalized advertising at adssettings.google.com.
- Google Fonts — loads the Inter font family. See Google Fonts Terms.
- GitHub API — the build-time spec checker fetches the latest MCP release tag from GitHub's public API. No personal data is sent.
Cookies
This site does not set its own cookies. Google AdSense may set cookies for ad personalization and frequency capping. You can manage cookie preferences through your browser settings.
Changes to this policy
If this privacy policy changes, the "Last updated" date at the top will be revised. Continued use of the site after changes constitutes acceptance of the updated policy.
Contact
If you have questions about this privacy policy, email us at [email protected].