Skip to main content

MCP Registry Deployment Guide

Complete guide for deploying LangGraph Agent to the Model Context Protocol (MCP) Registry with HTTP/SSE transport support.

Table of Contents

Overview

The MCP Server with LangGraph supports multiple MCP transports:
  • stdio (Standard Input/Output) - For local/desktop applications
  • HTTP/SSE (Server-Sent Events) - For web applications and remote access
The agent is fully compatible with the MCP specification and can be published to any standards-compliant MCP registry.

Transports

The agent supports three MCP transports:
  1. StreamableHTTP (Recommended) - Modern HTTP streaming
  2. stdio - Local/desktop applications
  3. HTTP/SSE (Deprecated) - Legacy Server-Sent Events

stdio Transport

Used by: Claude Desktop, local CLI tools Configuration:
Files:
  • src/mcp_server_langgraph/mcp/server_stdio.py - stdio transport implementation
Used by: Web applications, remote clients, mobile apps, production deployments Why StreamableHTTP?
  • Modern HTTP/2+ streaming
  • Better compatibility with load balancers and proxies
  • Proper request/response pairs
  • Native HTTP streaming without SSE limitations
  • Full MCP spec compliance
Configuration:
Endpoints:
  • POST /message - Main MCP endpoint (streaming or regular)
  • GET /tools - List available tools (convenience)
  • GET /resources - List available resources (convenience)
  • GET /health - Health check
  • GET / - Server info and capabilities
Files:
  • src/mcp_server_langgraph/mcp/server_streamable.py - StreamableHTTP transport implementation
Streaming Support:
  • Set Accept: application/x-ndjson or Accept: text/event-stream for streaming responses
  • Responses are newline-delimited JSON
  • Works with standard HTTP infrastructure

HTTP/SSE Transport (Deprecated)

⚠️ This transport is deprecated in the MCP specification. Use StreamableHTTP instead. Used by: Legacy clients Configuration:
Endpoints:
  • GET /sse - Server-Sent Events stream
  • POST /messages - MCP JSON-RPC messages
  • GET /tools - List available tools
  • GET /resources - List available resources
Files:
  • mcp_server_http.py - HTTP/SSE transport implementation (legacy)

Registry Manifest

manifest.json

Located at .mcp/manifest.json, this file contains:
Key fields:
  • name - Unique identifier for the registry
  • version - Semantic version (semver)
  • transports - Supported transport configurations
  • capabilities - MCP protocol capabilities
  • tools - List of available tools with schemas
  • configuration - Required and optional environment variables

registry.json

Located at .mcp/registry.json, this file contains registry-specific metadata:

Publishing to Registry

Automated Publishing

Use the provided script:
Script workflow:
  1. Validates manifest files
  2. Builds package tarball
  3. Uploads to registry
  4. Generates registry card

Manual Publishing

Client Configuration

Claude Desktop

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json Linux: ~/.config/Claude/claude_desktop_config.json

Web Application (HTTP/SSE)

Python Client (HTTP/SSE)

Testing

Test stdio Transport

Test HTTP/SSE Transport

Test with MCP Inspector

Production Deployment

Deploy HTTP/SSE Server to Kubernetes

Configure Kong for MCP

Key Kong settings for SSE:
  • read-timeout: 86400000 (24 hours)
  • write-timeout: 86400000 (24 hours)
  • Session affinity for SSE connections

DNS Configuration

SSL/TLS

Use cert-manager for automatic certificate provisioning:

Health Checks

Monitoring

Prometheus metrics:
Grafana dashboard queries:

Registry Compliance Checklist

  • Manifest file - .mcp/manifest.json with all required fields
  • Registry info - .mcp/registry.json with metadata
  • stdio transport - Implemented in src/mcp_server_langgraph/mcp/server_stdio.py
  • HTTP/SSE transport - Implemented in mcp_server_http.py
  • Tools - Documented with JSON schemas
  • Resources - Documented and accessible
  • Health checks - /health endpoint
  • Documentation - README, deployment guides
  • Versioning - Semantic versioning (1.0.0)
  • Authentication - JWT and API Key support
  • Rate limiting - Kong integration
  • CORS - Configured for web clients
  • SSL/TLS - Certificate provisioning
  • Monitoring - Prometheus metrics

Resources

Support

For registry-related issues: