FolioSpace Library

MCP

Install the local MCP bridge for agents.

FolioSpace MCP runs on the machine where your AI Agent is running. It connects to the FolioSpace Library service on your NAS through a secure Bearer Token.

MCP does not need to be deployed on the same device as FolioSpace Library. It handles control and lookup for directories, works, games, scans, status, and play records. Media files are still accessed through authenticated URLs returned by the server, so real NAS paths are not exposed to clients.

Install

curl -fsSL https://foliospace.app/install-mcp.sh | sh

This installs foliospace-mcp to ~/.local/bin/foliospace-mcp from the 0.993 release files published under /releases.

Client configuration

{
  "mcpServers": {
    "foliospace-library": {
      "command": "/Users/you/.local/bin/foliospace-mcp",
      "env": {
        "FOLIOSPACE_BASE_URL": "http://your-nas-ip:8080",
        "FOLIOSPACE_API_TOKEN": "your-access-key"
      }
    }
  }
}

What MCP is for

Use MCP for lookup, diagnostics, manifests, preferences, private state, progress, scan jobs, scan settings, and error summaries. MCP does not transfer large files. Comic pages, EPUB resources, PDF content, ROM files, video streams, HLS playlists, and thumbnails are still read through URLs returned by the HTTP Client API.

Because the MCP server talks to your own FolioSpace Library instance, it needs FOLIOSPACE_BASE_URL and, when auth is enabled, FOLIOSPACE_API_TOKEN.

Common tools

Dynamic game-platform discovery

MCP 0.993 adds foliospace.get_game_platform_catalog. It returns every platform recognized by the connected FolioSpace server, including stable IDs, display titles, aliases, indexed counts, and availability. Agents should use it when generating platform menus or answering which systems the server supports.

foliospace.list_game_platforms remains the inventory-only facets tool for platforms currently represented by visible game records.

Resources