Сервер Model Context Protocol (MCP), который обеспечивает интеграцию с API Lulu Print для услуг печати по запросу через Claude Desktop и другие клиенты MCP.
Создавайте и управляйте заданиями на печать книг и других печатных материалов
Отслеживайте статус заказа от создания до доставки
Рассчитайте стоимость перед размещением заказов
Поддержка нескольких позиций в заказе
Проверьте внутренние файлы PDF перед печатью
Проверка файлов PDF обложек с проверкой размеров
Рассчитайте необходимые размеры обложки на основе количества страниц
Получите подробный статус проверки и отчеты об ошибках
Рассчитать себестоимость продукции на основе спецификаций
Включить расчеты стоимости доставки и налогов
Поддержка различных уровней доставки (от MAIL до EXPRESS)
Получите подробную разбивку затрат
Получить доступные варианты доставки по месту назначения
Поддержка международной доставки
Различные уровни обслуживания: от стандартной почты до экспресс-доставки
Подпишитесь на обновления статуса задания на печать
Управление конечными точками веб-перехвата
Тестовая доставка вебхука
Просмотреть историю отправки вебхуков
Related MCP server: OpenPrints MCP
# Install the package globally
npm install -g @devlimelabs/lulu-print-mcp
# Start the server
lulu-print-mcp# Clone the repository
git clone https://github.com/devlimelabs/lulu-print-mcp.git
cd lulu-print-mcp
# Install dependencies
npm install
# Set up development environment
npm run setup:dev
# Start the development server
npm run dev# Build and run with Docker Compose
docker-compose up -d
# Or build and run the Docker image directly
docker build -t lulu-print-mcp .
docker run -p 3000:3000 lulu-print-mcpЗарегистрируйте учетную запись разработчика Lulu на сайте https://developers.lulu.com/
Для тестирования создайте учетную запись sandbox на сайте https://developers.sandbox.lulu.com/
Перейдите на страницу ключей API.
Скопируйте свой клиентский ключ и секретный ключ клиента
# Create a configuration file
cp .env.example .envОтредактируйте файл .env , используя ваши учетные данные API Lulu:
# Required: Your Lulu API credentials
LULU_CLIENT_KEY=your_client_key_here
LULU_CLIENT_SECRET=your_client_secret_here
# Optional: API endpoints (defaults are provided)
LULU_API_URL=https://api.lulu.com
LULU_SANDBOX_API_URL=https://api.sandbox.lulu.com
LULU_AUTH_URL=https://api.lulu.com/auth/realms/glasstree/protocol/openid-connect/token
LULU_SANDBOX_AUTH_URL=https://api.sandbox.lulu.com/auth/realms/glasstree/protocol/openid-connect/token
# Use sandbox environment for testing (default: false)
LULU_USE_SANDBOX=false
# Enable debug logging (default: false)
DEBUG=falseДобавьте этот сервер MCP в файл конфигурации Claude Desktop:
# Run the Claude Desktop setup script
npm run setup:claudeСледуйте инструкциям, чтобы обновить файл конфигурации Claude Desktop. Скрипт сгенерирует конфигурацию, похожую на:
{
"mcpServers": {
"lulu-print": {
"command": "lulu-print-mcp",
"env": {
"LULU_CLIENT_KEY": "your_client_key",
"LULU_CLIENT_SECRET": "your_client_secret"
}
}
}
}Добавьте этот MCP-сервер в файл конфигурации курсора:
Откройте настройки курсора ( Cursor → Settings или Cmd+, на Mac)
Перейдите в раздел «Функции».
Найдите настройки «Model Context Protocol»
Добавьте следующую конфигурацию:
{
"mcpServers": {
"lulu-print": {
"command": "node",
"args": ["/path/to/global/lulu-print-mcp/dist/index.js"],
"env": {
"LULU_CLIENT_KEY": "your_client_key",
"LULU_CLIENT_SECRET": "your_client_secret"
}
}
}
}Или, если установлено глобально:
{
"mcpServers": {
"lulu-print": {
"command": "lulu-print-mcp",
"env": {
"LULU_CLIENT_KEY": "your_client_key",
"LULU_CLIENT_SECRET": "your_client_secret"
}
}
}
}Добавьте этот сервер MCP в конфигурацию Windsurf:
Создайте или отредактируйте файл .windsurf/config.json в каталоге вашего проекта.
Добавьте следующую конфигурацию:
{
"mcpServers": {
"lulu-print": {
"command": "lulu-print-mcp",
"env": {
"LULU_CLIENT_KEY": "your_client_key",
"LULU_CLIENT_SECRET": "your_client_secret"
}
}
}
}Для настройки разработки с помощью Windsurf:
{
"mcpServers": {
"lulu-print": {
"command": "tsx",
"args": ["src/index.ts"],
"cwd": "/path/to/lulu-print-mcp",
"env": {
"LULU_CLIENT_KEY": "your_client_key",
"LULU_CLIENT_SECRET": "your_client_secret"
}
}
}
}Рассчитайте стоимость задания на печать, не создавая его:
calculate-print-job-cost
line_items: Array of items to price
- pod_package_id: Product SKU (e.g., "0600X0900BWSTDPB060UW444MXX")
- page_count: Number of pages
- quantity: Number of copies
shipping_address: Delivery address
- street1: Street address
- city: City name
- country_code: 2-letter ISO country code
- postcode: Postal code
- phone_number: Contact phone
shipping_option: MAIL | PRIORITY_MAIL | GROUND | EXPEDITED | EXPRESSСоздайте новый заказ на печать:
create-print-job
line_items: Array of books to print
- title: Book title
- cover_url: URL to cover PDF
- interior_url: URL to interior PDF
- pod_package_id: Product SKU
- quantity: Number of copies
shipping_address: Delivery address
- name: Recipient name
- street1: Street address
- city: City
- country_code: 2-letter ISO code
- postcode: Postal code
- phone_number: Phone
contact_email: Email for order communication
shipping_level: MAIL | PRIORITY_MAIL | GROUND | EXPEDITED | EXPRESS
external_id: Your order reference (optional)Список заданий на печать с дополнительными фильтрами:
list-print-jobs
page: Page number (optional)
page_size: Results per page (optional)
status: Filter by status (optional)
created_after: Filter by creation date (optional)
created_before: Filter by creation date (optional)Получите подробную информацию о конкретном задании печати:
get-print-job
id: Print job IDОбновить задание на печать (только до оплаты):
update-print-job
id: Print job ID
external_id: New reference (optional)
contact_email: New email (optional)Отменить задание на печать (только если оно неоплачено):
cancel-print-job
id: Print job IDПолучите текущий статус задания на печать:
get-print-job-status
id: Print job IDПолучите подробную стоимость печати:
get-print-job-costs
id: Print job IDПолучите статистику заданий печати за определенный период времени:
get-print-job-statistics
start_date: Start date (YYYY-MM-DD) (optional)
end_date: End date (YYYY-MM-DD) (optional)
group_by: DAY | WEEK | MONTH (optional)Проверьте внутренний PDF-файл:
validate-interior-file
file_url: URL to interior PDF
pod_package_id: Product SKU (optional, for normalization)Проверьте статус проверки:
get-interior-validation
validation_id: ID from validate-interior-fileРассчитайте необходимые размеры чехла:
calculate-cover-dimensions
pod_package_id: Product SKU
page_count: Number of interior pages
unit: IN | MM | PT (optional, default: PT)Проверьте файл PDF обложки:
validate-cover-file
file_url: URL to cover PDF
pod_package_id: Product SKU
page_count: Number of interior pagesПроверьте статус проверки обложки:
get-cover-validation
validation_id: ID from validate-cover-fileПолучите доступные варианты доставки:
get-shipping-options
country_code: 2-letter ISO country code
state_code: State/province code (optional)
quantity: Number of items (optional)
pod_package_id: Product SKU (optional)
page_count: Number of pages (optional)
level: Filter by specific level (optional)Создайте подписку на вебхук:
create-webhook
url: Webhook endpoint URL
topics: Array of events (currently supports ["PRINT_JOB_STATUS_CHANGED"])Список всех подписок на веб-перехватчики:
list-webhooksПолучить данные вебхука:
get-webhook
id: Webhook IDОбновите вебхук:
update-webhook
id: Webhook ID
url: New URL (optional)
topics: New topics (optional)
is_active: Enable/disable (optional)Удалить вебхук:
delete-webhook
id: Webhook IDОтправьте тестовый вебхук:
test-webhook
id: Webhook ID
topic: PRINT_JOB_STATUS_CHANGEDСписок попыток доставки вебхука:
list-webhook-submissions
webhook_id: Filter by webhook (optional)
page: Page number (optional)
page_size: Results per page (optional)Для идентификации продукции Lulu использует 27-символьную систему артикулов:
Формат : Trim Size + Color + Print Quality + Bind + Paper + PPI + Finish + Linen + Foil
Артикул | Описание |
| 8,5" x 11" черно-белая стандартная льняная упаковка с темно-синим льном и золотой фольгой |
| 6" x 9" полноцветная стандартная мягкая обложка с глянцевой обложкой |
| 7" x 10" полноцветная книга премиум-класса в рулонном переплете с матовой обложкой |
| 6" x 9" черно-белая стандартная мягкая обложка с матовой обложкой |
Используйте калькулятор цен Lulu для расчета артикулов, соответствующих вашим конкретным потребностям.
Чтобы использовать среду песочницы Lulu для тестирования:
Создайте учетную запись sandbox на сайте https://developers.sandbox.lulu.com/
Получите учетные данные API вашей песочницы
Установите LULU_USE_SANDBOX=true в вашем .env файле
Или используйте флаг --sandbox при запуске CLI: lulu-print-mcp --sandbox
В режиме песочницы:
Используйте тестовые номера кредитных карт для платежей
Заказы не будут отправлены в реальное производство.
Идеально подходит для разработки и тестирования
lulu-print-mcp [options]
Options:
-s, --sandbox Use Lulu sandbox environment instead of production
-d, --debug Enable debug logging
-h, --help Display help
-V, --version Display versionПроверьте правильность вашего клиентского ключа и секрета.
Проверьте, используете ли вы правильную среду (производственную или песочницу)
Убедитесь, что ваши учетные данные API имеют необходимые разрешения.
Обеспечьте публичный доступ к файлам PDF через URL
Проверьте требования к формату файла в документации Lulu.
Проверьте, соответствуют ли количество страниц и размеры спецификациям продукта.
Проверьте подключение к Интернету
Убедитесь, что настройки брандмауэра разрешают HTTPS-подключения к api.lulu.com.
Включите режим отладки, чтобы увидеть подробные журналы запросов/ответов.
Вклады приветствуются! Пожалуйста, не стесняйтесь отправлять запрос на включение.
Массачусетский технологический институт
Calculate the cost of a print job without creating it
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | Yes | Lulu product ID | |
| quantity | Yes | Number of copies |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It clearly indicates this is a read-only calculation tool (not creating anything), which is helpful. However, it doesn't mention potential limitations like rate limits, authentication requirements, or what specific cost components are included in the calculation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that communicates the essential purpose without any wasted words. It's appropriately sized for a simple calculation tool and front-loads the key information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 2-parameter calculation tool with no annotations and no output schema, the description provides adequate but minimal context. It clearly states the purpose but doesn't explain what the output looks like (cost format, currency, breakdown) or any prerequisites for successful calculation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents both parameters. The description doesn't add any additional meaning or context about the parameters beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('calculate the cost') and resource ('print job'), and explicitly distinguishes it from the alternative action of creating a print job. This provides excellent clarity about what the tool does and what it doesn't do.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context about when to use this tool ('without creating it'), which implicitly suggests it's for cost estimation before actual creation. However, it doesn't explicitly mention when NOT to use it or provide specific alternatives beyond the implied contrast with creation tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get specifications and details for a Lulu product
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | Yes | Lulu product ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. The description states it 'gets' details, implying a read-only operation, but doesn't clarify permissions, rate limits, error conditions, or what 'specifications and details' includes. For a tool with zero annotation coverage, this is insufficient behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, achieving optimal conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, and output format. Without annotations or output schema, the agent must rely heavily on the description, which is incomplete for informed tool selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with the single parameter 'product_id' documented as 'Lulu product ID'. The description doesn't add any parameter-specific information beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and resource ('specifications and details for a Lulu product'), making the purpose understandable. However, it doesn't differentiate from the sibling tool 'calculate-print-job-cost', which appears unrelated but could potentially overlap in product context. The description is specific but lacks sibling distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions. With only one sibling tool that seems unrelated (cost calculation), the lack of explicit usage guidelines leaves the agent to infer based on tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
calculate-print-job-costget-product-detailsScored across 2 tools
The two tools have completely distinct purposes: one calculates costs for print jobs, while the other retrieves product specifications. There is no overlap in functionality, making it impossible for an agent to confuse them.
Both tools use a verb-object naming pattern, but they mix conventions: 'calculate-print-job-cost' uses kebab-case, while 'get-product-details' uses hyphenation inconsistently with the first. The verbs 'calculate' and 'get' are clear but not perfectly aligned in style.
With only two tools, the server feels thin for a print service domain. It lacks essential operations like creating print jobs, managing orders, or handling payments, which are core to such a service. The count is too low for the apparent scope.
The tool surface is severely incomplete for a print service. It covers cost calculation and product details but misses critical operations such as job creation, order submission, status tracking, and payment processing, leaving significant gaps that will cause agent failures.
Furgonetka MCP Server is an extension for LLMs (such as Claude) that integrates AI assistants with Poland's most popular courier brokerage platform. The server enables models to interact directly with services from various couriers (including InPost, DPD, DHL, UPS, and Poczta Polska) through a single, unified interface. With this integration, your AI stops just "writing about logistics" and starts actually managing it.
Publish and schedule videos to TikTok, YouTube Shorts, Instagram, Facebook, LinkedIn, Pinterest, Bluesky, Threads and X from Claude, Cursor or any MCP client. Upload once, post everywhere, track views in unified analytics, and retry failed posts. Official platform APIs only, free plan available. Docs: https://docs.multi-upload-tool.com/mcp
Connect Amazon Seller Central to Claude or ChatGPT via MCP. Orders, inventory, pricing, fees, FBA.
Create projects, nodes, and tasks in UluP Spaces by conversation with Claude.
