Skip to main content
Glama
rocnubie

Tier Maker List MCP Server

by rocnubie
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Local

Tier Maker List MCP Server

Free Tier List Maker With Images | Tier Maker List

MCP Badge License: MIT Read Only Stdio Transport MCP Node

A Model Context Protocol server that exposes the canonical Tier Maker List knowledge surface — browser editing workflows, local processing, and safety boundaries, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

Official website: https://tiermakerlist.com

🛠️ About Tier Maker List

Tier Maker List is a static, image-first tier list maker that opens directly to a blank board. Visitors can rank images by drag or tap, keep drafts locally without signing up, export a PNG or .tierlist.json file, and prepare a challenge for friends.

The public template catalog currently includes Pokemon Starters Gen 1-9 and Pokemon Starter Evolutions. Built-in sharing uses stable item IDs, a template version, tier, and order; custom images are not embedded in the URL. This MCP describes the editor workflow and template boundaries as read-only context, not as a hosted board or image service.

The site runs in the browser with localStorage for drafts and challenge records. Image sources, character rights, and any commercial use of exported boards require their own review.

Related MCP server: aiphotoeditor-mcp

Tools

get_editor_scope

Return the editor workflow and the documented limits on local processing or export. (Tier Maker List)

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for Tier Maker List (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

  • site://tiermakerlist/workbench — Public editing workflow, local-processing model, and documented safety limits.

  • site://tiermakerlist/faq — Short FAQ generated from public site metadata.

  • site://tiermakerlist/links — Canonical URLs to share with users.

Prompts

tell_me_about_tiermakerlist

Summarize what the site is, who it's for, and how it works. — Tier Maker List

review_edit_scope_tiermakerlist

Review an editing workflow without promising unsupported file mutation. — Tier Maker List

Installation

Install via Smithery

npx -y @smithery/cli install tiermakerlist-mcp --client claude

(Replace claude with cursor, windsurf, or continue for those clients.)

Install from source

git clone https://github.com/rocnubie/tiermakerlist-mcp.git
cd tiermakerlist-mcp
pnpm install

Then add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):

{
  "mcpServers": {
    "tiermakerlist-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/tiermakerlist-mcp/src/index.mjs"
      ]
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector node src/index.mjs

Official Links

Development

pnpm install
pnpm start                 # run the server over stdio

License

MIT

Available Tools

2 tools
get_editor_scopeA

Return the editor workflow and the documented limits on local processing or export. (Tier Maker List)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must disclose behavioral traits. It only states what is returned, without mentioning side effects (likely read-only), authentication needs, or performance. For a simple getter, this is minimal – at least a read-only hint would help.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no redundancy. The information is front-loaded and every word is necessary. Excellent conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but the tool has no parameters. The description covers what the tool returns adequately. However, it could be improved by adding that it is a read-only operation or specifying the return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With no parameters and 100% schema coverage, the baseline is 4. The description adds value by explaining what the tool returns (workflow and limits), which is beyond the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses specific verb 'Return' and names the resource: 'editor workflow and the documented limits on local processing or export'. This clearly distinguishes it from the sibling tool 'get_official_links', which likely returns links. The purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus the sibling. The phrase '(Tier Maker List)' provides some context but does not specify alternatives or when not to use. Usage is implied but not directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedget_editor_scope
    • First observedget_official_links
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one provides editor scope and limits, the other returns official links. There is no ambiguity.

Naming Consistency5/5

Both tools follow a consistent 'get_' verb_noun pattern, making them predictable and easy to understand.

Tool Count3/5

With only 2 tools, the server is minimal but arguably appropriate if its sole scope is providing documentation. However, the server name implies broader tier list functionality, making it feel slightly under-scoped.

Completeness1/5

The server name suggests tools for creating or managing tier lists, but the actual tools only return metadata about the server itself. There are no CRUD or lifecycle operations for tier lists, which is a severe gap.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/tiermakerlist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server