Skip to main content
Glama

Nockit ⚡

A lightweight, low-latency Model Context Protocol (MCP) server for seamless tool execution and context integration.

npm version license node version


💡 Overview

Nockit MCP bridges the gap between AI assistants (Claude Desktop, Cursor, Zed, etc.) and local development workflows. Built with minimal overhead, it provides fast, reliable tool execution and context bridging over standard input/output (stdio) or HTTP transport layers.

  • 🚀 Lightweight & Fast: Zero bloat, optimized for instant startup and low-latency message relay.

  • 🔌 Plug & Play: Seamless integration with MCP-compatible clients like Claude Desktop and Cursor.

  • 🛠️ Configurable: Simple JSON-based environment configuration.

  • Local & Portable: Works offline out of the box.


Related MCP server: allcanuse-mcp

Installation

You can run nockit-mcp directly using npx or install it globally/locally via your favorite package manager:

Using npx (Recommended)

No installation required:

npx nockit-mcp@latest

Global Installation

  npm install -g nockit-mcp
# or
  pnpm add -g nockit-mcp
# or    
  yarn global add nockit-mcp

Local Project Dependency

  npm install nockit-mcp

⚡ Quickstart

1. Claude Desktop Integration

Add nockit-mcp to your Claude Desktop configuration file:

  • Linux: ~/.config/Claude/claude_desktop_config.json

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

  JSON {
    "mcpServers": {
        "nockit": {
        "command": "npx",
        "args": [
            "-y",
            "nockit-mcp@latest"
        ],
        "env": {
            "NOCKIT_LOG_LEVEL": "info"
        }
        }
    }
  }

Restart Claude Desktop, and the Nockit tools will be available automatically.

2. Running Locally for Development

If you are developing or testing nockit-mcp locally:

# Clone the repository
git clone [https://github.com/username/nockit.p](https://github.com/username/nockit.p)
cd nockit

# Install dependencies
npm install

# Build the package
npm run build

# Link locally for testing
npm link

📲 Auto-Notify (push notifications to your phone)

nockit can push a notification to your phone (ntfy.sh) the moment an AI agent starts waiting on you (needs_input) or finishes a task (completed) — with zero manual tool calls.

# One-time setup: detects installed clients and wires everything up
npx -y nockit-mcp setup

# Check what's configured
npx -y nockit-mcp status

# Manual fallback / one-off push
npx -y nockit-mcp send --status needs_input --summary "Review the PR when you're back"

nockit setup installs:

Client

Mechanism

Events pushed

opencode

plugin (~/.config/opencode/plugin/) + global config

question tool, permission prompts

Claude Code

Notification + Stop hooks in ~/.claude/settings.json

permission_prompt, idle_prompt, agent_needs_input, elicitation_dialog, task completion

Kimi Code

[[hooks]] block in ~/.kimi-code/config.toml

PermissionRequest, Stop, task.completed

Copilot CLI

hooks file in ~/.copilot/hooks/nockit.json

permission_prompt, agent_idle, elicitation_dialog, completions

OpenClaw

best-effort hook in ~/.openclaw/hooks/

stop / reset (no documented idle event)

Antigravity

MCP server in ~/.gemini/config/mcp_config.json

MCP tool + rules only (no public hooks API)

Install a single client explicitly: npx -y nockit-mcp setup --client claude --client kimi

All hooks are fire-and-forget (they never block or slow the agent), rate-limited to one push per 60s per client, and idempotent — re-running setup never duplicates hooks.

📣 Delivery channels

Every notification fans out to all configured channels. nockit setup asks about each optional channel after the ntfy topic — paste a webhook URL (or a bot token + chat id) and you're done. All channels are optional; ntfy always works.

Channel

What you need

Where to get it

ntfy.sh

a topic (auto-generated)

https://ntfy.sh

Discord

a webhook URL

create one in your server: Settings → Integrations → Webhooks — official docs: https://discord.com/developers/docs/resources/webhook

Slack

an incoming webhook URL

https://api.slack.com/messaging/webhooks

Telegram

bot token + chat id

create a bot with @BotFather for the token — https://core.telegram.org/bots — then message your bot and read the chat id from https://api.telegram.org/bot<TOKEN>/getUpdates (send API: https://core.telegram.org/bots/api#sendmessage)

Discord / Slack webhooks are simple HTTP forwarding: nockit just POSTs the message to your webhook URL. The URL itself is a secret — it lives in ~/.config/nockit/config.json (and the DISCORD_WEBHOOK / SLACK_WEBHOOK env vars), so keep that file private.

You can also configure channels without the interactive setup by setting the env vars below, or by editing ~/.config/nockit/config.json directly (discordWebhook, slackWebhook, telegramBotToken, telegramChatId).


⚙️ Configuration

nockit-mcp can be customized using environment variables passed during execution or configured in your MCP host client:

Environment Variable

Type

Default

Description

NOCKIT_LOG_LEVEL

string

info

Log verbosity (debug, info, warn, error)

NOCKIT_PORT

number

3000

Port used when running in HTTP/SSE transport mode

NOCKIT_HOST

string

localhost

Host interface binding for HTTP mode

NTFY_TOPIC

string

nockit_default_alerts

ntfy.sh topic to publish to

DISCORD_WEBHOOK

string

Discord webhook URL to forward notifications to

SLACK_WEBHOOK

string

Slack incoming webhook URL to forward to

TELEGRAM_BOT_TOKEN

string

Telegram bot token (with TELEGRAM_CHAT_ID)

TELEGRAM_CHAT_ID

string

Telegram chat id the bot sends messages to


Available Tools & Capabilities

List the primary tools or capabilities exposed by your MCP server here.

  • ping: Health check tool to verify server readiness and latency.

  • get_status: Returns current operational metrics and system status.


Testing & Verification

Run the built-in test suite:

npm test

To test the MCP protocol connection locally using the official MCP Inspector:

npx @modelcontextprotocol/inspector npx nockit-mcp

License

Distributed under the MIT License. See LICENSE for more information.

Install Server
A
license - permissive license
A
quality
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A MCP server for Windows/Linux that provides 90+ tools enabling AI assistants to systematically manage local systems, including system probing, command execution, file editing, network diagnostics, and more.
    12
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    A lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.
    5,309
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    An MCP server that gives your AI assistant full awareness of your local dev environment — running processes, Docker containers, git state, open ports, log files, and more.
    137
    1
    MIT

View all related MCP servers

Related MCP Connectors

  • Personal assistant MCP server with search, execute, packages, jobs, secrets, and integrations.

  • A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…

  • MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeCrack-01/NockIt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server