Ablestack

You run an MCP server that exposes ABLESTACK MOLD API capabilities as MCP tools. This server lets you connect, call, debug, and auto-register MOLD API endpoints through the mold_* tool namespace, enabling dynamic exploration and verification of the MOLD API from your MCP client.

How to use

You connect to the MCP server using a client that supports MCP. Start by configuring the connection information so the client can reach the server and authenticate requests. Once connected, you can call arbitrary MOLD API endpoints, inspect signatures, and read or register available APIs on demand. Use the provided mold_getConfig and mold_setConfig tools to review and persist endpoint, API key, secret, and signature algorithm settings. The mold_call tool lets you perform arbitrary API calls, while mold_signDebug helps you verify the normalization, signature, and final URL before performing calls. Use mold_autoRegisterApis to discover every API described by the listApisMeta data and automatically register them as individual tools like mold_<APIname> for quick access.

If you are working with asynchronous operations, you can leverage the isAsync support by appending _wait, _timeoutMs, and _intervalMs options to the respective API tools. Complex nested parameters automatically flatten into bracket notation (for example, details[0].cpuNumber=8). You can toggle the signing algorithm between SHA1 and SHA256 to match client and server expectations. When debugging, mold_signDebug helps you compare the normalized string, signature, and final request URL to quickly locate issues.

How to install

Prerequisites you need: Node.js version 18 or newer, and network access to reach the MOLD API endpoint.

# Install dependencies
npm i

# Run in stdio mode
node server.js

Configuration and workflow notes

Configure the MCP client to connect to the mold server by providing the endpoint, API key, secret, and signing algorithm. You can enable automatic registration of all APIs at startup if you want the client to dynamically register every available API as a separate mold_<APIname> tool.

Environment variables you may set for the server (or per client) include MOLD_ENDPOINT, MOLD_API_KEY, MOLD_SECRET_KEY, MOLD_SIG_ALGO, and MOLD_AUTOREGISTER. You can modify and persist these settings using mold_setConfig, which can also write to disk for persistence at ~/.config/mcp-mold/config.json with restricted permissions.

Security and best practices

Treat API and secret keys as sensitive information. If you suspect a compromise, rotate keys immediately. Use the SHA256 signing algorithm by default and ensure the client and server agree on the algorithm. In stdio mode, route logs to stderr and keep stdout protocol-only to avoid leaking sensitive information.

Troubleshooting tips

If you encounter a 401 signature error, verify that the hash algorithm matches on both sides, remove extraneous whitespace or newlines from keys, and ensure the canonicalized string is properly formatted with lowercase keys, sorted order, proper URL encoding, and spaces encoded as %20. If 401 persists, check for network access restrictions or permission issues. Use mold_signDebug to compare the normalized string and the final URL to quickly identify the mismatch.

Examples and capabilities overview

Key capabilities include reading and setting connection info, performing arbitrary API calls, debugging signatures, automatically registering APIs, and polling asynchronous operations. You can browse available APIs through mold_listApisMeta and then call them via mold_<APIname> tools that are automatically created after registration.

Notes on tools and parameters

The core tools include mold_getConfig for viewing current endpoint and credentials, mold_setConfig for configuring and persisting connection details, mold_call for arbitrary API calls, mold_signDebug for signature debugging, mold_listApisMeta for metadata, and mold_autoRegisterApis for dynamic tool generation. After auto-registration, asynchronous APIs accept _wait, _timeoutMs, and _intervalMs to control polling.

Available tools

mold_getConfig

View current endpoint, API key (masked), algo, and config path

mold_setConfig

Set and persist connection information including endpoint, apiKey, secret, and algo

mold_signDebug

Show the normalized string, signature, and final URL for a given command and parameters

mold_call

Invoke an arbitrary API call with specified command and parameters

mold_listApisMeta

Query listApis metadata to discover API names, async status, and expected parameters

mold_autoRegisterApis

Dynamically register all APIs as individual mold_<APIname> tools

mold_<API명>

Independently registered tools for each API after auto registration