PindouAI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recent_patternsA | Fetch the most recent public Perler bead and pixel art patterns from the PindouAI gallery. |
| get_website_urlA | Get the official URLs for PindouAI tools, such as the pattern generator and gallery. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_pixel_art | Instructs the user on how to use PindouAI to convert images into Perler bead or pixel art patterns. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one fetches pattern data, the other provides URLs. There is no overlap or ambiguity between them.
Both tools follow the same verb-noun convention with snake_case (get_recent_patterns, get_website_url). The pattern is consistent and predictable.
With only 2 tools, the server feels thin for a general-purpose API. However, the scope appears intentionally narrow, so the count is borderline but not extreme.
The tools cover basic access to recent patterns and URLs, but lack searching, filtering, or detailed retrieval. There are minor gaps that an agent might work around but not critical for the stated purpose.