P

paged.net

paged.net hosts static websites and keeps each upload as a version that can be published or restored later. Site owners can create, publish, inspect, and manage their own sites through the web app, REST API, or MCP server.

2 integrations · MCP · REST

paged.net exposes two public developer integration surfaces on its own domain: a versioned owner REST API at `https://paged.net/api/v1` and an OAuth-protected remote MCP server at `https://paged.net/api/mcp` over streamable HTTP.

discovered 17d ago
MCP servers1
REST · OpenAPI1
Credentials
paged.net personal access tokenbearerGet token ↗

Sign in to PagedNet, open API tokens in the control panel, and create a personal access token. Choose sites:read for read-only access or sites:write for create/update/delete and publishing access. Copy the secret when it is shown; tokens start with pnpat_ and are shown once.

OAuth 2.0oauth2
OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.

paged.net personal access tokenbearerGet token ↗

Sign in at https://paged.net, open Tokens in the dashboard and create a token. Choose sites:read to inspect sites, or sites:write as well to create, publish and delete them. The secret starts with pnpat_ and is shown once. Personal access tokens work with the REST API only; MCP clients sign in with OAuth.

paged.net OAuthoauth2

MCP clients discover the authorization server from https://paged.net/.well-known/oauth-protected-resource, register themselves (dynamic client registration or a client ID metadata document), and send the owner through a consent screen. Scopes: sites:read, sites:write.

conventions · 4/8 published

Publish these signals → /publishing