Lightpaper Mcp
About
publish your essays, research papers and blogs at the speed of light
Details
- Author
- lightpaperorg
- Downloads
- 140
- Categories
- Other
Jump to
- API-first publishing with no frontend or editor
- Permanent URLs with content negotiation (HTML and JSON)
- Quality scoring (structure, substance, tone, attribution)
- Author gravity trust system with identity verification levels
- Full content export and GDPR-compliant hard delete
- Search API, sitemap.xml, JSON-LD, RSS feeds
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Lightpaper McpCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Run the FastAPI application locally via Docker Compose (docker compose up -d), create an account through the auth endpoint, verify an OTP code to obtain an API key, and then use the publish endpoint with that key. The MCP server is included in the repository under the mcp/ directory.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"lightpaper mcp": {
"lightpaper": {
"command": "lightpaper-mcp",
"env": {
"LIGHTPAPER_API_KEY": "your-api-key"
}
}
}
}
}McpServers
{
"lightpaper": {
"command": "lightpaper-mcp",
"env": {
"LIGHTPAPER_API_KEY": "your-api-key"
}
}
}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
| Document | Description |
|----------|-------------|
| API_DESIGN.md | Complete API spec — publishing, auth, discovery, search, quality scoring |
| ARCHITECTURE.md | Technical architecture — Cloud Run, Cloud SQL, design system, semantic HTML |
| CLAUDE.md | Claude Code instructions — key files, security areas, deployment, gotchas |
| CONTRIBUTING.md | Development setup and contribution guidelines |
| SECURITY.md | Vulnerability 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 (Firebase Auth), revocable keys, full content export (GET /v1/account/export → ZIP), GDPR hard-delete, and clear TOS: authors own copyright, platform has display license only.
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
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
