mcp-builder-mcp
# mcp-server-demo
MCP server with OpenAPI validation and analysis tools.
## Running the server
Run: `uv run python main.py`
This starts the server on **streamable-http** at `http://127.0.0.1:8000/mcp`. It works locally and behind ngrok or other tunnels with no extra commands or env vars. For Cursor/stdio, use: `uv run python main.py stdio`.
The **validate_openapi** tool accepts file paths, inline JSON/YAML, or any public URL. The tool fetches and reads the content over HTTP (no manual download required). Supported URL types include: raw file URLs (e.g. `raw.githubusercontent.com/.../ProjectSight-v1.json`), Google Drive view or direct download links, and any other public URL that returns JSON or YAML. Both “read the page” and “download” semantics work: the tool GETs the URL and parses the response body.
After validation, the **prompt_mcp_developer_context** tool provides Trimble Agentic Ecosystem context, an inferred market segment and intended end users from the API, and two prompts for the agent creator: (1) the job role of the person adding MCP tools for this API, and (2) the task/workflow/job the agent being created will aid in. Pass either the `analysis` from `validate_openapi` (when valid) or `openapi_input` (URL/path/inline) to get these prompts.
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose within the MCP server generation workflow. Tools like validate_openapi, propose_endpoint_bundles, and generate_mcp_server handle specific sequential steps, while utilities like get_workflow_status and reset_workflow serve unique supporting roles. There is no functional overlap between any tools.
Most tools follow a consistent verb_noun pattern (e.g., validate_openapi, generate_mcp_server, upload_to_github). The exception is send_repo_email_to_user, which uses a verb_noun_preposition_noun structure, slightly deviating from the otherwise uniform naming convention.
With 9 tools, the server is well-scoped for its purpose of guiding users through a 6-step MCP server generation process. Each tool serves a necessary role in the workflow, from validation to deployment, without redundancy or excessive fragmentation.
The toolset provides complete coverage of the MCP server generation lifecycle, including validation, planning, generation, deployment, and communication. It covers all essential steps from OpenAPI validation to GitHub upload and email notification, with no apparent gaps that would hinder an agent's ability to complete the workflow.