Blank Files

Exposes Blank Files as MCP tools to list, filter, and fetch file entries via HTTP or stdio.

javascript

1

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "filearchitect-blankfiles-website": {
      "command": "node",
      "args": [
        "/absolute/path/to/blankfiles-website/scripts/mcp/blankfiles-mcp.mjs"
      ],
      "env": {
        "BLANKFILES_BASE_URL": "https://blankfiles.com"
      }
    }
  }
}

You can interact with the Blank Files catalog via an MCP server that exposes core file listing and lookup actions as tools. This enables automations and integrations to query available files, filter by type or category, and retrieve exact file entries through a simple, scriptable interface.

How to use

You will run the MCP server locally and connect to it with an MCP client. The server provides tools that let you list files, filter by type, and fetch detailed entries for a specific category and extension. Use each tool by name and supply optional filters as arguments. Your MCP client can then present results, drive downloads, or feed data into other automation layers.

How to install

Prerequisites you need before starting:

Node.js 18+ (for MCP runtime)
npm (included with Node.js)

Follow these steps to install and run the MCP server:

# Clone the repository containing the MCP server
git clone https://github.com/filearchitect/blankfiles-website.git
cd blankfiles-website

# Install dependencies for the MCP server
npm install

# Start the MCP server component
npm run mcp:server

Additional configuration and notes

The MCP server is exposed as a local, stdio-based service. You may run it with Node and a script path as shown in the example configuration.

Optional environment variable when starting the MCP server:

BLANKFILES_BASE_URL=https://blankfiles.com

If you provide the environment variable, the server will default to using the Blank Files public site as its base URL for catalog data and assets.

Example MCP client configuration to connect to the local stdio server is shown below. Adapt the absolute path to where you keep the MCP script in your environment.

MCP config example

{
  "mcpServers": {
    "blankfiles": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/blankfiles-website/scripts/mcp/blankfiles-mcp.mjs"],
      "env": {
        "BLANKFILES_BASE_URL": "https://blankfiles.com"
      }
    }
  },
  "envVars": [
    {
      "name": "BLANKFILES_BASE_URL",
      "description": "Base URL for catalog and assets (default: https://blankfiles.com)",
      "required": true,
      "example": "https://blankfiles.com"
    }
  ]
}

Available tools

list_blank_files

List files with optional filters such as category, type, and limit.

files_by_type

List entries filtered by the file extension/type.

file_by_category_type

Perform a deterministic lookup by category and extension, returning a single matching entry if found.