Zerno Lite

one.zernoPublished by zerno.oneOfficial publisherv1.0.0Updated Oct 25, 2026

Give AI agents secure access to ZERNO project briefs, tasks, and context over remote MCP.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Knowledge & Memory

Server details

Identifier: one.zerno/zerno-lite
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to zerno.one, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/one.zerno%2Fzerno-lite.svg)](https://sourceweft.com/mcp/one.zerno%2Fzerno-lite?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP server that gives AI agents OAuth-authorized access to ZERNO project briefs, tasks, agent context and intake workflows.

What you can do: Read project orientation: brief with focus, next action, do-not-do and memory index, plus compiled agent context and recent events for a run. Browse the task backlog with filtered listings and full detail for a single task. Update task fields and status, with ICE scores recomputed. Submit triage proposals that await human approval, file a review task from an agent report, and append a session summary to project memory.
When to use it: Useful for coding, product or automation agents that need to understand a ZERNO project before acting, and for keeping task status and project memory current from within an agent session. Requires an existing ZERNO account and an authorized project.
Requirements: A remote hosted endpoint only; no local package or stdio option. Requires a ZERNO account and an authorized workspace/project. Authentication is OAuth 2.1 with PKCE and dynamic client registration, completed through browser consent; no static API key. User-scoped tokens need a project_slug to select the project.

Before you install

Several tools write: task updates, triage proposals, intake tasks and memory events change project data, though nothing deletes data or calls third-party services. Triage proposals still need human approval. Access is tied to the authorized workspace, and calls are audit-logged; a read-only token only exposes the four read tools.

Installation

In SourceWeft

Open Zerno Lite in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/one.zerno%2Fzerno-lite/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zerno-lite": {
      "type": "http",
      "url": "https://zerno.one/mcp"
    }
  }
}

README

ZERNO Lite — MCP Server

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.

Endpoint


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

Quickstart

Add a remote connector named zerno with URL https://zerno.one/mcp, then complete the OAuth consent in the browser.

Claude Code / Claude Desktop: Settings → Connectors → add custom connector (name zerno, URL above).
Codex CLI: codex mcp add zerno --url https://zerno.one/mcp
Cursor: Settings → MCP → Add server → URL https://zerno.one/mcp

For user-scoped tokens, tell the agent which project with a project_slug (e.g. zerno-one).

Tools (8)

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.

Security & privacy

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.

Limitations

Requires a ZERNO account and an authorized project. Remote/hosted only (no stdio or packaged distribution). Tools only — no MCP resources or prompts.

Files in this repo

server.json — Official MCP Registry manifest
tools-list.json — full tools/list (8 tools, exact schemas)
smithery-server-card.json — static server card for Smithery
LICENSE — MIT

License

MIT — applies to this metadata repository.

Source: README.md at commit 18b1db8

Tools

SourceWeft has not read this server's tools yet.

Version history

v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts