MCP.so
Sign In

Zerno Lite Mcp Server

@zernozerno

About Zerno Lite Mcp Server

Connect AI agents to your ZERNO product backlog over a secure remote MCP endpoint. Read project briefs, list and open tasks, retrieve compiled project memory, patch task status, submit triage proposals, and file agent-intake tasks. OAuth 2.1 (PKCE), per-project authorization. 8 t

Basic information

Category

Other

Transports

stdio

Publisher

zernozerno

Submitted by

zernozerno

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "zerno": {
      "url": "https://zerno.one/mcp"
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Zerno Lite Mcp Server?

Zerno Lite Mcp Server 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 is built for coding agents, product agents, and automation workflows that need to understand a project before acting, without unrestricted backend access.

How to use Zerno Lite Mcp Server?

Add a remote MCP connector pointing to https://zerno.one/mcp and complete the OAuth consent in your browser. For user-scoped tokens, specify a project_slug (e.g., zerno-one). Supported in Claude Code/Desktop, Codex CLI, and Cursor via their respective connector settings or commands.

Key features of Zerno Lite Mcp Server

  • 8 read‑only or mutation‑limited tools; no data deletion
  • OAuth 2.1 with PKCE and bearer token authentication
  • Per‑project authorization with dynamic client registration
  • Streamable HTTP transport (JSON‑RPC 2.0 over POST)
  • Audit‑logged calls; no secrets returned in tool output
  • Hosted service only; no stdio or packaged distribution

Use cases of Zerno Lite Mcp Server

  • Provide project orientation (brief, focus, next action) to a coding agent
  • Retrieve compiled project memory and recent events for an agent run
  • List and update tasks in the ZERNO backlog
  • Submit triage proposals or file review tasks from agent reports

FAQ from Zerno Lite Mcp Server

What transport and authentication does the server use?

Streamable HTTP (JSON‑RPC 2.0 over POST) with OAuth 2.1, PKCE (S256), and bearer tokens. Dynamic client registration (RFC 7591) removes the need for static API keys.

What tools are available?

Eight tools covering project brief retrieval, agent context, task listing/detail, task updates, triage proposals, agent intake tasks, and session event capture. Read‑only tokens only see the four read tools.

Can the server delete data or call third‑party services?

No tool deletes data or calls third‑party services. All mutations are limited to fields/status updates and creation of proposals or tasks.

Is the server self‑hostable?

No. Zerno Lite Mcp Server is remote/hosted only — it runs at https://zerno.one/mcp and does not support stdio or packaged distribution.

What are the prerequisites for using the server?

A ZERNO account and an authorized workspace/project are required. The server provides only tools; no MCP resources or prompts are exposed.

Comments

More Other MCP servers