
Blank Files MCP
io.github.filearchitectPublished by GitHub account filearchitectv1.0.1Updated Nov 10, 2026
MCP server for listing and retrieving minimal valid blank files from blankfiles.com.
Overview
Lists and looks up minimal valid blank files from blankfiles.com by category and file type, so an assistant can find a downloadable blank file.
- What you can do
- List blank files with optional category, type and limit filters
- List catalog entries by file extension
- Look up a single file deterministically by category plus extension
- When to use it
- Useful when you need a minimal, valid blank file of a given format (for example a spreadsheet or document) to test uploads, validate file handling, or seed a workflow, and want the assistant to find the right download entry.
- Requirements
- Runs as a local Node.js process (npm package @filearchitect/blankfiles-mcp, stdio). Network access to blankfiles.com is needed; the optional BLANKFILES_BASE_URL environment variable overrides the base URL. No authentication is declared.
Installation
In SourceWeft
- Open Blank Files MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Blank Files Website
Laravel application that powers blankfiles.com. Browse and download minimal valid blank files by type and category. File data and assets are served from the filearchitect/blank-files repository via a configurable CDN.
Requirements
- PHP 8.2+
- Composer
- Node.js 18+ (for Vite frontend build)
Installation
Set CDN_URL in .env (see Configuration). Then build the frontend and run the app:
Or use Laravel Herd with a .test domain.
Configuration
Project structure
Deployment
On push to main, GitHub Actions:
- Builds the frontend (Vite) with
npm ciandnpm run build. - SCPs
public/build/to the Forge server. - Triggers a Laravel Forge deployment.
- Runs
php artisan optimize:clearon the server.
Required repository secrets:
FORGE_SSH_HOST— SSH host for the server.FORGE_SSH_USER— SSH user (e.g.forge).SSH_PRIVATE_KEY— Private key for SCP/SSH.FORGE_SERVER_ID— Forge server ID.FORGE_SITE_ID— Forge site ID.FORGE_API_KEY— Forge deploy token.
See .github/workflows/deploy.yml.
For developers and bots
Base URL
Production: https://blankfiles.com. HTML and JSON are available; use Accept: application/json where applicable.
Web routes
API routes (prefix api/v1)
Machine-friendly notes
- The canonical file catalog schema is defined in the blank-files repo:
files/files.json(keyfiles, array of{ type, url, category, package? }). - Download URLs: use the API
urlfield for direct CDN access, orGET /files/download/{category}/{type}for a same-origin download with a predictable filename. - Conditional requests are supported on API responses and sitemap (
ETag,Last-Modified). - Rate limits: public IP-based limits and optional API-key limits (
X-API-Key). - API usage analytics are logged to
storage/logs/api-usage-*.log(configurable channel). - Compatibility policy: API policy.
- Web landing analytics for growth pages are logged to
storage/logs/web-traffic-*.log.
Client snippets
Compatibility policy
- URL versioning is stable under
/api/v1/*. - Breaking changes require a new major API path version.
- Deprecated endpoints are kept for at least 90 days before removal.
- New fields may be added; clients should ignore unknown fields.
Related
- filearchitect/blank-files — Source of truth for the file list and blank file assets.
MCP server (for agent marketplaces/registries)
This repository now includes a minimal MCP server that exposes Blank Files as tool calls.
- Script:
scripts/mcp/blankfiles-mcp.mjs - Run:
npm run mcp:server - Optional env:
BLANKFILES_BASE_URL(default:https://blankfiles.com)
Available MCP tools:
list_blank_files— list files, optional filters (category,type,limit)files_by_type— list entries by extensionfile_by_category_type— deterministic single lookup by category + extension
Example local MCP client config entry:
Registry submission helpers:
- Template metadata:
scripts/mcp/registry/server.json.template - Publish checklist:
scripts/mcp/registry/PUBLISHING.md
Published package workspace:
packages/blankfiles-mcp(publish as@filearchitect/blankfiles-mcp)
OpenClaw skill (ClawHub discoverability)
This repository includes an OpenClaw-ready skill bundle:
- Skill path:
skills/blankfiles - Skill entry:
skills/blankfiles/SKILL.md - Publish guide:
skills/blankfiles/references/publish.md
Typical publish flow:
License
This project is licensed under the MIT License.
Source: README.md at commit 00d8852
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.