Nekoweb

Nekoweb MCP Server

Installation

%22%2C%22password%22%3Atrue%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22nekoweb_session_token%22%2C%22description%22%3A%22Optional%3A%20Nekoweb%20session%20token%20(the%20token%20cookie%20from%20nekoweb.org).%20Leave%20empty%20to%20skip%22%2C%22password%22%3Atrue%7D%5D&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22nekoweb-mcp-server%22%5D%2C%22env%22%3A%7B%22NEKOWEB_API_KEY%22%3A%22%24%7Binput%3Anekoweb_api_key%7D%22%2C%22NEKOWEB_SESSION_TOKEN%22%3A%22%24%7Binput%3Anekoweb_session_token%7D%22%7D%7D](https://insiders.vscode.dev/redirect/mcp/install?name=nekoweb&inputs=%5B%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22nekoweb_api_key%22%2C%22description%22%3A%22Nekoweb%20API%20key%20(from%20https%3A%2F%2Fnekoweb.org%2Fapi)%22%2C%22password%22%3Atrue%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22nekoweb_session_token%22%2C%22description%22%3A%22Optional%3A%20Nekoweb%20session%20token%20(the%20token%20cookie%20from%20nekoweb.org).%20Leave%20empty%20to%20skip%22%2C%22password%22%3Atrue%7D%5D&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22nekoweb-mcp-server%22%5D%2C%22env%22%3A%7B%22NEKOWEB_API_KEY%22%3A%22%24%7Binput%3Anekoweb_api_key%7D%22%2C%22NEKOWEB_SESSION_TOKEN%22%3A%22%24%7Binput%3Anekoweb_session_token%7D%22%7D%7D)) %22%2C%22password%22%3Atrue%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22nekoweb_session_token%22%2C%22description%22%3A%22Optional%3A%20Nekoweb%20session%20token%20(the%20token%20cookie%20from%20nekoweb.org).%20Leave%20empty%20to%20skip%22%2C%22password%22%3Atrue%7D%5D&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22nekoweb-mcp-server%22%5D%2C%22env%22%3A%7B%22NEKOWEB_API_KEY%22%3A%22%24%7Binput%3Anekoweb_api_key%7D%22%2C%22NEKOWEB_SESSION_TOKEN%22%3A%22%24%7Binput%3Anekoweb_session_token%7D%22%7D%7D&quality=insiders](https://insiders.vscode.dev/redirect/mcp/install?name=nekoweb&inputs=%5B%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22nekoweb_api_key%22%2C%22description%22%3A%22Nekoweb%20API%20key%20(from%20https%3A%2F%2Fnekoweb.org%2Fapi)%22%2C%22password%22%3Atrue%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22nekoweb_session_token%22%2C%22description%22%3A%22Optional%3A%20Nekoweb%20session%20token%20(the%20token%20cookie%20from%20nekoweb.org).%20Leave%20empty%20to%20skip%22%2C%22password%22%3Atrue%7D%5D&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22nekoweb-mcp-server%22%5D%2C%22env%22%3A%7B%22NEKOWEB_API_KEY%22%3A%22%24%7Binput%3Anekoweb_api_key%7D%22%2C%22NEKOWEB_SESSION_TOKEN%22%3A%22%24%7Binput%3Anekoweb_session_token%7D%22%7D%7D&quality=insiders))

Prerequisites

1. Node.js 20.3 or newer. The Claude Desktop extension doesn't need it, because Claude Desktop includes its own.
2. A Nekoweb API key (required). Log in to Nekoweb, open https://nekoweb.org/api and generate a key. The key gives full access to your site's files, so keep it private.
3. A Nekoweb session token (optional). Without it, everything in Nekoweb's official API works: your files, uploads, site info and limits. With it, you also get site settings, tags, stats history, followers, your feed, following sites and search results that show who you follow. See Getting your session token.

Getting your session token

The session token is the login cookie your browser uses on nekoweb.org. The server uses it to read and change things that aren't in the official API.

1. Log in at https://nekoweb.org in your browser.
2. Open the developer tools (F12) and go to Application → Cookies (Chrome, Edge) or Storage → Cookies (Firefox), then pick https://nekoweb.org.
3. Copy the value of the cookie named token.
4. Put it in your MCP config as NEKOWEB_SESSION_TOKEN, as in the examples below, and restart your client.

[!WARNING]

The session token is more powerful than the API key: it can do anything you can do while logged in, including changing your account settings. Keep it private, and never paste it into a chat with your assistant. It stops working when the session ends, for example when you log out, and then you need to copy a new one.

Keeping your API key and session token safe

• Don't commit them. If your MCP config lives in a project (e.g. .vscode/mcp.json), use your client's secret prompt, like the VS Code button above does, instead of pasting them into the file.
• Regenerate the key if it leaks. Generating a new key at https://nekoweb.org/api makes the old one stop working. For a leaked session token, log out of nekoweb.org to end that session.
• Limit local uploads. Set NEKOWEB_LOCAL_ROOT to your site project's folder so the assistant can only upload files from there. See Configuration.

The examples below include both the API key and the session token. If you don't want the session token, leave it out: each client has an API key only version.

Claude Code

claude mcp add nekoweb -e NEKOWEB_API_KEY=your-api-key -e NEKOWEB_SESSION_TOKEN=your-session-token -- npx -y nekoweb-mcp-server

API key only

claude mcp add nekoweb -e NEKOWEB_API_KEY=your-api-key -- npx -y nekoweb-mcp-server

Claude Desktop

Download nekoweb-mcp-server.mcpb and open it. Claude Desktop shows an install screen that asks for your API key and, optionally, your session token. Leave the session token empty to skip it.

Or add it to the config file

Open Settings → Developer → Edit Config, add the server to claude_desktop_config.json, then restart Claude Desktop:

{

"mcpServers": { "nekoweb": { "command": "npx", "args": ["-y", "nekoweb-mcp-server"], "env": { "NEKOWEB_API_KEY": "your-api-key", "NEKOWEB_SESSION_TOKEN": "your-session-token" } } } }

For the API key only, remove the NEKOWEB_SESSION_TOKEN line (and the comma before it).

VS Code

Use the install button above. VS Code asks for your API key and session token when the server first starts; leave the session token empty to skip it. Or add this to .vscode/mcp.json or your user MCP configuration:

{

"inputs": [ { "type": "promptString", "id": "nekoweb_api_key", "description": "Nekoweb API key", "password": true }, { "type": "promptString", "id": "nekoweb_session_token", "description": "Optional: Nekoweb session token. Leave empty to skip", "password": true } ], "servers": { "nekoweb": { "command": "npx", "args": ["-y", "nekoweb-mcp-server"], "env": { "NEKOWEB_API_KEY": "${input:nekoweb_api_key}", "NEKOWEB_SESSION_TOKEN": "${input:nekoweb_session_token}" } } } }

For the API key only, remove the nekoweb_session_token input and the NEKOWEB_SESSION_TOKEN line.

Cursor

Use the install button above, then replace your-api-key and your-session-token with yours, or delete the NEKOWEB_SESSION_TOKEN line to use the API key only. Or add this to ~/.cursor/mcp.json:

{

"mcpServers": { "nekoweb": { "command": "npx", "args": ["-y", "nekoweb-mcp-server"], "env": { "NEKOWEB_API_KEY": "your-api-key", "NEKOWEB_SESSION_TOKEN": "your-session-token" } } } }

For the API key only, remove the NEKOWEB_SESSION_TOKEN line (and the comma before it).

Other MCP hosts

Any host that supports local (stdio) MCP servers works. Configure it to run npx -y nekoweb-mcp-server with the NEKOWEB_API_KEY environment variable set, and optionally NEKOWEB_SESSION_TOKEN. Most hosts use the same JSON format as the Claude Desktop and Cursor examples above.

Build from source

Clone this repository and run npm install and npm run build. Then use node /path/to/nekoweb-mcp-server/build/index.js as the command in your host's config instead of npx -y nekoweb-mcp-server.

Check that it works

Ask your assistant: _"What's on my Nekoweb site?"_ It should list your site's files.

Configuration

See Getting your session token for how to get the session token.

Tools

Tools marked read-only never change your site. The others change files, so most clients ask for your approval before running them.

Site

• nekoweb_get_site_info - Get a site's title, domain, views, followers, update count and dates (read-only)
• site: Domain of another public site, e.g. yoursite.nekoweb.org. Omit for your own site (string, optional)
• response_format: markdown (default) or json (string, optional)

• nekoweb_list_sites - List every site on your account, with its stats and the folder that holds its files (read-only)
• response_format: markdown (default) or json (string, optional)

• nekoweb_get_limits - Show how many API requests you have left and when each limit resets (read-only)
• response_format: markdown (default) or json (string, optional)

Files

• nekoweb_list_folder - List the files and folders in a folder (read-only)
• path: Folder to list, e.g. /mysite.nekoweb.org/blog. Defaults to / (string, optional)
• recursive: Also list subfolders. Each subfolder uses one API request, up to 25 per call (boolean, optional)
• max_depth: How many levels of subfolders to list, 1–10, default 3 (number, optional)
• limit: Maximum entries to return, 1–500, default 100 (number, optional)
• offset: Entries to skip, for paging through large folders (number, optional)
• response_format: markdown (default) or json (string, optional)

• nekoweb_read_file - Read a file's source exactly as stored, SSI directives included. Images up to 5 MB are shown as images (read-only)
• path: File to read, e.g. /mysite.nekoweb.org/index.html (string, required)
• offset: Character to start reading from, for long files (number, optional)
• max_chars: Maximum characters to return, default 20,000 (number, optional)

• nekoweb_write_file - Create a text file or replace its whole content
• path: File to write, e.g. /mysite.nekoweb.org/index.html (string, required)
• content: The complete new content of the file (string, required)
• mode: create_or_overwrite (default) writes the file whether or not it exists; edit_existing fails if it doesn't (string, optional)

• nekoweb_create - Create an empty file or a new folder
• path: Path to create, e.g.