MCPOSprint

MCPOSprint

An MCP server that enables users to print markdown tasklists, Notion tasks with QR codes, and arbitrary images directly to ESC/POS thermal printers over USB. It includes specialized tools for task processing, automated card generation, and printer diagnostics.

Category
Visit Server

README

MCPOSprint - MCP Server for ESC/POS Printing over USB

Hi! This escalated quickly and became a whole thing. Full disclosure, AI helped me write a lot of this code, but I've tested it pretty throughly on a mac to confirm it works.

This is a uv based MCP that lets you connect an MCP client to a usb connected ESC/POS printer. It has baked in tools for printing your tasks from notion with QR codes, and a template to print out markdown tasklists, as well as a generic print image tool you can use to print arbitrary images. I've only tested it with an EPSON_TM_T20III-17, so YMMV with other ESC/POS printers.

šŸš€ Installation

MCPOSprint runs directly via uvx.

Prerequisites - Install these first

  • Python 3.10+
  • UV package manager: Install from astral.sh/uv
  • Thermal printer : ESC/POS compatible USB printer
  • Notion API Token (optional): If you want to print tasks from Notion. You can see how to generate a token in Notion's docs
  • libusb for USB printer access
    • macOS: brew install libusb
    • Ubuntu/Debian: sudo apt install libusb-1.0-0-dev

Getting Started

  1. Install UV (if not already installed):

    curl -LsSf https://astral.sh/uv/install.sh | sh
    
  2. Configure Your MCP Client with MCPOSprint (see configuration section below)

šŸŽÆ MCP Client Setup

Minimal Configuration (Recommended)

You can add this to the mcp config file of whatever client you use

For most users, just configure your Notion credentials if you want them:

{
  "mcpServers": {
    "mcposprint": {
      "command": "uvx",
      "args": ["mcposprint"],
      "env": {
        "PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin",
        "NOTION_API_KEY": "your_notion_api_key_here",
        "TASKS_DATABASE_ID": "your_database_id_here"
      }
    }
  }
}

