Quire MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Quire MCP Create a new Quire project called my-catalogue in my Documents folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Quire MCP
About Quire
Quire is an open source digital publishing tool developed by Getty for creating beautiful, scholarly publications in multiple formats such as web, print and e-book. Optimized for visual imagery and designed to be widely accessible.
Related MCP server: any-cli-mcp-server
About Quire MCP
Quire MCP leverages the Model Context Protocol (MCP) to let you interact with Quire through natural language conversation, without needing to use the terminal directly. For example, you can prompt claude to:
"Create a new Quire project called my-catalogue in my Documents folder"
and Claude Desktop will handle the rest.
Note: Quire MCP is currently a work in progress. Phase 1 focuses on core CLI tooling. Contributions and feedback are welcome.
Requirements
Node.js 18+
npm
quire CLI installed
Claude Desktop
Quire CLI
Visit the official Quire repository and follow the instructions for your operating system: πlink.
Confirm Quire CLI is accessible:
quire --version
Claude Desktop
Download the latest release from Claude: πlink
Starting the MCP Server
Through your terminal or IDE of choice, navigate to path where this repo is cloned and run the following commands:
Build: npm run build
Run the server: npm run
Configuring your local mcp server with Claude Desktop
You need to register the MCP server with Claude Desktop by editing its config file.
For MacOS/Linux
~/Library/Application Support/Claude/claude_desktop_config.json
For Windows
C:\\Users\\YOUR_USERNAME\\AppData\\Roaming\\Claude\\claude_desktop_config.json
Note: If the file does not exist, create it with the filename: claude_desktop_config.json
Add the following to the config file:
{
...
"mcpServers": {
"quire": {
"command": "node",
"args": ["/absolute/path/to/qr-mcp-server/build/index.js"],
"env": {
"PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin"
}
}
}
...
}Finding your PATH value
The PATH value tells Claude Desktop where to find npm and npx. It varies depending on how Node was installed on your system.
Run the following in your terminal to find the correct value:
MacOS/Linux
echo $PATHWindows
echo %PATH%Copy the output and replace the PATH value in the config above with your own.
Common PATH values by setup
Setup | PATH to add |
Homebrew (macOS) | /opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin |
nvm | ~/.nvm/versions/node/v20.x.x/bin:/usr/bin:/bin |
Windows | C:\Program Files\nodejs |
Note: If you're unsure which applies to you, run which npx (macOS/Linux) or where npx (Windows) in your terminal.
This returns the full path to the binary:
e.g. /opt/homebrew/bin/npx
Remove the /npx from the filename and insert the remaining path to your PATH config.
e.g. /opt/homebrew/bin
Replace /absolute/path/to/quire-mcp/index.js with the actual path on your machine. After saving and restarting Claude Desktop, you should see the π¨ Icon in the chat interface including the Quire tools which are available.
Available Tools
4 toolsbuild_quire_projectB
Runs the Build command to generate html site files
Inputs: projectName, projectPath.
create_new_quire_projectB
Create a new Quire project in the current directory or specified folder
Inputs: projectName (required), folder, starterTemplate.
preview_quire_projectA
Runs the Preview command to generate the html site files and start a local server. Typically port 8080.
Inputs: projectName, projectPath.
stop_quire_previewA
Stops the currently running quire preview process, if any.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 4 tools
Each tool targets a distinct lifecycle step: create project, stop preview, build site, and preview site. Build and preview both generate HTML, so they could be confused, but preview's server behavior and description clarify the distinction.
Most tools follow a clear verb_quire_target pattern, such as stop_quire_preview, build_quire_project, and preview_quire_project. create_new_quire_project breaks the pattern slightly with an extra 'new', but the intent is still clear.
With only four tools, the set is compact and well-scoped to the main Quire operations. Each tool serves a necessary purpose without redundancy.
The core Quire workflow is covered: create a project, preview it, build the site, and stop the preview server. There is no status, clean, or listing command, but those are not essential for a minimal local-site-generation MCP server.
Maintenance
Related MCP Connectors
Manage projects, tasks, time tracking, and team collaboration through natural language.
Query, explore, and manage your databases through natural conversation.
Interact with the Stitch API using natural language commands.
Deploy, monitor, and manage your OpenClaw AI assistants via natural language.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables natural language interaction with the QIT CLI for testing WordPress/WooCommerce plugins. Supports running security, e2e, and activation tests, managing test environments, and accessing test results through conversational commands.221MIT
- AlicenseNot gradedqualityDmaintenanceTurn any CLI tool into an MCP server by leveraging its --help output, enabling natural language interaction with tools like gh, az, git, etc.25MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language interaction with any Python CLI application (Click, Typer, Argparse) through the Model Context Protocol.22MIT
- FlicenseCqualityDmaintenanceEnables adding and running arbitrary CLI commands through natural language, with recursive help parsing.38-