UTCP Documentation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_PATH | No | Path to UTCP documentation directory (default: current directory) | . |
| LOG_LEVEL | No | Logging level | info |
| SERVER_NAME | No | Server name for MCP | utcp-docs |
| OPENAI_API_KEY | No | OpenAI API key (required for ask_utcp_expert tool) | |
| SERVER_VERSION | No | Server version | 1.0.0 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_utcp_docsB | Search UTCP documentation for specific topics, protocols, or concepts. Returns relevant documentation sections with excerpts. |
| validate_utcp_manualA | Validate a UTCP manual against the v1.0.1 specification. Returns validation errors and warnings. |
| generate_utcp_manualB | Generate a UTCP manual template for a specific protocol (HTTP, CLI, MCP, SSE, Streamable HTTP) |
| convert_openapi_to_utcpA | Convert an OpenAPI 3.0 specification to a UTCP manual. Automatically maps endpoints, parameters, and authentication. |
| get_utcp_examplesA | Get example UTCP manuals for common use cases (weather API, GitHub API, database, CLI tools) |
| get_best_practicesC | Get UTCP best practices and recommendations for implementation |
| ask_utcp_expertA | Ask a UTCP expert agent (powered by OpenAI) any question about UTCP. The agent has deep knowledge of the entire UTCP specification and will provide detailed, accurate answers with examples and relevant documentation. |
| semantic_search_docsA | Advanced semantic search using RAG (Retrieval-Augmented Generation) over UTCP documentation. Provides enhanced relevance scoring, query expansion, and detailed match reasons. Use this for more sophisticated searches than the basic search_utcp_docs tool. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Complete UTCP Documentation | Full UTCP specification and documentation |
| UTCP Introduction | Introduction to UTCP |
| UTCP Protocols | All UTCP protocol documentation |
| Security Best Practices | Security considerations for UTCP implementations |
| Weather API Example | Example UTCP manual for weather API with authentication |
| GitHub API Example | Example UTCP manual for GitHub API with OAuth |
| Database Example | Example UTCP manual for database queries via MCP |
| CLI Tool Example | Example UTCP manual for command-line tool integration |
| UTCP Manual JSON Schema | JSON Schema for UTCP manual validation |
| Naming Conventions | Best practices for naming tools and parameters |
| Authentication Practices | Best practices for implementing authentication |
| Error Handling Practices | Best practices for error handling |
| Testing Practices | Best practices for testing UTCP tools |
| General Best Practices | General guidelines for UTCP implementation |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes, but search_utcp_docs and semantic_search_docs overlap significantly, both serving documentation search with only detail-level differences. This could cause an agent to misselect.
Names follow a verb_noun pattern consistently (ask_, convert_, generate_, get_, search_, validate_). However, semantic_search_docs deviates slightly by including an adjective before the verb, and the two search tools differ in naming scheme while still being recognizable.
8 tools is appropriate for a documentation and specification server. Each tool addresses a specific need: expert Q&A, conversion, generation, examples, best practices, validation, and two search variants. No tool seems superfluous, and the count is well within the ideal 3-15 range.
The tool set covers the core workflows of interacting with UTCP documentation: asking questions, converting from OpenAPI, generating manuals, retrieving examples and best practices, searching, and validating. Missing a tool for updating or comparing manuals, but the set is largely complete for the server's stated purpose.