mcp-http

Teamwork MCP HTTP Server

HTTP transport server for the Teamwork Model Context Protocol implementation

📖 Overview

The Teamwork MCP HTTP Server provides an HTTP interface for the Model Context Protocol, enabling secure and scalable communication between Large Language Models and Teamwork.com. This server implements the MCP specification over HTTP transport, making it suitable for production deployments and cloud environments.

🤖 What is the HTTP Server for?

This HTTP server is designed for:

• Production deployments: Scalable, stateless HTTP-based MCP communication
• Cloud environments: Easy deployment with load balancing and health checks
• Multi-client support: Handle multiple concurrent LLM connections
• Monitoring and observability: Built-in metrics, logging, and tracing

✨ Features

• HTTP Transport: POST-based API implementing the MCP specification
• SSE Transport: GET-based Server-Sent Events for streaming MCP communication
• Health Checks: Built-in health endpoint
• Observability: Comprehensive logging, metrics, and Datadog APM integration
• Production Ready: Designed for cloud deployment with proper error handling
• Stateless: No server-side session management for horizontal scaling

🚀 Quick Start

📋 Prerequisites

• Go 1.27 or later
• Valid Teamwork API credentials
• OAuth2 client configuration

🏃 Running the Server

# Basic HTTP server
TW_MCP_SERVER_ADDRESS=:8080 \
  go run cmd/mcp-http/main.go

# With custom configuration
TW_MCP_URL=https://my-mcp.example.com \
  TW_MCP_SERVER_ADDRESS=:8080 \
  TW_MCP_LOG_LEVEL=debug \
  go run cmd/mcp-http/main.go

🚀 Transport Options

The server supports two transport mechanisms:

POST Transport (JSON-RPC)

Traditional HTTP POST requests to / with JSON-RPC payloads:

curl -X POST http://localhost:8080/ \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"..."}}'

GET Transport (Server-Sent Events)

Streaming SSE connections to /sse with GET requests:

curl -X GET http://localhost:8080/sse \
  -H "Authorization: Bearer <token>" \
  -H "Accept: text/event-stream"

This establishes a persistent connection for bidirectional streaming communication via Server-Sent Events.

🔗 Extended API Endpoints

Besides the MCP endpoints, the HTTP server provides the following extended API endpoints:

⚙️ Configuration

Command-Line Flags

Server Configuration

The server can be configured using the following environment variables:

Logging Configuration

Datadog APM Configuration

🔄 Protocol Compatibility

The server negotiates the highest protocol revision the client also supports, so clients on older spec revisions keep working unchanged. Both handshakes are served: server/discover (SEP-2575) for stateless clients and initialize for everything older. Both bypass authentication, so pre-auth connector setup works either way.

Two wire-level behaviours changed with the 2026-07-28 revision, and the server runs stateless, so they apply here:

If a client turns out to depend on the old behaviour, the SDK ships an escape hatch that restores it without a code change:

MCPGODEBUG=allowsessionsinstateless=1

Set it on the deployment and the server reads Mcp-Session-Id, echoes it back, and answers DELETE with 204 again, exactly as before. It is a temporary compatibility parameter: the SDK removes it in v1.9.0, so treat it as a stopgap while the client is fixed, not a permanent setting. MCPGODEBUG takes a comma-separated list, and the full set of parameters for the pinned SDK version is documented at https://go.sdk.modelcontextprotocol.io/mcpgodebug/ (also in-tree at docs/mcpgodebug.md of the modelcontextprotocol/go-sdk module).

Two further notes for clients:

• The logging capability is no longer advertised. It was deprecated by SEP-2577 and this server never sent a notifications/message, so no client loses functionality. Clients on pre-2026-07-28 revisions can still call logging/setLevel; on 2026-07-28 the SDK rejects it with -32601, as the revision removed the method.
• tools/list responses carry cacheScope: "private". The tool list is filtered per OAuth token scope, so shared intermediaries must not cache it.

🧪 Testing

MCP HTTP CLI

The MCP HTTP CLI is a command-line tool for interacting with the MCP HTTP server. It provides a simple interface for testing API endpoints and performing common tasks.

For more information check here.

🔍 MCP Inspector

For debugging purposes, use the MCP Inspector tool:

NODE_EXTRA_CA_CERTS=letsencrypt-stg-root-x1.pem npx @modelcontextprotocol/inspector node build/index.js

[!IMPORTANT] Note: The NODE_EXTRA_CA_CERTS environment variable is required when using OAuth2 authentication with the Let's Encrypt certification authority. Download the certificate here.

🔍 Monitoring

The HTTP server provides comprehensive monitoring capabilities:

• Health Checks: /health and /ready endpoints for load balancer integration
• Structured Logging: JSON or text format with configurable log levels
• Datadog APM: Distributed tracing and performance monitoring
• Metrics: Built-in metrics for request rates, latencies, and errors