Photon vs Roast My Design System
A side-by-side look at the Photon and Roast My Design System MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
PhotonDeveloper ToolsBuild MCP servers, CLI tools, and web dashboards for AI agents from a single TypeScript file.41FairAuth: no auth requiredVerdict: choose Photon for developer tools work; choose Roast My Design System for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
PChoose Photon when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
Choose Roast My Design System when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P Photon | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 41/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 100 | 27 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Photon | View Roast My Design System |
Tools & capabilities
Photon tools
No tool names declared yet. Check the project README from the listing page.
Roast My Design System tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Photon
No confirmed install command for Photon yet — follow the setup steps linked from its listing page rather than a guessed package name.
Roast My Design System
{
"mcpServers": {
"roast-my-design-system-2": {
"command": "npx",
"args": [
"-y",
"roast-my-design-system@latest"
]
}
}
}
Frequently asked questions
Photon is categorized under Developer Tools and uses an install path we have not confirmed yet. Roast My Design System belongs to Developer Tools and uses a local stdio subprocess. Pick Photon for developer tools work and Roast My Design System for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Photon has no confirmed install command yet — follow its own setup instructions.
Photon is listed as free. Auth: no auth required. Roast My Design System is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add portel-photon and roast-my-design-system-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Photon has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 100 GitHub stars. Roast My Design System has 51/100 (Good) with 5 views, 0 installs and 27 GitHub stars.