npm @nograai/mcpstdioupdated 2mo ago
The MCP server behind Nogra — brief, GO, dispatch, evidence, verify for AI-assisted work. This package is the protocol bridge: 32 public tools for briefs, dispatch transport, run events, registry and redaction, served over MCP stdio against the current workspace's local .nogra/ records.
What can you do with Nogra?
Nogra MCP
The MCP server behind Nogra — brief, GO, dispatch,
evidence, verify for AI-assisted work. This package is the protocol bridge:
32 public tools for briefs, dispatch transport, run events, registry and
redaction, served over MCP stdio against the current workspace's local
.nogra/ records.
Install
Usually nothing to install: the Nogra Claude Code plugin starts this server
automatically through its bundled launcher (npx first, uvx/pipx as
fallbacks). Standalone:
npx -y @nograai/mcp # npm path — standalone platform binaries, no Python needed
uvx nogra-mcp # PyPI path — needs uv on PATH
Run it from a workspace folder; it reads and writes that workspace's
.nogra/ records.
What it serves
Public mode only: 32 tools covering brief save/validate/promote, dispatch handoffs, transport lifecycle (dispatch, status, events, return), run records, the contract registry and text redaction. Everything stays in local markdown/JSON files the user owns — the server does zero model inference, makes no network calls of its own, and never touches credentials.
Naming
The nogra MCP server name is reserved for the public plugin path. If you
develop against a local checkout, register it under a different name (for
example nogra-dev) so the two never collide.
Install
Add Nogra to your client. Pick the one you use.
claude mcp add mcp -- npx -y @nograai/mcpcodex mcp add mcp -- npx -y @nograai/mcpamp mcp add mcp -- npx -y @nograai/mcp{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@nograai/mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@nograai/mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"mcp","command":"npx","args":["-y","@nograai/mcp"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@nograai/mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@nograai/mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@nograai/mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"mcp": {
"type": "local",
"command": "npx",
"args": [
"-y",
"@nograai/mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"@nograai/mcp"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y @nograai/mcpRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation10/25
- Maintenance16/25
- Trust6/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 57 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.0.3Latest | Jul 6, 2026 |