restate

This MCP server exposes the Restate Admin API as MCP tools, allowing you to manage Restate services, deployments, and related state through the MCP protocol. It provides tools to list and manage services, deploy or update service configurations, cancel or kill ongoing invocations, and query key-value state and other attributes exposed by Restate's introspection schema. Once running, MCP clients can emit requests to the Restate MCP server to perform common administrative tasks without direct REST calls.

To use it, ensure the MCP server is running with the provided mcp_config entry. Use your MCP client to interact with the restate tool namespace exposed by the MCP server. Typical workflows include listing available Restate services, initiating a deployment for a service, and adjusting configuration settings such as idempotency retention. The server will translate MCP requests into Restate Admin API calls under the hood and return results through MCP responses.

Prerequisites:

• Node.js (LTS) installed on your machine
• npm or pnpm to install dependencies

Installation steps:

1. Install dependencies and build the project npm run clean-install && npm run build

2. Ensure the MCP configuration includes the Restate MCP server entry In your MCP config, add: { "mcpServers": { "restate": { "command": "node", "args": [".../restate-mcp-server/dist/index.js"] } } }

3. Run the MCP server using your usual MCP runtime with the above configuration. If you run locally, you can start the node server directly with the path to the built dist index.js as shown in the mcp_config.

4. Verify connectivity by issuing a simple MCP request against the Restate tools namespace and confirming a valid response from the Restate Admin API.

Notes and tips:

• The built artifact is expected under dist/index.js after a successful build; ensure the path in mcp_config points to this file.
• If you modify configuration or environment, restart the MCP server to apply changes.
• The server acts as a translator between MCP requests and the Restate Admin API; ensure proper authentication/authorization is configured on the Restate side if required by your environment.
• Common env vars (if provided by the Restate MCP): set RESTATE_API_URL, RESTATE_API_TOKEN, or any similar credentials your deployment requires. If not used, you can omit or leave placeholders in env.
• When deploying services, ensure your Restate services are reachable from the MCP runtime and that any required networking or firewall rules allow the necessary traffic.