Skip to main content
Glama
MCP Toolkit

MCP Toolkit

README.md
# MCP Toolkit

A small, open-source **Model Context Protocol (MCP)** server providing developer utilities over stdio. Zero runtime dependencies; Node.js 20+.

**Current version: v0.3.0** — nine local tools, zero runtime dependencies.

## Tools

| Tool | Purpose |
| --- | --- |
| `json_inspect` | Validate JSON and report the value type, object keys, or array length |
| `text_analyze` | Count Unicode characters, words, and lines |
| `json_pointer` | Look up a JSON value by RFC 6901 pointer (e.g. `/items/0/name`) |
| `url_encode` | Encode or decode URL components without network requests |
| `url_inspect` | Parse an HTTP(S) URL without fetching it |
| `sha256_hash` | Compute SHA-256 of UTF-8 text (hex output) |
| `base64_convert` | Encode UTF-8 or decode strict Base64 UTF-8; `operation` is `encode` or `decode` |
| `json_format` | Format JSON with `indent` from 0 (minified) to 8 (default 2) |
| `timestamp_convert` | Convert timezone-qualified ISO 8601 strings or Unix **milliseconds** into UTC ISO and Unix seconds/milliseconds |

## Quick start

```bash
git clone https://github.com/logicnestxvoidlure/mcp-toolkit.git
cd mcp-toolkit
npm test
npm start
```

Configure a local MCP client to launch the server over **stdio** (replace with the absolute path of your checkout):

```json
{
  "mcpServers": {
    "mcp-toolkit": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-toolkit/src/server.js"]
    }
  }
}
```

The server handles MCP JSON-RPC 2.0 messages over newline-delimited stdio, with `initialize`, `ping`, `tools/list`, and `tools/call`. The supported protocol version is `2025-03-26`. HTTP transport is not implemented.

## Try a tool

Using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector):

```bash
npx @modelcontextprotocol/inspector node src/server.js
```

Connect using stdio, list tools, and call `sha256_hash` with `{ "text": "abc" }`. The resulting SHA-256 hex digest starts with `ba7816bf`.

`url_inspect` only parses URLs and never makes network requests. `timestamp_convert` requires a timezone in ISO strings; numeric timestamps are Unix milliseconds. Base64 decoding rejects malformed Base64 and invalid UTF-8.

Example inputs: `json_pointer` takes `{ "json": "{\"a\":1}", "pointer": "/a" }` and returns `{ "value": 1 }`; `url_encode` takes `{ "text": "hello world", "operation": "encode" }` and returns `{ "operation": "encode", "result": "hello%20world" }`.

## Contribute

New contributors are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) and browse [good first issues](https://github.com/logicnestxvoidlure/mcp-toolkit/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). Start with a small change, run `npm test`, and open a pull request describing what you changed. Contributions are reviewed for correctness and maintainability; no prior MCP experience is required for documentation and test improvements.

## Development

Run `npm test` (Node.js 20+). GitHub Actions tests Node.js 20, 22, and 24. See [CONTRIBUTING.md](CONTRIBUTING.md).

## Roadmap

- More developer integrations and better argument validation
- Better MCP compliance and integration tests
- npm publishing after release validation

## Security

Tools run locally, do not fetch URLs, and do not send input to external services. Avoid passing secrets to third-party MCP clients. Stdout is reserved for protocol messages.

## License

[MIT](LICENSE)

TDQS

B3.3/5.0

Scored across 9 tools

Disambiguation4/5

Each tool targets a distinct operation, and the json_* family is reasonably separated into inspect (structure/validation), format (pretty-print/minify), and pointer (value lookup). Minor friction remains between json_inspect and json_format since both parse JSON, and the encode/decode pairs (base64_convert, url_encode) require reading descriptions to know direction is toggled by a flag.

Naming Consistency4/5

Nearly all names follow a consistent snake_case subject_verb pattern (json_inspect, text_analyze, url_encode, timestamp_convert). The exceptions are json_pointer, which is noun_noun with no verb, and sha256_hash, where the verb is inverted, but both remain readable and unambiguous.

Tool Count5/5

Nine tools is well within the ideal 3-15 range and every tool maps to a distinct, frequently needed utility operation. Nothing feels padded or redundant within the set.

Completeness4/5

The surface covers common text/JSON/encoding/timestamp/URL chores with both encode and decode directions for Base64 and URL, plus URL and JSON inspection. Gaps exist for adjacent frequent needs like other hash algorithms (MD5/SHA-1), HMAC, UUID generation, or regex operations, but core workflows have no dead ends.

Maintenance

ActivityMaintained
ResponsivenessOutdated data