Skip to main content
Glama
enesjakozh
DMontgomery40

Meta MCP Server

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

元 MCP 服务器

“Meta” 是因为它是一个创建 MCP 服务器的 MCP 服务器。也因为“扎克，你真倒霉，我先拿到了”（说真的，虽然我是事后才意识到这一点的）。

特征

AI（较差）创作的内容：

  • 动态服务器生成：允许通过指定要创建的目录和文件来创建定制的 MCP 服务器。

  • 自动化文件管理：自动处理新服务器所需目录和文件的创建。

  • MCP 工具集成：利用模型上下文协议 SDK 高效管理工具和资源。

  • 错误处理：强大的错误管理，即使遇到无效输入或系统错误也能确保稳定性。

  • 调试支持：详细的日志和系统提示，有助于调试和操作透明度。

在 Claude Desktop 中配置

  },
    "meta-mcp-server": {
      "command": "npx",
      "args": ["-y", "meta-mcp-server"]
    }
  }

安全性：此服务器未实施高级安全措施，仅用于开发目的。请确保其在安全的环境中运行，并考虑在生产环境中实施额外的身份验证和验证机制。

Related MCP server: MCP Server Creator

支持

如需支持、功能请求或报告错误，请在 GitHub 存储库页面上打开问题。

执照

MIT 许可证

版权所有 (c) 2024 David Montgomery

特此授予获得此软件和相关文档文件（“软件”）副本的任何人免费许可，以无限制方式处理软件，包括但不限于使用、复制、修改、合并、发布、分发、再授权和/或销售软件副本的权利，并允许向其提供软件的人员这样做，但须遵守以下条件：

上述版权声明和本许可声明均应包含在软件的所有副本或实质性部分中。

本软件按“原样”提供，不附带任何形式的明示或暗示保证，包括但不限于适销性、适用于特定用途和非侵权性的保证。在任何情况下，作者或版权所有者均不对因本软件或使用或以其他方式处理本软件而引起的或与之相关的任何索赔、损害或其他责任承担责任，无论是合同、侵权或其他诉讼。

Available Tools

1 tool
write_mcp_serverC

Write files for an MCP server based on our discussion with the user

ParametersJSON Schema
NameRequiredDescriptionDefault
outputDirYesDirectory where server files should be created
filesYes

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool writes files, implying a mutation operation, but does not address permissions, error handling, file overwriting behavior, or output format. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for the complexity, with no wasted information.

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

Completeness2/5

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

Given the tool's complexity (file writing with nested array parameters), lack of annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It does not cover behavioral aspects, error cases, or detailed usage, making it inadequate for safe and effective tool invocation.

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 50% (only 'outputDir' has a description), and the description does not add any parameter-specific details beyond what the schema provides. It mentions 'files' generally but does not explain the structure or usage of the 'files' array. The baseline is 3 due to moderate schema coverage, but the description fails to compensate for the undocumented 'files' parameter.

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

Purpose4/5

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

The description clearly states the action ('write files') and the target ('for an MCP server'), specifying the purpose as file creation based on user discussion. It lacks explicit differentiation from siblings, but since there are no sibling tools, this is not a deficiency.

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

Usage Guidelines2/5

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

The description provides minimal guidance by mentioning 'based on our discussion with the user,' which implies usage context but does not specify when to use this tool versus alternatives, prerequisites, or exclusions. With no sibling tools, the lack of comparative guidance is less critical, but overall guidance remains vague.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • Addedwrite_mcp_server
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as writing MCP server files based on user discussions, making it distinct by default.

Naming Consistency5/5

The single tool name 'write_mcp_server' follows a consistent verb_noun pattern (write + mcp_server). Since there is only one tool, naming consistency is inherently perfect with no deviations to assess.

Tool Count2/5

One tool is too few for a server named 'Meta MCP Server', which implies a broader scope or meta-level functionality. A single tool feels thin and limited, suggesting the server might be underdeveloped or narrowly focused beyond typical expectations.

Completeness2/5

The tool set is severely incomplete for a meta-level server. It only provides a write function without any complementary tools for reading, updating, deleting, or managing MCP servers, creating significant gaps that will hinder agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches