mcp-toolkit-server

A production-quality Model Context Protocol (MCP) server, written in TypeScript, that exposes a small toolkit of everyday utilities as MCP tools, resources, and prompts.

What is MCP?

The Model Context Protocol is an open protocol from Anthropic that standardizes how applications provide context and capabilities to large language models. An MCP server advertises tools (functions the model can call), resources (readable data the model can pull in as context), and prompts (reusable prompt templates). MCP clients — such as Claude Desktop, IDE assistants, or custom agents — connect to servers and let the model use those capabilities.

This server speaks MCP over stdio: the client launches it as a subprocess and communicates via JSON-RPC on stdin/stdout. All logging is therefore sent to stderr so it never corrupts the protocol stream.

Related MCP server: lit-forge MCP server

What this server does

mcp-toolkit-server bundles a handful of self-contained utilities so you can experiment with MCP without external services or API keys. It also keeps an in-memory notes store that is exposed both as tools and as browsable resources.

Tools

Resources

Prompts

Install & build

Requires Node.js 18+.

npm install
npm run build

This compiles src/ to dist/ (with type declarations).

Run

After building, run the compiled server:

node dist/index.js

Or, once published/installed, via the bin entry:

npx mcp-toolkit-server

The server communicates over stdio, so running it directly in a terminal will simply wait for a client to connect. You should see the startup line printed to stderr:

mcp-toolkit-server v0.1.0 running on stdio.

Add it to an MCP client (Claude Desktop)

Add an entry to your claude_desktop_config.json (on Windows this lives at %APPDATA%\Claude\claude_desktop_config.json). Use an absolute path to the built entrypoint:

{
  "mcpServers": {
    "toolkit": {
      "command": "node",
      "args": ["C:\\SourceCode\\mcp-toolkit-server\\dist\\index.js"]
    }
  }
}

Restart the client; the toolkit server's tools, resources, and prompts will then be available.

Development

# Run directly from TypeScript source without building (via tsx):
npm run dev

# Type-check only:
npm run lint

# Run the test suite (Vitest):
npm test

# Watch mode:
npm run test:watch

The pure logic (calculator, text_stats, slugify, base64, hash, and the notes store) lives in dedicated modules under src/tools/ and src/store.ts, and is unit-tested in test/ without requiring a running server.

Project structure

mcp-toolkit-server/
├── src/
│   ├── index.ts          # Entrypoint: create server, register everything, connect via stdio
│   ├── config.ts         # Server name/version constants
│   ├── store.ts          # In-memory NotesStore (shared by tools and resources)
│   ├── resources.ts      # server://info and note://{id} resources
│   ├── prompts.ts        # summarize and code_review prompts
│   └── tools/
│       ├── index.ts      # Registers all tools on the server
│       ├── calculator.ts # Safe arithmetic evaluator
│       ├── text.ts       # textStats + slugify
│       ├── encoding.ts   # base64 + hash
│       └── datetime.ts   # timezone formatting
├── test/                 # Vitest unit tests for the pure logic
├── package.json
├── tsconfig.json
├── vitest.config.ts
├── LICENSE
└── README.md

License

MIT © 2026 Nachimuthu Easwaramoorthy