Skip to main content
Glama
UTCP Documentation MCP Server
by edujuan

UTCP Documentation MCP Server

A comprehensive MCP server that helps AI coding agents understand and implement the Universal Tool Calling Protocol (UTCP)

TypeScript MCP License: MIT

๐Ÿš€ Features

  • ๐Ÿค– LLM-Powered Expert Agent: Ask questions in natural language to an OpenAI-powered agent with deep UTCP knowledge

  • ๐Ÿ“š Documentation Search: Semantic search across complete UTCP specification

  • โœ… Manual Validation: Validate UTCP manuals against v1.0.1 spec with detailed errors

  • ๐ŸŽจ Code Generation: Generate UTCP manual templates for HTTP, CLI, MCP, SSE protocols

  • ๐Ÿ”„ OpenAPI Conversion: Convert OpenAPI 3.0 specs to UTCP manuals automatically

  • ๐Ÿ“ Examples Library: Ready-to-use examples for weather APIs, GitHub, databases, CLI tools

  • ๐Ÿ’ก Best Practices: Built-in guidance for naming, authentication, and implementation

Related MCP server: LockSpec

๐Ÿ“ฆ Installation

NPM

npm install -g utcp-docs

From Source

git clone https://github.com/yourusername/utcp-docs-mcp-server.git
cd utcp-docs-mcp-server
npm install
npm run build
npm link

๐Ÿ”ง Configuration

For Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "utcp-docs": {
      "command": "utcp-docs",
      "env": {
        "DOCS_PATH": "/path/to/utcp-docs",
        "OPENAI_API_KEY": "sk-..."
      }
    }
  }
}

For Cursor IDE

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "utcp-docs": {
      "command": "npx",
      "args": ["utcp-docs"],
      "env": {
        "OPENAI_API_KEY": "sk-..."
      }
    }
  }
}

Environment Variables

Create a .env file or set in your MCP config:

# OpenAI API Key (required for ask_utcp_expert tool)
OPENAI_API_KEY=sk-...

# Documentation path (default: current directory)
DOCS_PATH=.

# Server configuration
SERVER_NAME=utcp-docs
SERVER_VERSION=1.0.0
LOG_LEVEL=info

๐Ÿ› ๏ธ Available Tools

๐Ÿ†• 1. Ask UTCP Expert (LLM Agent)

NEW! Ask an OpenAI-powered agent any question about UTCP:

{
  "tool": "ask_utcp_expert",
  "arguments": {
    "question": "How do I authenticate with bearer tokens?"
  }
}

The agent:

  • Has deep knowledge of the entire UTCP specification

  • Retrieves relevant documentation automatically

  • Provides detailed explanations with code examples

  • Includes source references

  • Offers best practices and guidance

Example Questions:

  • "What is body_template and when should I use it?"

  • "Show me a complete HTTP tool example with OAuth2"

  • "How do I chain CLI commands together?"

  • "Why is my tool name failing validation?"

Requires: OpenAI API key (set OPENAI_API_KEY environment variable)


2. Search UTCP Documentation

Search the complete UTCP specification:

{
  "tool": "search_utcp_docs",
  "arguments": {
    "query": "how to implement HTTP authentication",
    "section": "protocols",  // optional: introduction, protocols, guides, api
    "limit": 5               // optional: max results
  }
}

Example Response:

# Search Results for "HTTP authentication"

## Result 1: HTTP Protocol Authentication
**Section:** protocols
**Relevance:** 45

Authentication in HTTP protocols can be configured using the auth field...

3. Validate UTCP Manual

Validate your UTCP manual against the specification:

{
  "tool": "validate_utcp_manual",
  "arguments": {
    "manual": {
      "manual_version": "1.0.0",
      "utcp_version": "1.0.1",
      "tools": [...]
    }
  }
}

Response:

โœ… Valid UTCP Manual
The manual passes all validation checks and conforms to UTCP v1.0.1 specification.

Or with errors:

โŒ Invalid UTCP Manual

## Errors
- /tools/0/name: Tool name "GetWeather" must use snake_case
- /tools/0/tool_call_template: HTTP template requires a URL

## Warnings
- /tools/0/description: Tool description should be at least 10 characters

4. Generate UTCP Manual

Generate a UTCP manual template:

