Skip to main content
Glama
Snehil-Shah

LibreSprite MCP

by Snehil-Shah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
run_scriptB
        Run a JavaScript script inside Libresprite.

        IMPORTANT: Make sure you are well versed with the documentation and examples provided in the resources `docs:reference` and `docs:examples`.

        Args:
            script: The script to execute

        Returns:
            Console output

Prompts

Interactive templates invoked by user choice

NameDescription
libresprite Prompt template to use the libresprite tool with proper context conditioning. Args: prompt: User prompt Returns: Prompt to process

Resources

Contextual data attached and managed by the client

NameDescription
read_referenceRead the libresprite command reference documentation.
read_examplesRead example scripts using libresprite commands.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity between tools. The singular tool has a clear and distinct purpose.

Naming Consistency5/5

The single tool name 'run_script' follows a consistent verb_noun pattern. No inconsistencies exist due to the absence of other tools.

Tool Count2/5

The server provides only one tool for a complex domain (LibreSprite pixel art editor). This is too few for typical workflows, which would require multiple tools for editing, layering, and exporting.

Completeness2/5

The server exposes only a generic script runner, lacking direct tools for common operations like creating, editing, or exporting sprites. While scripting can compensate, the surface is severely incomplete for the stated domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources