allmcps-server

submit_mcp_server

Submit a new MCP server repository to AllMCPs.com for indexing and review, with optional enrichment fields for a complete listing.

Instructions

Programmatically submit a new MCP server repository to AllMCPs.com for indexing and review. Supports the same optional enrichment fields as the human submission form — fill in whichever you can confidently determine from the repository (README, package.json, code) to produce a fully flushed-out listing. Omit anything you are not confident about rather than guessing; all enrichment fields are optional and unrecognized enum values are simply dropped, not rejected.

Input Schema

Name	Required	Description
`url`	Yes	GitHub repository or website URL
`name`	Yes	Server name (e.g., "PostgreSQL MCP")
`tags`	No	Up to 5 short lowercase keywords describing the server (e.g. ["postgres", "sql", "database"]).
`email`	Yes	Contact email for listing verification & status updates
`license`	No	SPDX license identifier or name, e.g. "MIT", "Apache-2.0".
`authType`	No	What authentication the server requires to connect.
`category`	No	Best-matching category from the AllMCPs directory. Must be one of the exact enum values.
`supportUrl`	No	Optional issues/discussions/docs URL for getting help.
`websiteUrl`	No	Optional official website URL
`description`	No	Short summary of what this MCP server does
`pricingModel`	No	How this server is priced/licensed to use.
`pricingNotes`	No	Short free-text pricing detail, e.g. "Free tier up to 1k requests/mo".
`compatibleClients`	No	MCP clients this server is confirmed to work with, from the fixed client slug list.
`maintenanceStatus`	No	Repository maintenance status, inferred from recent commit/release activity.
`suggestedInstallArgs`	No	Args for the install command, e.g. ["-y", "@scope/mcp-server-name"].
`suggestedInstallCommand`	No	Command to run the server, e.g. "npx".

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.2.0Oct 18, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "☁️ Cloud Platforms",
-  "⚖️ Legal",
-  "🌎 Translation Services",
-  "🌐 Social Media",
-  "🌳 Environment & Nature",
-  "🎓 Education",
-  "🎙️ Podcasts",
-  "🎙️ Speech-to-Text",
-  "🎥 Multimedia Process",
-  "🎧 Support & Service Management",
-  "🎧 Text-to-Speech",
-  "🎨 Art & Culture",
-  "🎮 Gaming",
-  "🎯 Marketing",
-  "🏃 Sports",
-  "🏠 Home Automation",
-  "🏠 Real Estate",
-  "🏢 Workplace & Productivity",
-  "🏭 Industrial & IoT",
-  "👤 Customer Data Platforms",
-  "👨‍💻 Code Execution",
-  "💬 Communication",
-  "💰 Finance & Fintech",
-  "💻 Developer Tools",
-  "📂 Browser Automation",
-  "📂 File Systems",
-  "📊 Data Platforms",
-  "📊 Data Visualization",
-  "📊 Monitoring",
-  "📋 Product Management",
-  "📐 Architecture & Design",
-  "📟 Embedded System",
-  "🔄 Version Control",
-  "🔎 end to end RAG platforms",
-  "🔎 Search & Data Extraction",
-  "🔑 Cryptography",
-  "🔒 Delivery",
-  "🔒 Security",
-  "🔗 Aggregators",
-  "🔬 Research",
-  "🔮 Spirituality & Esoterica",
-  "🖥️ Command Line",
-  "🖥️ OS Automation",
-  "🗄️ Databases",
-  "🗣️ Conversational AI",
-  "🗺️ Location Services",
-  "🤖 Coding Agents",
-  "🤝 Agreements & Coordination",
-  "🧠 Knowledge & Memory",
-  "🧬 Biology & Bioinformatics",
-  "🧮 Data Science Tools",
-  "🚀 Aerospace & Astrodynamics",
-  "🚆 Travel & Transportation",
-  "🛒 E-Commerce",
-  "🛠️ Other Tools and Integrations",
-  "Biology, Medicine and Bioinformatics"
-]New value: +[
+  "☁️ Cloud Platforms",
+  "⚖️ Legal",
+  "🌎 Translation Services",
+  "🌐 Social Media",
+  "🌳 Environment & Nature",
+  "🎓 Education",
+  "🎙️ Podcasts",
+  "🎙️ Speech-to-Text",
+  "🎥 Multimedia Process",
+  "🎧 Support & Service Management",
+  "🎧 Text-to-Speech",
+  "🎨 Art & Culture",
+  "🎮 Gaming",
+  "🎯 Marketing",
+  "🏃 Sports",
+  "🏠 Home Automation",
+  "🏠 Real Estate",
+  "🏢 Workplace & Productivity",
+  "🏭 Industrial & IoT",
+  "👤 Customer Data Platforms",
+  "👨‍💻 Code Execution",
+  "💬 Communication",
+  "💰 Finance & Fintech",
+  "💻 Developer Tools",
+  "📂 Browser Automation",
+  "📂 File Systems",
+  "📊 Data Platforms",
+  "📊 Data Visualization",
+  "📊 Monitoring",
+  "📋 Product Management",
+  "📐 Architecture & Design",
+  "📟 Embedded System",
+  "📦 Delivery",
+  "🔄 Version Control",
+  "🔎 Search & Data Extraction",
+  "🔑 Cryptography",
+  "🔒 Security",
+  "🔗 Aggregators",
+  "🔬 Research",
+  "🔮 Spirituality & Esoterica",
+  "🖥️ Command Line",
+  "🖥️ OS Automation",
+  "🗄️ Databases",
+  "🗣️ Conversational AI",
+  "🗺️ Location Services",
+  "🤖 Coding Agents",
+  "🤝 Agreements & Coordination",
+  "🧠 Knowledge & Memory",
+  "🧬 Biology & Bioinformatics",
+  "🧮 Data Science Tools",
+  "🚀 Aerospace & Astrodynamics",
+  "🚆 Travel & Transportation",
+  "🛒 E-Commerce",
+  "🛠️ Other Tools and Integrations"
+]

changedInput schema / properties / compatibleClients / items / enum

Previous value: -[
-  "claude-desktop",
-  "cursor",
-  "cline",
-  "windsurf",
-  "claude-code",
-  "vs-code"
-]New value: +[
+  "claude-desktop",
+  "cursor",
+  "cline",
+  "windsurf",
+  "claude-code",
+  "vs-code",
+  "zed",
+  "codex",
+  "gemini-cli",
+  "jetbrains",
+  "roo-code",
+  "continue",
+  "lm-studio"
+]

Changed12 schema fields changedv2.0.3Aug 20, 2026

addedInput schema / properties / authType

Added value: +{
+  "description": "What authentication the server requires to connect.",
+  "enum": [
+    "none",
+    "api_key",
+    "oauth",
+    "other"
+  ],
+  "type": "string"
+}

changedInput schema / properties / category / description

Previous value: -"Category (e.g., \"Databases\", \"Developer Tools\")"New value: +"Best-matching category from the AllMCPs directory. Must be one of the exact enum values."

addedInput schema / properties / category / enum

Added value: +[
+  "☁️ Cloud Platforms",
+  "⚖️ Legal",
+  "🌎 Translation Services",
+  "🌐 Social Media",
+  "🌳 Environment & Nature",
+  "🎓 Education",
+  "🎙️ Podcasts",
+  "🎙️ Speech-to-Text",
+  "🎥 Multimedia Process",
+  "🎧 Support & Service Management",
+  "🎧 Text-to-Speech",
+  "🎨 Art & Culture",
+  "🎮 Gaming",
+  "🎯 Marketing",
+  "🏃 Sports",
+  "🏠 Home Automation",
+  "🏠 Real Estate",
+  "🏢 Workplace & Productivity",
+  "🏭 Industrial & IoT",
+  "👤 Customer Data Platforms",
+  "👨‍💻 Code Execution",
+  "💬 Communication",
+  "💰 Finance & Fintech",
+  "💻 Developer Tools",
+  "📂 Browser Automation",
+  "📂 File Systems",
+  "📊 Data Platforms",
+  "📊 Data Visualization",
+  "📊 Monitoring",
+  "📋 Product Management",
+  "📐 Architecture & Design",
+  "📟 Embedded System",
+  "🔄 Version Control",
+  "🔎 end to end RAG platforms",
+  "🔎 Search & Data Extraction",
+  "🔑 Cryptography",
+  "🔒 Delivery",
+  "🔒 Security",
+  "🔗 Aggregators",
+  "🔬 Research",
+  "🔮 Spirituality & Esoterica",
+  "🖥️ Command Line",
+  "🖥️ OS Automation",
+  "🗄️ Databases",
+  "🗣️ Conversational AI",
+  "🗺️ Location Services",
+  "🤖 Coding Agents",
+  "🤝 Agreements & Coordination",
+  "🧠 Knowledge & Memory",
+  "🧬 Biology & Bioinformatics",
+  "🧮 Data Science Tools",
+  "🚀 Aerospace & Astrodynamics",
+  "🚆 Travel & Transportation",
+  "🛒 E-Commerce",
+  "🛠️ Other Tools and Integrations",
+  "Biology, Medicine and Bioinformatics"
+]

