Nogra
Verify-before-done trust layer for AI-assisted work. 32 tools, local-first, no credentials.
Open source Open in the app JSON README (API)
About
Verify-before-done trust layer for AI-assisted work. 32 tools, local-first, no credentials.
Details
- Kind
- MCP servers
- Topic
- No topic detected
- Publisher
- nograai
- Origin
- official
- Category
- ferramentas
- Transport
- local
- Version
- 1.0.3
- Last push
- 2026-07-06T04:57:27Z
- Repository state
- ativo
- Language
- Python
- Added
- 2026-08-29 04:00:55
- Updated
- 2026-08-29 04:00:55
- Origin id
io.github.nograai/nogra-mcp
README
# Nogra MCP The MCP server behind [Nogra](https://nogra.ai) — 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: ```bash 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. <!-- mcp-name: io.github.nograai/nogra-mcp -->