Skillforge Render API

What Skillforge Render API MCP server does

Skillforge Render API MCP server provides agent-accessible rendering for three output types: screenshots, PDF files, and Open Graph images. It is intended for use through the Model Context Protocol, allowing an MCP-compatible client or agent to call the rendering service rather than integrating with the API directly.

The available listing identifies the output categories but does not describe the input format for each operation. It does not state whether the service renders URLs, HTML, templates, files, or another source format. Developers should verify those request details against the service documentation before building an integration.

How it works

An MCP client connects to the Render API through the server and submits a rendering request. The service can be authorized in either of two ways: with a Bearer key or with an x402 USDC payment made for an individual call.

The provided material does not identify the MCP transport, endpoint format, payment network, wallet procedure, response schema, or supported rendering options. Those details are necessary for implementation and are not inferred here. The listing also does not name specific MCP client applications that are supported.

Setup and configuration

Authentication requires one of the access methods stated by the listing. A Bearer key is suitable when the service is configured for key-based access. Per-call x402 USDC is the alternative payment path identified for the server.

No environment variable names, installation command, package name, configuration file, endpoint URL, or example client configuration is provided. Consequently, there is no grounded variable list or setup recipe to reproduce from the available material. Before deployment, confirm how credentials or payment authorization are supplied to the MCP process and how the process is launched by the chosen client.

Tools and capabilities

The documented capabilities are:

• Render screenshots through MCP.
• Render PDF documents through MCP.
• Render Open Graph images through MCP.
• Authenticate with a Bearer key.
• Pay per call with x402 USDC.

The names and signatures of the underlying MCP tools are not provided. The listing also does not establish whether these capabilities share one tool or are exposed as separate tools.

Limitations and notes

Skillforge Render API MCP server should be evaluated against the required rendering inputs, output formats, and authentication workflow before adoption. The available source contains no README, so client compatibility, transport support, rate limits, file-size limits, rendering options, error behavior, and licensing information remain unspecified. No claim can be made here about support for a particular editor, desktop application, agent framework, or payment environment.