Skip to main content
Glama
rocnubie

palsaveeditor-mcp

by rocnubie
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

Pal Save Editor MCP Server

Palworld Save Editor Tool - Inspect Before Changes

MCP Badge Node Read Only License: MIT MCP

A Model Context Protocol server that exposes the canonical Pal Save Editor 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://palsaveeditor.com

🛠️ About Pal Save Editor

Pal Save Editor is a browser-only Palworld save safety workbench. It recognizes local save file sets, compares snapshots, creates a private recognition receipt, and exports a local safe pack while keeping file processing in a Web Worker.

The current release deliberately limits its scope: real Palworld binary mutation is locked, binary comparison is limited to paths, roles, sizes, signatures, and hashes, and field-level semantic diff is available only for documented JSON fixtures. PlM and Oodle files remain read-only, and the tool does not repair bytes or guarantee that Palworld will load an exported candidate.

This MCP exposes those capabilities and safety boundaries as read-only context. It does not receive save files, edit a user's world, or claim that an unsupported repair path exists.

Related MCP server: LessonLab MCP Server

Tools

get_editor_scope

Return the editor workflow and the documented limits on local processing or export. (Pal Save Editor)

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for Pal Save Editor (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

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

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

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

Prompts

tell_me_about_palsaveeditor

Summarize what the site is, who it's for, and how it works. — Pal Save Editor

review_edit_scope_palsaveeditor

Review an editing workflow without promising unsupported file mutation. — Pal Save Editor

Installation

Install via Smithery

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

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

Install from source

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

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

{
  "mcpServers": {
    "palsaveeditor-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/palsaveeditor-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. (Pal Save Editor)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so description carries full burden. It indicates a read operation returning data, which is safe. But it lacks details on potential side effects, rate limits, or response size. Minimal but acceptable.

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

Conciseness4/5

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

Single sentence with parenthetical is concise. However, it could benefit from slightly more structure (e.g., separate sentences for workflow and limits). Still efficient.

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

Completeness3/5

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

For a zero-parameter tool with no output schema, the description is adequate but sparse. It names what is returned but not the format or structure. Could be more complete for agent understanding.

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?

No parameters in schema, description adds no parameter info as none exist. Per guidelines, 0 parameters yields baseline 4. No need for further param detail.

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?

The description clearly states it returns 'editor workflow and documented limits', which is a specific resource. It distinguishes from sibling 'get_official_links' by focusing on editor internals vs links.

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

Usage Guidelines4/5

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

The usage context is clear: to retrieve editor workflow and limits. However, no explicit when-not-to-use or alternatives are provided. Sibling tool is distinct enough that no exclusion is needed.

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

A4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: one returns editor scope/limits, the other returns official links. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools follow a consistent 'get_' prefix with a noun indicating the resource, adhering to a clear verb_noun pattern.

Tool Count3/5

With only 2 tools, the server feels thin for its stated domain ('Pal Save Editor'). It is borderline acceptable, but the scope is very limited.

Completeness2/5

The server only provides informational tools and lacks any core save editing functionality. For a server named 'palsaveeditor-mcp', this is a significant 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/palsaveeditor-mcp'

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