Bytario

io.github.helloderekgPublished by GitHub account helloderekgv1.0.1Updated Oct 24, 2026

40 MCP tools for image, PDF, QR, barcode, data, text, color, and render operations.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Bytario exposes 40 MCP tools for image, PDF, QR, barcode, data, text, color, and render operations from a local process.

What you can do
Bytario is a local stdio MCP server that provides 40 tools grouped around image, PDF, QR, barcode, data, text, color, and render operations. The registry description lists these categories but does not detail individual tool names or parameters. It runs on the user's machine and is marked as desktop only, so it is not available as a web executable.
When to use it
Consider it when an assistant needs to generate or process images, PDFs, QR codes, barcodes, colors, or rendered output as part of a local workflow. It is a fit for desktop setups where these operations are frequent enough to justify a dedicated server.
Requirements
Runs as a local process over stdio, installed from the npm package @bytario/mcp, so Node.js is required. A Bytario API key must be supplied in the BYTARIO_API_KEY environment variable; the manifest marks it required and secret. The key is described as an sk_live_ value, and the description points to a pricing page for obtaining one.
Before you install
The server requires a live API key in BYTARIO_API_KEY, which is a secret and should not be exposed in logs or shared configuration. The key format suggests a paid, production account, so usage may incur costs. The manifest declares no authentication beyond this key, and no tool list is provided, so review what each tool does before granting it access to files or data.

Installation

In SourceWeft

  1. Open Bytario 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.

Tools

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

Version history

1
  1. v1.0.1LatestSep 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.