{
  "tool": "generate_utcp_manual",
  "arguments": {
    "tool_name": "get_weather",
    "description": "Get current weather for a location",
    "protocol": "http",
    "endpoint": "https://api.openweathermap.org/data/2.5/weather",
    "method": "GET",
    "parameters": {
      "location": {
        "type": "string",
        "description": "City name",
        "required": true
      }
    },
    "include_auth": true
  }
}

Supported Protocols:

  • http - RESTful HTTP APIs

  • cli - Command-line tools

  • mcp - Model Context Protocol servers

  • sse - Server-Sent Events

  • streamable_http - Streaming HTTP responses

5. Convert OpenAPI to UTCP

Convert OpenAPI 3.0 specifications to UTCP manuals:

{
  "tool": "convert_openapi_to_utcp",
  "arguments": {
    "openapi_spec": {
      "openapi": "3.0.0",
      "info": { "title": "My API", "version": "1.0.0" },
      "paths": {
        "/users": {
          "get": {
            "operationId": "getUsers",
            "summary": "List users"
          }
        }
      }
    }
  }
}

6. Get UTCP Examples

Get ready-to-use example UTCP manuals:

{
  "tool": "get_utcp_examples",
  "arguments": {
    "use_case": "weather"  // weather, github, database, cli-tool
  }
}

Available Examples:

  • weather - OpenWeatherMap API integration

  • github - GitHub REST API (repos, issues)

  • database - Database query tools via MCP

  • cli-tool - Git command-line wrapper

7. Get Best Practices

Get UTCP implementation best practices:

{
  "tool": "get_best_practices",
  "arguments": {
    "topic": "naming"  // naming, authentication, error-handling, testing, general
  }
}

๐Ÿ“– Resources

The server provides these resources via MCP:

Resource URI

Description

utcp://docs/full

Complete UTCP documentation (9700+ lines)

utcp://docs/introduction

UTCP introduction and overview

utcp://docs/protocols

All protocol documentation

utcp://examples/weather

Weather API example manual

utcp://examples/github

GitHub API example manual

utcp://schema/manual

UTCP JSON Schema for validation

๐Ÿงช Usage Examples

Example 1: Creating a New UTCP Manual

// 1. Generate a template
const result = await callTool("generate_utcp_manual", {
  tool_name: "send_email",
  description: "Send an email via SendGrid API",
  protocol: "http",
  endpoint: "https://api.sendgrid.com/v3/mail/send",
  method: "POST",
  parameters: {
    to: { type: "string", description: "Recipient email", required: true },
    subject: { type: "string", description: "Email subject", required: true },
    body: { type: "string", description: "Email body", required: true }
  },
  include_auth: true
});

// 2. Validate the generated manual
const validation = await callTool("validate_utcp_manual", {
  manual: JSON.parse(result)
});

// 3. Get best practices for authentication
const practices = await callTool("get_best_practices", {
  topic: "authentication"
});

Example 2: Converting Existing OpenAPI Spec

// 1. Read your OpenAPI spec
const openApiSpec = JSON.parse(fs.readFileSync("api-spec.json"));

// 2. Convert to UTCP
const utcpManual = await callTool("convert_openapi_to_utcp", {
  openapi_spec: openApiSpec
});

// 3. Validate the result
const validation = await callTool("validate_utcp_manual", {
  manual: JSON.parse(utcpManual)
});

Example 3: Searching Documentation

// Search for specific implementation details
const results = await callTool("search_utcp_docs", {
  query: "how to handle streaming responses",
  section: "protocols",
  limit: 3
});

// Get an example to reference
const example = await callTool("get_utcp_examples", {
  use_case: "github"
});

๐Ÿ—๏ธ Development

Setup

# Clone repository
git clone https://github.com/yourusername/utcp-docs-mcp-server.git
cd utcp-docs-mcp-server

# Install dependencies
npm install

# Build
npm run build

# Run in development mode
npm run dev

Testing

# Run all tests
npm test

# Run tests in watch mode
npm run test:watch

# Generate coverage report
npm run test:coverage

Project Structure

utcp-docs/
โ”œโ”€โ”€ src/
โ”‚   โ”œโ”€โ”€ index.ts              # Entry point
โ”‚   โ”œโ”€โ”€ server.ts             # MCP server implementation
โ”‚   โ”œโ”€โ”€ types/
โ”‚   โ”‚   โ””โ”€โ”€ utcp.ts           # TypeScript types
โ”‚   โ”œโ”€โ”€ services/
โ”‚   โ”‚   โ”œโ”€โ”€ documentation.ts  # Documentation search
โ”‚   โ”‚   โ”œโ”€โ”€ validator.ts      # UTCP validation
โ”‚   โ”‚   โ”œโ”€โ”€ generator.ts      # Manual generation
โ”‚   โ”‚   โ””โ”€โ”€ converter.ts      # OpenAPI conversion
โ”‚   โ””โ”€โ”€ schemas/
โ”‚       โ””โ”€โ”€ utcp-manual.schema.json
โ”œโ”€โ”€ docs/
โ”‚   โ””โ”€โ”€ examples/             # Example UTCP manuals
โ”œโ”€โ”€ tests/
โ”‚   โ””โ”€โ”€ services/             # Unit tests
โ”œโ”€โ”€ llms.txt                  # Complete UTCP documentation
โ””โ”€โ”€ package.json

๐Ÿ“‹ Requirements

  • Node.js: 20.x or higher

  • TypeScript: 5.3 or higher

  • MCP SDK: 1.0.4 or higher

๐Ÿค Contributing

Contributions are welcome! Please follow these steps:

  1. Fork the repository

  2. Create a feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

Development Guidelines

  • Write tests for new features

  • Follow TypeScript best practices

  • Update documentation for API changes

  • Ensure all tests pass before submitting PR

๐Ÿ“š Resources

UTCP Resources

MCP Resources

๐Ÿ› Troubleshooting

Server Not Starting

Issue: Error: Cannot find module 'ajv-formats'

Solution:

npm install ajv-formats
npm run build

Documentation Not Loading

Issue: Error loading llms.txt

Solution: Ensure DOCS_PATH environment variable points to the correct directory:

export DOCS_PATH=/path/to/utcp-docs

Validation Errors

Issue: Tool names failing validation

Solution: Use snake_case naming:

  • โœ… get_user_data

  • โŒ GetUserData

  • โŒ getUserData

๐Ÿ“„ License

MIT License - see LICENSE file for details

๐Ÿ™ Acknowledgments

  • UTCP Team for creating the Universal Tool Calling Protocol

  • Anthropic for the Model Context Protocol

  • All contributors to this project

๐Ÿ“ž Support


Built with โค๏ธ for the AI development community

Making UTCP implementation easier, one tool at a time.

Available Tools

8 tools
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.

Inputs: question (required), performance_mode.

convert_openapi_to_utcpA

Convert an OpenAPI 3.0 specification to a UTCP manual. Automatically maps endpoints, parameters, and authentication.

Inputs: openapi_spec (required).

generate_utcp_manualB

Generate a UTCP manual template for a specific protocol (HTTP, CLI, MCP, SSE, Streamable HTTP)

Inputs: tool_name (required), description (required), protocol (required), endpoint, +3 more.

get_best_practicesC

Get UTCP best practices and recommendations for implementation

Inputs: topic.

get_utcp_examplesA

Get example UTCP manuals for common use cases (weather API, GitHub API, database, CLI tools)

Inputs: use_case (required).

search_utcp_docsB

Search UTCP documentation for specific topics, protocols, or concepts. Returns relevant documentation sections with excerpts.

Inputs: query (required), section, limit, excerpt_length.

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.

Inputs: query (required), limit, excerpt_length, section, +1 more.

validate_utcp_manualA

Validate a UTCP manual against the v1.0.1 specification. Returns validation errors and warnings.

Inputs: manual (required).

Tool Schema Changelog

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

Loading tool schema changelogโ€ฆ

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Exposes Specmatic's API contract testing, resiliency testing, and mocking capabilities to AI coding agents via natural language, enabling automated validation and simulation of API behaviors.
      3
      49 npm
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with accurate OpenAPI contract details to prevent hallucinated API calls, supporting multi-version pinning, endpoint discovery, and request validation.
      42 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to save, retrieve, and semantically search code snippets, generate language-specific style guides, and produce comprehensive documentation through discoverable MCP tools and multi-agent workflows.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent-planned, human-reviewed HTTP API testing through MCP, turning OpenAPI/Swagger definitions and requirements into executable Hurl/k6 test plans. Supports plan review, execution, cleanup, and reports for coding agents such as Codex and Claude Code.
      MIT