Getting Started: Simplified Setup & Robust MCP Performance

Kickstart Golang MCP servers with this starter example—simplified setup, robust performance, and accelerated progress.

Visit Repository

✨ Developer Tools

4.6(51 reviews)

76 saves

35 comments

This tool saved users approximately 11168 hours last month!

About Getting Started

What is Getting Started: Simplified Setup & Robust MCP Performance?

Imagine setting up a messaging framework that usually takes days, done in under an hour. This guide walks you through installing and testing LiteLLM’s MCP implementation alongside tools from mark3labs. Focus is on streamlining dependencies, reducing friction with Go-based server/client pairs, and verifying performance via Python bridges—all while avoiding the rabbit holes of version mismatches.

How to use Getting Started: Simplified Setup & Robust MCP Performance?

Install essentials: Go 1.24.1 and uv (we prefer uv for managed Python environments)

Bootstrap Python env:

uv venv --python 3.13 && source .venv/bin/activate

Dependency dance:
- Client/server folders get their Go deps via go mod download
- Bridge requirements handled via pip install in the bridge directory
Launch options:
- Local dev: Run Go server (go run main.go) + client
- Production mode: Docker compose in the bridge folder

Getting Started Features

Key Features of Getting Started: Simplified Setup & Robust MCP Performance?

Transport flexibility: SSE over HTTP (works with legacy systems)
Language agnosticism: Go backend + Python frontend showcase
Fail-safe setup: Explicit dependency checks prevent hidden breakages
Diagnostic readiness: Logging baked into client/server endpoints

Use cases of Getting Started: Simplified Setup & Robust MCP Performance?

API gateway prototyping with minimal overhead
Performance benchmarking across MCP implementations
CI/CD pipeline integration for messaging layers
Teaching scenario for MCP concepts (clear separation of components)

FAQ from Getting Started: Simplified Setup & Robust MCP Performance?

Why Go for the server?: Lightweight, fast startup, and excellent HTTP/2 support out of the box
Can I skip Docker?: Yes, but manual dependency management becomes your responsibility
Python version matters?: 3.13 is required for uv compatibility—don’t downgrade unless necessary
Where’s the magic happen?: In bridge/litellm_client.py—that’s where MCP meets real-world SDKs

Getting Started FAQ

Final Notes

While this setup prioritizes simplicity, remember: error messages are your friends. If Go modules get tangled, a go clean -modcache might save your day. And when in doubt, check the original PR for implementation context. Happy protocol hacking!

Content

Getting Started

This project tests the initial LiteLLM MCP implementation with a few other MCP servers and clients. In particular the go-based mcp server and client from mark3labs

Requirements

You need to have the following installed

go 1.24.1
uv

Setup deps

uv venv --python 3.13
source .venv/bin/activate # windows -- source .venv/Scripts/active
uv pip install -r bridge/requirements.txt

# cd into each and install dependencies
cd client;go mod download; cd ..
cd server; go mod download; cd ..

Setup litellm proxy

Or via docker

cd bridge
docker compose up

Running MCP Go server

cd server
go mod download
go run main.go -t sse -p 8080 # transport over http network with port 8080

Running MCP Go client

# run go mcp server first on sse transport
cd client
go run main.go -mcpUri 'http://localhost:8080/sse' # connect to mcp server on uri

Testing Litellm sdk MCP client

# run go mcp server first on sse transport

# run client
cd bridge
python litellm_client.py