API & MCP

Reocities can be driven programmatically as well as through the interface.

HTTP API

The API covers listing, reading and writing files in your site, so you can publish from a script or a build step instead of the file manager. Full endpoint reference lives in the API documentation.

MCP server

There is also an MCP server, which lets an AI assistant work on your site directly — reading files, making edits, checking stats — with a token you issue and can revoke. Useful if you would rather describe a change than make it yourself.

Keys and safety

Treat API tokens like passwords. Anything holding your token can rewrite your site. Issue a separate token per tool so you can revoke one without breaking the others.