Dream Pixel Forge
io.github.LegorobotdudePublished by GitHub account Legorobotdudev1.0.0Updated Oct 24, 2026
Create and edit on-brand images and videos with reusable character and product references.
Overview
A remote MCP server that lets an assistant generate and edit on-brand images and videos using reusable character and product references.
- What you can do
- Generate images and videos from assistant prompts through the Dream Pixel Forge service, using your account's existing credits. Reuse saved character and product references so results stay on-brand across generations. Edit existing images and videos rather than only creating new ones. No individual tools are listed in the manifest, so exact operations are not documented here.
- When to use it
- Useful when you want an assistant to produce or revise brand-consistent visual content, such as character or product imagery and short videos, without leaving the chat. Less relevant if you only need text or code work.
- Requirements
- A remote endpoint at dreampixelforge.com over streamable HTTP; no local package or runtime. A Dream Pixel Forge account is required, and the Authorization header must carry a bearer token containing your DPF API key from Settings. Generation consumes your existing credits.
Installation
In SourceWeft
- Open Dream Pixel Forge in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Legorobotdude%2Fdream-pixel-forge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"dream-pixel-forge": {
"type": "http",
"url": "https://www.dreampixelforge.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.0LatestSep 20, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.