Default settings used:

  • OUTPUT_DIR: ./images (saved relative to Claude Desktop's working directory)
  • PRINTER_NAME: EPSON_TM_T20III-17
  • CARD_WIDTH/HEIGHT: 580 pixels (optimized for 58mm thermal printers)

Full Configuration (Advanced)

If you need to override defaults:

{
  "mcpServers": {
    "mcposprint": {
      "command": "uvx", 
      "args": ["mcposprint"],
      "env": {
        "PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin",
        "OUTPUT_DIR": "./my-custom-images",
        "PRINTER_NAME": "YOUR_PRINTER_NAME",
        "CARD_WIDTH": "580",
        "CARD_HEIGHT": "580", 
        "NOTION_API_KEY": "your_notion_api_key_here",
        "TASKS_DATABASE_ID": "your_database_id_here",
        "DEBUG": "false"
      }
    }
  }
}

Configuration Notes:

  • PATH: Adjust for your system (macOS Homebrew path shown)
  • OUTPUT_DIR: Where images are saved (relative to Claude Desktop's working directory)
  • PRINTER_NAME: Use your actual thermal printer name
  • Notion credentials: Optional - only needed for Notion integration

Available Environment Variables

Variable Default Description
OUTPUT_DIR ./images Where generated card images are saved
PRINTER_NAME EPSON_TM_T20III-17 Your thermal printer name
CARD_WIDTH 580 Card width in pixels
CARD_HEIGHT 580 Card height in pixels
NOTION_API_KEY (none) Your Notion integration API key
TASKS_DATABASE_ID (none) Your Notion tasks database ID
DEBUG false Enable debug logging

Output Directory

Generated card images are saved to the OUTPUT_DIR (default: ./images) relative to Claude Desktop's working directory. The directory is created automatically if it doesn't exist.

Notion Setup

  1. Create a Notion integration at https://www.notion.so/my-integrations
  2. Copy the API key to your .env file
  3. Share your tasks database with the integration
  4. Copy the database ID to your .env file

Database should have these properties:

  • Name or Task (title)
  • Due Date (date)
  • Priority (select: High, Medium, Low)
  • Status (status: Not Started, In Progress, Done)
  • Description (rich text, optional)

Usage with MCP Clients

Once connected, you can use these tools in your MCP client:

  • Generate cards from markdown: Use process_static_cards tool
  • Fetch Notion tasks: Use process_notion_tasks tool (with progress tracking)
  • Print existing images: Use print_only tool
  • Test printer: Use test_printer_connection tool
  • Run diagnostics: Use run_diagnostics tool
  • Get printer specs: Access image://thermal-card-size resource

Markdown Format

## Morning Routine
- *Get dressed
- Brush teeth
- Make coffee
- Check calendar

## Work Tasks
- *Review emails
- Update project status
- *Prepare for 2pm meeting
- Submit timesheet
  • Use ## Title for card headers
  • Use - Task for regular tasks
  • Use - *Task for priority tasks (marked with ā˜…)

Development Installation (Optional)

Only needed for contributing or customization:

# Clone the repository  
git clone https://github.com/your-username/mcposprint.git
cd mcposprint

# Install with uv
uv sync

# Start the MCP server
uv run mcposprint

šŸ”§ MCP Tools

MCPOSprint provides 6 MCP tools for task card generation and printing:

Available Tools

  1. process_static_cards - Generate cards from markdown files

    • Parameters: file (string), no_print (boolean)
    • Returns: List of generated file paths
  2. process_notion_tasks - Fetch and process Notion tasks (with progress tracking)

    • Parameters: no_print (boolean)
    • Returns: List of generated file paths
    • Features: Real-time progress updates via Context
  3. print_only - Print existing image files from directory

    • Parameters: directory (string)
    • Returns: Success status message
  4. test_printer_connection - Test thermal printer connectivity

    • Returns: Connection status message
  5. run_diagnostics - Run comprehensive system diagnostics

    • Returns: Detailed diagnostic information
  6. create_sample_files - Generate sample markdown file for testing

    • Returns: Success status message

MCP Resources

  • image://thermal-card-size - Thermal printer card specifications
    • Width: 384 pixels (48mm at 203 DPI)
    • Height: Variable (200-400 pixels)
    • Format: PNG, monochrome

šŸ–Øļø Printer Setup

Supported Printers

AI Generated List of ESC/POS Compatible Thermal Printers

  • EPSON: TM-T20III, TM-T88V, TM-T82, TM-T70
  • Star Micronics: TSP143, TSP654, TSP100
  • Citizen: CT-S310II, CT-S4000
  • Most USB thermal printers supporting ESC/POS protocol

Printer Setup via MCP Tools

Use the MCP tools to test and configure your printer:

# Test printer connection
Use: test_printer_connection

# Run full diagnostics
Use: run_diagnostics

Architecture

The MCP server is modularized into clean components:

mcposprint/
ā”œā”€ā”€ core/
│   ā”œā”€ā”€ config.py      # Configuration management
│   └── printer.py     # Main orchestration class
ā”œā”€ā”€ parsers/
│   ā”œā”€ā”€ markdown.py    # Markdown file parser
│   └── notion.py      # Notion API integration
ā”œā”€ā”€ generators/
│   └── card.py        # PIL-based card image generation
└── printers/
    └── escpos_printer.py  # ESC/POS direct USB interface

šŸ” Troubleshooting

Common Issues

  1. Printer not found

    • Use the test_printer_connection MCP tool
    • Use the run_diagnostics MCP tool for detailed information
    • Check USB connections and printer power
  2. Notion connection fails

    • Use the run_diagnostics MCP tool to verify API configuration
    • Check that your API key is valid in .env
    • Verify database permissions in Notion
    • Ensure the database ID is correct
  3. MCP Server connection issues

    • Verify the server is running: uv run mcposprint
    • Check your MCP client configuration
    • Ensure the working directory path is correct

Real-time Progress Tracking

The process_notion_tasks tool provides real-time progress updates:

  • āœ… API Success: Found X tasks
  • Processing task 1/3: Task Name
  • āœ… Generated: ./output/file.png
  • āœ… Print Success: Task Name

This prevents client timeouts during long operations.

Development

Local Development

# Install in development mode with dev dependencies
uv sync --all-extras

# Run tests (when available)
pytest

# Format code
black mcposprint/
isort mcposprint/

# Type checking
mypy mcposprint/

Running the MCP Server

# Start the server for development
uv run mcposprint

# Test with MCP inspector (if available)
# Connect your MCP client to localhost

License

MIT License - see LICENSE file for details.

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests if applicable
  5. Submit a pull request

Changelog

v1.0.0 - MCPOSprint Initial Release

  • āœ… Full MCP server implementation with 6 tools
  • āœ… Real-time progress tracking with Context support
  • āœ… Async Notion task processing with timeout handling
  • āœ… Thermal printer card generation and printing
  • āœ… Static markdown card processing
  • āœ… Modular architecture with clean separation
  • āœ… Environment-based configuration
  • āœ… ESC/POS direct USB printing support
  • āœ… QR code generation for Notion tasks
  • āœ… Comprehensive error handling and diagnostics

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
E2B

E2B

Using MCP to run code via e2b.

Official
Featured