Nekoweb MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEKOWEB_API_KEY | Yes | Your Nekoweb API key from https://nekoweb.org/api. Required for authenticated operations; without it, only public site lookups work. | |
| NEKOWEB_LOCAL_ROOT | No | A folder on your computer. When set, the upload tools can only read files inside it. When unset, any file you name can be uploaded. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for managing a static website hosted on Nekoweb (nekoweb.org). Paths are absolute from the account's file root. Each site's files are usually in a folder named after it, e.g. "/mysite.nekoweb.org/index.html"; nekoweb_list_sites shows each site's folder and nekoweb_list_folder at "/" shows the layout. Typical workflow: nekoweb_list_sites to find the folder, nekoweb_list_folder to explore, nekoweb_read_file to read, nekoweb_write_file to change text files, nekoweb_upload_file for binaries. File operations share a rate limit; check nekoweb_get_limits before bulk work.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nekoweb_get_site_infoA | Get a Nekoweb site's title, domain, views, followers, update count and creation/update dates. Without 'site', returns the site that the configured API key belongs to. With 'site', looks up any public Nekoweb site (no API key needed). Examples:
|
| nekoweb_list_sitesA | List every site on the Nekoweb account that owns the API key, with domain, title, views, followers, dates and the folder that holds each site's files. The main site is marked. Call this first to learn the folder to use in file paths, e.g. '/mysite.nekoweb.org'. Use nekoweb_get_site_info for a single site. |
| nekoweb_get_limitsA | Show the account's current API rate limits: 'general' (most file operations), 'big_uploads' (chunked uploads over 95MB) and 'zip' (zip imports). Each limit has the maximum, how many requests remain, and when the counter resets. Call this before bulk operations or after a 429 error. |
| nekoweb_list_folderA | List the files and folders inside a folder of your Nekoweb site, sorted by path. Set recursive=true to walk subfolders too (up to max_depth levels; each subfolder costs one API request against the rate limit, capped at 25 per call). Results are paginated with limit/offset. Examples:
|
| nekoweb_read_fileA | Read the raw source of a file on your Nekoweb site (SSI directives in .html files are returned as written, not rendered). Text files are returned as text, paginated by character offset. Images up to 5.0 MB are returned as images. Other binaries return only their size. Examples:
|
| nekoweb_createA | Create a new empty file or a new folder on your Nekoweb site. Fails if something already exists at that path. To create a file with content in one step, use nekoweb_write_file instead. Examples:
|
| nekoweb_write_fileA | Write text content to a file on your Nekoweb site, creating it or replacing its entire content. mode='create_or_overwrite' (default) uploads the file whether or not it exists; the parent folder must already exist (create it with nekoweb_create). mode='edit_existing' only changes a file that already exists. Always send the complete new file content; there is no partial update. For binary or local files, use nekoweb_upload_file. Examples:
|
| nekoweb_deleteA | Permanently delete a file or a folder (including everything inside it) from your Nekoweb site. This cannot be undone. Example: "Remove the old drafts folder" -> { path: "/mysite.nekoweb.org/drafts" } |
| nekoweb_moveA | Rename or move a file or folder on your Nekoweb site. Both are full paths from your file root; the destination's parent folder must exist. Examples:
|
| nekoweb_upload_fileA | Upload one or more files (any type, e.g. images, fonts, HTML) into a folder of your Nekoweb site. Existing files with the same name are overwritten. Provide files as local_paths (files on this machine) and/or as base64 'files'. Files over 95MB are sent automatically with Nekoweb's chunked big-file upload. For plain text content, nekoweb_write_file is simpler. Examples:
|
| nekoweb_import_zipA | Upload a .zip archive and extract it into a folder of your Nekoweb site, e.g. to deploy a whole site at once. Extracted files overwrite existing files with the same paths. The 'zip' rate limit is strict (often 1 import per period); check nekoweb_get_limits first when unsure. Example: "Deploy my built site" -> { zip_local_path: "C:/projects/site/dist.zip", folder: "/mysite.nekoweb.org" } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool maps to a distinct resource/action: site metadata (get_site_info, list_sites), account limits, and file operations (list_folder, read_file, create, write_file, delete, move, upload_file, import_zip). The potentially overlapping trio of create/write_file/upload_file is explicitly differentiated in the descriptions (empty file vs text content vs binaries/local files), so an agent can select correctly.
All names share the nekoweb_ prefix and snake_case, and most follow verb_noun (get_site_info, list_folder, read_file, write_file, upload_file, import_zip). A few are bare verbs (create, delete, move) that drop the noun, a minor deviation that remains readable and predictable.
Eleven tools is well within the ideal range and each one covers a distinct capability of a static-site file host. Nothing appears redundant or padded; site info, limits, and the full file lifecycle each earn their place.
The file/folder lifecycle is fully covered (create, read, write, list, move, delete, bulk upload, zip import) along with account introspection via get_limits and site listing. Minor gaps exist: no search across files, no copy operation, and no way to modify site-level settings, but agents can work around these via listing and read/write.