addedInput schema / properties / compatibleClients

Added value: +{
+  "description": "MCP clients this server is confirmed to work with, from the fixed client slug list.",
+  "items": {
+    "enum": [
+      "claude-desktop",
+      "cursor",
+      "cline",
+      "windsurf",
+      "claude-code",
+      "vs-code"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / license

Added value: +{
+  "description": "SPDX license identifier or name, e.g. \"MIT\", \"Apache-2.0\".",
+  "type": "string"
+}

addedInput schema / properties / maintenanceStatus

Added value: +{
+  "description": "Repository maintenance status, inferred from recent commit/release activity.",
+  "enum": [
+    "active",
+    "stable",
+    "experimental",
+    "archived"
+  ],
+  "type": "string"
+}

addedInput schema / properties / pricingModel

Added value: +{
+  "description": "How this server is priced/licensed to use.",
+  "enum": [
+    "free",
+    "freemium",
+    "paid",
+    "byok"
+  ],
+  "type": "string"
+}

addedInput schema / properties / pricingNotes

Added value: +{
+  "description": "Short free-text pricing detail, e.g. \"Free tier up to 1k requests/mo\".",
+  "type": "string"
+}

addedInput schema / properties / suggestedInstallArgs

Added value: +{
+  "description": "Args for the install command, e.g. [\"-y\", \"@scope/mcp-server-name\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / suggestedInstallCommand

Added value: +{
+  "description": "Command to run the server, e.g. \"npx\".",
+  "type": "string"
+}

addedInput schema / properties / supportUrl

Added value: +{
+  "description": "Optional issues/discussions/docs URL for getting help.",
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Up to 5 short lowercase keywords describing the server (e.g. [\"postgres\", \"sql\", \"database\"]).",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 5,
+  "type": "array"
+}

Addedv2.0.1Aug 5, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it delivers real behavioral traits beyond the schema: submissions enter an 'indexing and review' process (not instantly live), enrichment is optional, and unrecognized enum values are 'dropped, not rejected' rather than erroring. Missing are details on duplicate-submission handling, auth/rate-limit behavior, and what the submitter receives after posting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, purpose front-loaded, no wasted framing. Minor redundancy: 'all enrichment fields are optional' restates the earlier 'Supports the same optional enrichment fields,' so a small trim is possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter mutation-style tool with no annotations and no output schema, the description adequately covers intent, the optional-enrichment philosophy, and enum-drop behavior. It stops short of explaining the post-submission lifecycle (review outcome, confirmation), which an agent submitting programmatically would plausibly want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 16 parameters, making a 3 the correct baseline. The description frames the optional fields as 'enrichment fields' mirroring the human form and names likely sources (README, package.json, code), but adds no field-level format or enum detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (submit), resource (new MCP server repository), destination (AllMCPs.com), and outcome (indexing and review). It is clearly the only submission-style tool among siblings like search_mcp_servers, boost_mcp_server, and register_mcp_agent, so an agent can distinguish it immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives solid guidance on how to fill inputs ('fill in whichever you can confidently determine... Omit anything you are not confident about'), which is useful, but it never states when to choose this tool over siblings or what prerequisite conditions apply (e.g., whether the server must already be published to GitHub). Usage context is implied by the purpose rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server