Probo Connect Mcp

io.github.nickymitnickPublished by GitHub account nickymitnickv2.13.0Updated Oct 24, 2026

MCP server for Probo print-on-demand — search products, configure orders, track shipments.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search Probo print-on-demand products, configure print orders, and track shipments through the Probo reseller API.

What you can do
This local MCP server connects an assistant to Probo's print-on-demand service. According to its registry description, it supports searching the product catalog, configuring orders, and tracking shipments. It runs as a local process over stdio and exposes these capabilities as tools to the assistant.
When to use it
Useful when you work with Probo as a reseller and want an assistant to look up printable products, prepare or place orders, and check shipment status without leaving the chat. It is aimed at print-on-demand workflows rather than general e-commerce.
Requirements
Runs locally as an npm package over stdio, so Node.js is needed. Requires a Probo reseller API key supplied through the PROBO_API_KEY environment variable, plus the PROBO_API_MODE variable to choose test (default) or production mode. Network access to the Probo API is required.
Before you install
The server needs a Probo reseller API key (PROBO_API_KEY), which is a credential and should be kept secret. Setting PROBO_API_MODE to production places real orders, which can incur costs; keep it on test until you are sure. Order actions may create or change data on your Probo account.

Installation

In SourceWeft

  1. Open Probo Connect Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.13.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.