MCP Server in Clicks

No‑code SaaS to deploy custom Model Context Protocol (MCP) servers from JSON config. This monorepo includes:

• a production‑ready Go MCP server template (config‑driven, no code changes)
• a Go backend to orchestrate multi‑tenant deployments via Helm on Kubernetes
• a React + Tailwind frontend (SaaS UI)

Highlights

• Config‑driven MCP server using mark3labs/mcp-go
• Dynamic tools: map any HTTP API endpoint (method, headers, query, body)
• Secure auth: Bearer/basic, env var substitution, OAuth 2.0 discovery + challenges
• Input/output validation, robust errors to prevent LLM hallucination
• JSON‑RPC over HTTP for streamable MCP clients (Cursor, Claude, VS Code)
• Dockerized; Helm charts for one‑click per‑tenant deploys
• Backend with JWT auth, Google login (OIDC), MongoDB persistence, Helm Go SDK

Monorepo layout

.
├─ mcp-server-template/     # Go MCP server template (SDK: mark3labs/mcp-go)
│  ├─ cmd/server/           # Main entrypoint
│  ├─ internal/             # config, handlers, server, validation
│  ├─ examples/             # JSON configs (tools/prompts/resources)
│  ├─ deploy/helm/          # Helm chart for MCP server instances
│  ├─ Dockerfile            # Multi‑stage Docker build
│  └─ Makefile              # Build/test/lint/docker/helm
├─ backend/                 # Go backend API + CLI (Cobra, chi, viper)
│  ├─ cmd/                  # CLI entrypoints
│  ├─ internal/             # api, auth, config, helm svc, storage
│  ├─ Dockerfile            # Backend Docker image
│  ├─ k8s.yaml              # Backend Kubernetes manifests
│  └─ Makefile              # Build/test/docker/k8s/helm helpers
└─ frontend/                # React + TypeScript + Tailwind SaaS UI
   └─ (Vite, route guard, auth store, pages)

Prerequisites

• Go 1.23+
• Node 18+/pnpm or npm
• Docker 24+
• kubectl + access to a Kubernetes cluster
• Helm 3.14+

Quick start: run the MCP server locally (binary)

1. Build the server

cd mcp-server-template
go build -o mcp-server cmd/server/main.go

2. Run with an example configuration

./mcp-server --config examples/simple-server.json --port 9090 --log-level debug

3. Smoke test JSON‑RPC

curl -s -X POST http://127.0.0.1:9090/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq

You should see your configured tools. To call a tool, pass parameters via tools/call:

curl -s -X POST http://127.0.0.1:9090/mcp \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc":"2.0",
    "id":2,
    "method":"tools/call",
    "params":{
      "name":"get_quote",
      "arguments":{}
    }
  }' | jq

Tip: To use this server from Cursor/Claude locally, point your client to http://127.0.0.1:9090/mcp (e.g. Cursor’s ~/.cursor/mcp.json).

MCP server template: concepts

• Config first: define tools, prompts, resources entirely in JSON
• Tools map to HTTP endpoints with support for
  • method (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS)
  • path/query templating from input params
  • headers (static or env‑var substituted)
  • auth (bearer/basic/env var)
  • timeouts and retries
• Validation: request inputs and response shapes
• OAuth 2.0 resource hints
  • /.well-known/oauth-protected-resource for discovery
  • WWW-Authenticate challenges on /mcp when enabled

Example configuration (excerpt)

{
  "server": { "name": "example", "version": "0.1.0" },
  "runtime": { "default_timeout": "10s" },
  "security": {
    "oauth": {
      "enabled": true,
      "accepted_audiences": ["your-client-id"],
      "required_scopes": ["read"]
    }
  },
  "tools": [
    {
      "name": "get_quote",
      "description": "Get a random quote",
      "endpoint": "https://zenquotes.io/api/random",
      "method": "GET",
      "timeout": "10s"
    }
  ]
}

Build a Docker image (MCP server)

cd mcp-server-template
docker build -t sanskardevops/mcp-server-template:0.0.1 

... [View full README on GitHub](https://github.com/Sanskarzz/mcp-server-in-clicks#readme)