Claude Connectors Directory submission form: all 50 fields across 6 pages

## Problem Submitting an MCP server to Claude Connectors Directory requires filling out a Google Form with ~50 fields across 6 pages. The form structure is not documented anywhere, making it hard to prepare in advance. ## Form Structure (6 Pages) ### Page 1: Introduction No input fields. Links to Software Directory Policy and Terms. ### Page 2: Submission Details (~29 fields) **Company Information:** - Company/Organization Name (required) - Company/Organization URL (required) - Primary Contact Name (required) - Primary Contact Email (required) - Primary Contact Role - Anthropic Point of Contact (if known) **Server Details:** - MCP Server Name (required) — do NOT include "MCP" or "Server" in the name - MCP Server URL type: Universal URL / Custom MCP URLs (required) - MCP Server URL value (required) - Tagline — max 55 characters including spaces (required) - MCP Server Description — 50-100 words (required) - Use Cases + Examples — minimum 3 use cases with prompt examples (required) - Connection requirements (required) — free/paid account, admin rights, region restrictions. Write "No special requirements." if none - Read/Write Capabilities: Read Only / Write Only / Read + Write (required) - Is this an "MCP App" with interactive UI elements: Yes / No (required) - Third-party Connections and Web Access — checkboxes: web access, third-party AI models, third-party data retrieval, third-party data modification, N/A (required) - Data Handling — checkboxes: user-requested data only, no storage beyond session, encrypted HTTPS/TLS, GDPR compliant - Health data access: Yes / No (required) - Categories: Business & Productivity, Communication, Data & Analytics, Development tools, Financial Services, Consumer Health, Health & Life Sciences, Media & Entertainment, Commerce & Shopping, Other - Sponsored content or advertisements: No / Yes (banner ads) / Yes (ranking impacted) (required) **Authentication Details:** - Authentication Type: No auth / OAuth 2.0 / Custom URL (required) - Auth Client: Static OAuth Client / Dynamic OAuth Client (DCR, CIMD) - Static Client ID - Static Client Secret - Transport Support: Streamable HTTP / SSE — checkboxes (required). Streamable HTTP recommended, SSE will be deprecated. **Documentation & Support:** - MCP Server Documentation Link (required) - Privacy Policy URL (required) — displayed in Directory - Data Processing Agreement URL - Support Channel (required) — displayed in Directory ### Page 3: Test Account & Technical Details (~5 fields) - Testing Account Credentials (required) — use mcp-review@anthropic.com if email needed. No 2FA. - Test Account Server URL (if different from main) - Test Account Setup Instructions — must be clear enough for reviewers unfamiliar with the service - Test Data Availability checkboxes: includes sample data / all tools testable - List of tools — comma-separated: `tool_name (human-readable name)` (required) - Tool Titles & Annotations — must check BOTH: user-friendly titles specified AND accurate annotations specified (required) - List of resources (optional) - List of prompts (optional) ### Page 4: Launch Readiness & Media (~7 fields) - Server GA Date — only GA servers are listed - Testing confirmed in: Claude.ai (web) / Claude Desktop / Claude Code / Cowork — checkboxes (required) - Server Logo — square 1:1 SVG URL (required). Google Drive link OK. - Server Logo SVG upload (alternative, max 10MB) - Favicon verification checkbox (required) — verify at `https://www.google.com/s2/favicons?domain=YOUR_DOMAIN&sz=64` - Promotional Images upload (optional, 3-5 recommended, 1000px+ width PNG for MCP Apps) - Link to Promotional Materials ### Page 5: Skills & Plugins (all optional) - Skill Name (100 chars max) - Skill Description - GitHub URL of Skill - Extra Information on Skills - Related Plugins ### Page 6: Submission Checklist (all required) **Policy Compliance (must check all):** - Reviewed and agree to Software Directory Policy - Server does NOT enable cross-service automation - Server does NOT transfer money/crypto/financial transactions - MCP server is live, published, ready for production traffic - You work for the company that owns/controls the API endpoints **Technical Requirements (must check all):** - OAuth 2.0 fully implemented for all authenticated tools - All tools include safety annotations (readOnlyHint, destructiveHint) - Server accessible via HTTPS - CORS properly configured for browser-based auth - Claude.ai and Claude Code IPs allowlisted (if applicable) - Tested with Claude.ai on latest build **Documentation Requirements (must check all):** - Complete server documentation publicly accessible - Docs include setup instructions, tool descriptions, troubleshooting - Privacy policy published and accessible - Terms of service published and accessible **Testing Requirements (must check all):** - Test account with sample data ready - Test credentials valid for at least 30 days - All tools functional and tested - Additional Information (optional free text) ## Key URLs - Remote MCP submission form: https:[MASKED:high_entropy_secret] - Local MCPB form: https://forms.gle/9TkHpiATf7oAvg8g9 - Plugin form: https://docs.google.com/forms/d/e/1FAIpQLSdeFthxvjOXUjxg1i3KrOOkEPDJtn71XC-KjmQlxNP63xYydg/viewform - Submission guide: https://support.claude.com/en/articles/12922490-remote-mcp-server-submission-guide - Software Directory Policy: https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy - Update existing server: email mcp-review@anthropic.com - Review period: approximately 2 weeks (not guaranteed)