About Zerno Lite Mcp Server
ZERNO Lite is a hosted remote MCP server for coding agents, product agents, and automation workflows that need authorized project context. It provides scoped access to project briefs, task data, and memory, with OAuth-based authorization.
Key features
- 01Read project briefs and agent context
- 02List and retrieve tasks
- 03Update task fields and status
- 04Submit triage proposals for review
- 05Create intake tasks and memory events
- 06OAuth authorization per project
Use cases
- 01Give an agent project context before work
- 02Review and update a project backlog
- 03Submit task triage for human approval
- 04Record agent reports and session summaries
MCP support
Exposes eight tools through a hosted remote MCP endpoint, with no resources or prompts. OAuth 2.1 with PKCE and per-project authorization control access; read-only tokens see only read tools.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://zerno.one/mcpclaude mcp add --transport http zerno https://zerno.one/mcp{"mcpServers":{"zerno":{"type":"http","url":"https://zerno.one/mcp"}}}Open in Cursor{"servers":{"zerno":{"type":"http","url":"https://zerno.one/mcp"}}}Open in VS Code{"mcpServers":{"zerno":{"type":"http","url":"https://zerno.one/mcp"}}}{"mcpServers":{"zerno":{"serverUrl":"https://zerno.one/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEZERNO 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
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 |
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 manifesttools-list.json— fulltools/list(8 tools, exact schemas)smithery-server-card.json— static server card for SmitheryLICENSE— MIT
Links
- Website: https://zerno.one
- Docs: https://zerno.one/docs/mcp
License
MIT — applies to this metadata repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.