How to add a Privacy Policy URL to a Claude connector listing

Who this is for

• Developers submitting a remote MCP server or MCP App to the Connectors Directory
• Teams whose submission was flagged for a missing or incomplete privacy policy
• Agent builders who want the policy created by an agent, not by hand

Not for

• Local MCP servers (the directory no longer lists them on their own; they go inside a plugin)
• A guide to OAuth 2.0 or dynamic client registration

What the platform requires

• The Listing step asks for a documentation URL, a privacy policy URL, a support contact, an icon and a permanent URL slug.
• The server must be remote and reachable over https://; tools that act on a user's account use OAuth 2.0, and every tool needs a title and a readOnlyHint or destructiveHint annotation.
• The policy must cover data collection practices, usage and storage, third-party sharing, data retention and contact information. Missing or incomplete policies result in rejection.
• You provide test account credentials and confirm you have run every tool yourself; a Data handling step asks whether the API is your own, a partner's or a third party's.

Step-by-step: paste your privacy policy URL

1. Create the hosted privacy policy URL. Generate it as API/SDK with the connector's name, the data its tools read and write, retention and a support contact. Copy the live URL.
2. Put the same URL in your docs and README. Reviewers and users reach the policy from the listing and from your documentation. Link it from the documentation URL you will submit and from the server's README.
3. Open the developer portal and connect the server. At claude.ai/directory/manage choose Submit new, then MCP connector. Paste the https:// server URL or pick a custom connector you already added to Claude.
4. Fix tool annotations if the Tools step flags them. Every tool needs a title and a readOnlyHint or destructiveHint. Reviewers read tool names and descriptions against the policy, so make the read/write split explicit.
5. Fill the Listing step with the policy URL. Enter the name, one-liner, description, categories, documentation URL, privacy policy URL, support contact, icon and slug. The slug is permanent once published.
6. Complete Data handling, Test & launch and Compliance, then submit. State whose API it is, give reviewer credentials for a populated account, confirm you ran every tool, and accept the seven policy acknowledgments. Status and reviewer feedback appear in the portal.

Field labels to look for

Listing

Documentation URL, privacy policy URL, support contact, icon, categories, permanent slug.

Data handling

Own API, partner API with permission, or third-party API; flags for personal health data and sponsored content.

Compliance

Seven required acknowledgments, including prompt injection and conversation data collection.

Common reasons the form fails

• Policy that does not mention retention or third-party sharing
• Tools missing titles or read/write annotations, which the portal flags before review
• A documentation URL that does not link the policy
• Changing the policy URL between server versions

Create it from inside Claude

This site is itself a remote MCP server (https://www.privacypolicyurl.com/api/mcp) listed in the official MCP registry. Your agent can call create_privacy_policy_url from inside Claude to produce the URL this how-to asks for.

FAQ

Related

• Claude connector (MCP) privacy policy URL (lander)
• Custom GPT privacy policy URL
• Create the URL from your agent (MCP + REST)