Meta MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to listen on when using the streamable HTTP transport (node build/main.js --http). | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_mcp_serverC | Write files for an MCP server based on our discussion with the user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.