Server data from the Official MCP Registry
Give AI agents secure access to ZERNO project briefs, tasks, and context over remote MCP.
Give AI agents secure access to ZERNO project briefs, tasks, and context over remote MCP.
Remote endpoints: streamable-http: https://zerno.one/mcp
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"one-zerno-zerno-lite": {
"url": "https://zerno.one/mcp"
}
}
}From the project's GitHub README.
Official metadata for the ZERNO Lite Model Context Protocol (MCP) server.
ZERNO Lite is a remote MCP server that connects AI agents to ZERNO project context — project briefs, task and agent context, and structured intake workflows — over a secure, OAuth-authorized endpoint. It's built for coding agents, product agents, and automation workflows that need to understand a project before acting, without unrestricted backend access.
This repository is the public "front door" for the hosted server: metadata,
server.json, and the tool catalog for MCP directories. It does not contain the backend source — the server runs as a hosted service at the endpoint below.
https://zerno.one/mcp
| Transport | Streamable HTTP (JSON-RPC 2.0 over POST) |
| Auth | OAuth 2.1 with PKCE (S256); bearer tokens; per-project authorization |
| Registration | Dynamic Client Registration (RFC 7591) — no static API key |
| Capabilities | 8 tools · 0 resources · 0 prompts |
| Registry name | one.zerno/zerno-lite |
| Manifest | https://zerno.one/.well-known/mcp |
Add a remote connector named zerno with URL https://zerno.one/mcp, then complete the OAuth
consent in the browser.
zerno, URL above).codex mcp add zerno --url https://zerno.one/mcphttps://zerno.one/mcpFor user-scoped tokens, tell the agent which project with a project_slug (e.g. zerno-one).
| Tool | Does | Writes? |
|---|---|---|
zerno_get_project_brief | Project orientation: focus, next action, do-not-do, memory index | no |
zerno_get_agent_context | Compiled project memory + recent events for an agent run | no |
zerno_list_tasks | Filtered backlog listing | no |
zerno_get_task | Full detail for one task | no |
zerno_update_task | Patch task fields/status (ICE recomputed) | mutates |
zerno_submit_task_triage | Submit triage proposals (pending human approval) | creates proposals |
zerno_create_agent_intake_task | File a review task from an agent report | creates a task |
zerno_capture_session_event | Append a session summary to project memory | creates memory event |
Full machine-readable schemas: tools-list.json. No tool deletes data or calls
third-party services. tools/list is scope-filtered — a read-only token sees only the four read tools.
Every call requires OAuth; nothing is exposed unauthenticated. Bearer tokens are hashed at rest, no secrets are returned in tool output, and every call is audit-logged. Access is tied to the user's authorized ZERNO workspace/project.
Requires a ZERNO account and an authorized project. Remote/hosted only (no stdio or packaged distribution). Tools only — no MCP resources or prompts.
server.json — Official MCP Registry manifesttools-list.json — full tools/list (8 tools, exact schemas)smithery-server-card.json — static server card for SmitheryLICENSE — MITMIT — applies to this metadata repository.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.