FolioSpace Library

MCP

Install the local MCP bridge for agents.

MCP is not a cloud service. Deploy FolioSpace Library first, then install foliospace-mcp on the machine where Codex, Claude Desktop, or another MCP client runs.

FolioSpace MCP supports both standard MCP stdio Content-Length framing and newline-delimited JSON-RPC. Normal users should configure it through an MCP client such as Codex, Claude Desktop, or Hermes.

Install

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

This installs foliospace-mcp to ~/.local/bin/foliospace-mcp after the matching 0.88 MCP release files have been 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

Resources