connectors-directory-spec

Standardize tdmcp submissions to the Anthropic Connectors Directory for Codex Desktop Extensions.

30|6|Updated May 25, 2026

Search Tags:#documentation #compliance #anthropic #submission #tdmcp #desktop-extension #connectors-directory

Ready to run

npx skills add https://github.com/Pantani/tdmcp --skill connectors-directory-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: connectors-directory-spec
Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/connectors-directory-spec
Command: npx skills add https://github.com/Pantani/tdmcp --skill connectors-directory-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This spec provides an authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Codex Desktop Extension (MCPB). It details the two submission paths, explains why tdmcp is a Desktop Extension (not a remote connector), and documents every form field, rejection gates, and the local-only compliance narrative.

Core Features & Use Cases

Two submission paths exist for Desktop Extensions: one for remote MCP servers and one for Desktop Extensions; each path has distinct forms and gate criteria.
Clear guidance on why tdmcp must be packaged as an MCPB and how this affects deployment, review, and compliance.
Use cases include drafting, checking, and fixing submissions; ensuring privacy, safety annotations, and public docs alignment.

Quick Start

Review this specification before drafting any Desktop Extension submission to ensure you choose the correct path and meet all gating criteria.

Frequently Asked Questions about connectors-directory-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I submit a Desktop Extension to the Anthropic Connectors Directory?▼

Submitting a Desktop Extension requires choosing the correct MCPB submission path, completing required fields including privacy and docs URL, and passing local-only compliance and rejection gates before review.

What is the difference between remote MCP servers and Desktop Extensions submissions?▼

Remote MCP servers and Desktop Extensions follow distinct submission paths with separate forms and gate criteria tailored to their specific deployment models and local-only compliance requirements.

Why does tdmcp need to be packaged as an MCPB Desktop Extension?▼

Packaging tdmcp as an MCPB Desktop Extension enforces local-only compliance, directly determining deployment constraints, review criteria, and required safety annotations for the Anthropic Connectors Directory.

What are the required fields for an MCPB desktop extension submission?▼

MCPB desktop extension submissions require privacy information, safety annotations, and a public docs URL, ensuring all form fields pass validation and rejection gates during the directory review.

How do I validate a tdmcp submission before review?▼

Validating a tdmcp submission involves checking it against rejection gates, verifying local-only compliance, and confirming all required fields including privacy, safety annotations, and docs URL are complete.

What happens if my Desktop Extension submission fails local-only compliance?▼

Failing local-only compliance triggers rejection gates, blocking your Desktop Extension from directory review until you correct the packaging and required field violations specified in the submission path.