Skip to main content
Glama

mcp-starter

Secure, starter MCP server boilerplate with JWT authentication, schema validation, and Docker support.

Built for developers who want to expose AI-compatible APIs to tools like Claude, OpenAI, Sourcegraph Cody, or custom agents using the Model Context Protocol (MCP).

Features

  • JWT-based authentication with tenant isolation

  • Function auto-loading from /functions directory

  • Inline per-function schema validation (via AJV)

  • Dynamic MCP manifest generation (/mcp-manifest.json)

  • Docker container

  • CLI utility to generate JWTs for local testing

  • Health endpoints (/mcp, /healthz)


Related MCP server: MCP Server Templates

Running locally

Clone repo

git clone https://github.com/parmindersk/mcp-starter.git
cd mcp-starter

Run with Docker

docker-compose up

Run from code

pnpm install
pnpm start

Generating a Test Token

node tools/generateToken.js --tenant=acme --secret=supersecure

The --secret value (supersecure) must match the JWT_SECRET defined in your .env or docker-compose.yml.

Testing sample submitFeedback

curl -X POST http://localhost:3000/mcp \
  -H "Authorization: Bearer YOUR_JWT_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "submitFeedback",
    "params": {
      "message": "Love the product!",
      "rating": 5
    }
  }'

You can play around with the body to remove message or give an invalid value for rating to see how validation is working.

Follow SinghSpeak.com for more.

Have feedback or feature ideas? Open an issue or contribute via pull request.

Available Tools

1 tool
hello_toolD

Hello tool

Inputs: name (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly distinct by default.

    Naming Consistency5/5

    The single tool name 'hello_tool' follows a consistent verb_noun pattern (hello + tool). With only one tool, consistency is inherently perfect.

    Tool Count2/5

    A single tool is too few for most practical server purposes, as it severely limits functionality and scope. This feels thin and inadequate for typical MCP server use cases.

    Completeness1/5

    With only a 'hello_tool', the server lacks any meaningful domain coverage. It is severely incomplete, offering no operations for a coherent workflow or domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      A starter template for building MCP servers with support for No Auth, API Key, and OAuth authentication using the Dedalus Labs DAuth framework.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides production-grade starter templates for MCP servers with permission boundaries, integration tests, and eval contracts, enabling rapid development of secure and testable MCP servers.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready MCP server starter with authentication, observability, and a plugin system for building and deploying MCP servers quickly.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A security-first MCP (Model Context Protocol) backend built with Node.js and Express, featuring hardening, rate limiting, structured logging, and Docker support.
      MIT