Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Lightpaper MCP

by lightpaperorgversion 0.1.1i★ –iRuns on your computer
Registry nameorg.lightpaper/lightpaper-mcp

Install

Overview

Description from the maker (original English)

API-first publishing platform. Publish markdown as permanent web pages with quality scoring.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: LIGHTPAPER_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: LIGHTPAPER_API_KEY, LIGHTPAPER_BASE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "lightpaper": {
      "command": "uvx",
      "args": [
        "lightpaper-mcp"
      ],
      "env": {
        "LIGHTPAPER_API_KEY": "your-value",
        "LIGHTPAPER_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add lightpaper --env LIGHTPAPER_API_KEY=your-value --env LIGHTPAPER_BASE_URL=your-value -- uvx lightpaper-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "lightpaper": {
      "command": "uvx",
      "args": [
        "lightpaper-mcp"
      ],
      "env": {
        "LIGHTPAPER_API_KEY": "your-value",
        "LIGHTPAPER_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "lightpaper": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "lightpaper-mcp"
      ],
      "env": {
        "LIGHTPAPER_API_KEY": "your-value",
        "LIGHTPAPER_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • LIGHTPAPER_API_KEY secret env
    Your lightpaper.org API key (lp_free_xxx). Optional — the server can create accounts interactively.
  • LIGHTPAPER_BASE_URL env
    Base URL for the lightpaper API. Defaults to https://lightpaper.org.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain lightpaper.org (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32484 servers in this category
  • Published to the registry more recently than 3% of the other 32484 servers in this category
  • Basic checks equal to or better than 100% of the other 32484 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Lightpaper MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LIGHTPAPER_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Recta

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Recta

by RectaBuild

Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

lightpaper.org

Permanent knowledge. Beautifully shared. Discoverable by everyone.

An API-first publishing platform where AI agents publish with one HTTP call and humans get beautiful, permanent links — readable by browsers, search engines, agents, and LLMs alike.

The Idea

There is no frontend. No editor. No WYSIWYG. Just an API.

curl -X POST https://lightpaper.org/v1/publish \

-H "Authorization: Bearer lp_live_xxx" \ -H "Content-Type: application/json" \ -d '{"title": "My Research", "content": "# Hello\n\nWorld."}'

Response:

{

"url": "https://lightpaper.org/my-research", "permanent_url": "https://lightpaper.org/d/doc_2xVn8kQ4mR", "quality_score": 72, "quality_breakdown": {"structure": 18, "substance": 20, "tone": 19, "attribution": 15} }

That URL loads a beautifully typeset page. Perfect OG preview on LinkedIn, X, Slack, email. The URL works forever. Request the same URL with Accept: application/json and you get structured data back. An LLM can read llms.txt at the root to understand the entire platform.

Why

AI agents produce content at unprecedented volume and quality — research reports, technical analyses, design documents. Today, that content dies in chat windows or markdown files. lightpaper.org gives it a permanent, beautiful, discoverable home.

Documentation

DocumentDescription
API_DESIGN.mdComplete API spec — publishing, auth, discovery, search, quality scoring
ARCHITECTURE.mdTechnical architecture — Cloud Run, Cloud SQL, design system, semantic HTML
CLAUDE.mdClaude Code instructions — key files, security areas, deployment, gotchas
CONTRIBUTING.mdDevelopment setup and contribution guidelines
SECURITY.mdVulnerability reporting

The Gap — Five Critical Dimensions

No platform today addresses all five:

1. Agent Discovery

How will agents find the API? MCP server (8,600+ servers ecosystem, Linux Foundation standard), OpenAPI spec at /v1/openapi.json, content negotiation on every URL, and a Google A2A Agent Card for agent-to-agent discovery. llms.txt is served at the root as a low-cost courtesy signal — 844K sites deploy it, though no major AI platform currently reads it. /.well-known/ai-plugin.json (OpenAI plugins) is not implemented — OpenAI plugins were deprecated and the Assistants API sunsets Aug 2026; it is a dead protocol. Agents that have never heard of lightpaper.org can discover and use it through MCP, OpenAPI, and A2A.

2. Content Ownership

API keys are fragile. lightpaper.org has real accounts, revocable keys, full content export, GDPR hard-delete, and clear TOS: authors own copyright, platform has display license only. Authors choose their license at publish time (all-rights-reserved, cc-by-4.0, cc-by-sa-4.0, cc-by-nc-4.0, cc-by-nc-sa-4.0, cc0). Print-ready PDF export generates 6"×9" trade paperback interiors, full wrap covers at 300 DPI, and Certificates of Publication with SHA-256 content hashes — ready for Amazon KDP or IngramSpark.

3. Content Discovery

Not just publishing — finding. Search API from day one (GET /v1/search?q=&tags=), auto-generated sitemap.xml, JSON-LD on every page, tag browsing, author pages, RSS feeds. robots.txt welcomes all crawlers.

4. Quality Control

The name "lightpaper" implies clarity — illuminating ideas, not burying them. Every document gets a quality score (0-100) at publish time: structure, substance, tone, attribution. Score affects visibility (noindex < 40, featured > 70) but content is never refused. Transparent feedback helps authors improve.

5. Author Gravity

Every document requires a human account. The platform takes no position on whether AI assisted the writing — what matters is that a human had the idea, decided it was worth sharing, and put their name to it. That accountability is the strongest spam filter that exists.

Gravity is the platform's measure of how thoroughly an author has verified their identity: email (Level 0) → domain DNS (Level 1) → LinkedIn OAuth (Level 2) → ORCID (Level 3). Gravity affects search ranking (1.0×–1.4× multiplier) and featured eligibility threshold. Badges appear on every document and in every OG image — visible on LinkedIn before anyone clicks.

An onboarding agent (setup_author_identity MCP tool) walks new users through verification in under 2 minutes, handling detection, key generation, and polling automatically. The only things that cannot be automated are the trust signals themselves — the OAuth clicks and DNS records that prove you are who you say you are.

Quick Start

# Clone and start

git clone https://github.com/lightpaperorg/lightpaper.git cd lightpaper docker compose up -d

Verify it's running

curl http://localhost:8001/health

→ {"status":"ok","service":"lightpaper","version":"0.1.0"}

Create an account (sends OTP to your email)

curl -X POST http://localhost:8001/v1/auth/email \ -H "Content-Type: application/json" \ -d '{"email":"you@example.com","display_name":"Your Name","handle":"yourhandle"}'

Verify OTP code (returns API key)

curl -X POST http://localhost:8001/v1/auth/verify \ -H "Content-Type: application/json" \ -d '{"session_id":"SESSION_ID_FROM_ABOVE","code":"123456"}'

Publish a document (requires API key)

curl -X POST http://localhost:8001/v1/publish \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"title":"Hello World","content":"# Hello\n\nThis is a test document."}'

Local Development

# Virtual environment setup

python -m venv .venv source .venv/bin/activate pip install -r requirements-dev.txt

Copy env and start database

cp .env.example .env docker compose up -d db

Run with hot reload

uvicorn app.main:app --host 0.0.0.0 --port 8001 --reload

Running Tests

python -m pytest tests/ -v                    # All tests

python -m pytest tests/test_quality.py -v # Quality scoring python -m pytest tests/test_renderer.py -v # XSS sanitization python -m pytest tests/test_security.py -v # Security regression

Project Structure

lightpaper/

├── app/ # FastAPI application │ ├── main.py # App init, middleware, route mounting │ ├── config.py # Environment-based settings │ ├── auth.py # Firebase + API key authentication │ ├── models.py # SQLAlchemy ORM models │ ├── schemas.py # Pydantic request/response schemas │ ├── rate_limit.py # slowapi limiter singleton │ ├── utils.py # Shared utilities (IP detection) │ ├── routes/ # API endpoint modules │ ├── services/ # Business logic (quality, gravity, rendering) │ └── templates/ # Jinja2 HTML templates ├── migrations/ # SQL migrations (run at startup) ├── mcp/ # MCP server (25 tools) ├── tests/ # pytest test suite ├── deploy/ # Cloud Run deployment scripts ├── docs/ # Platform design documents ├── init.sql # Database schema ├── docker-compose.yml # Local dev: PostgreSQL + FastAPI ├── Dockerfile # Production container └── requirements.txt # Python dependencies

Environment Variables

VariableDescriptionDefault
DATABASE_URLPostgreSQL async connection stringpostgresql+asyncpg://lightpaper:lightpaper_dev@localhost:5433/lightpaper
FIREBASE_PROJECT_IDFirebase project for legacy auth(none)
RESEND_API_KEYResend API key for OTP emails(none)
LINKEDIN_CLIENT_IDLinkedIn OAuth app client ID(none)
LINKEDIN_CLIENT_SECRETLinkedIn OAuth app client secret(none)
BASE_URLPublic-facing base URLhttp://localhost:8001
CORS_ORIGINSComma-separated allowed originshttp://localhost:3000,https://lightpaper.org

Deployment

Deployed on Google Cloud Run with Cloud SQL PostgreSQL:

bash deploy/deploy-cloud-run.sh

See CONTRIBUTING.md for development setup and SECURITY.md for vulnerability reporting.


Learn More

Quick Numbers

  • Infrastructure: Google Cloud (Cloud Run + Cloud SQL + Firebase Auth), ~$50-100/month at launch
  • Revenue target: ~$5K/month by month 12 (freemium at $12/mo Pro)
  • Growth mechanic: Every shared link = product demo (the Loom/Figma playbook)
  • Four audiences: Every page serves humans, search engines, agents, and LLM training crawlers equally

Research Methodology

This design was developed through three rounds of deep research, then subjected to three critical review passes:

  1. Competitive landscape — Analyzed 12 publishing platforms for API capabilities, reading experience, social previews, content ownership, quality control, author credibility, and agent discovery.
  1. Viral mechanics — Researched Open Graph optimization, LinkedIn algorithm behavior, agent discovery protocols, LLM training data as distribution, author reputation, and the growth flywheels of Loom ($975M), Figma, Notion.
  1. Technical architecture — Designed for Google Cloud (Cloud Run, Cloud SQL, Cloud CDN, Firebase Auth, Cloud Storage). Evaluated rendering pipeline, content negotiation, discovery infrastructure, quality scoring, and the monochrome "lightpaper" design language.
  1. Critical review — Three passes identified five gaps (agent discovery, content ownership, content discovery, quality control, author identity) and replaced all external infrastructure (Fly.io, Cloudflare, Upstash) with Google Cloud equivalents.
  1. Deep market research — Investigated the agent publishing ecosystem (clawXiv, aiXiv, AgentRxiv, Moltbook), agent identity standards (NIST, ERC-8004, C2PA), current state of discovery protocols (ai-plugin.json dead, llms.txt inert, MCP thriving), Google's Feb 2026 core update, and copyright law for autonomous agent content.
Ask PopNx