A side-by-side look at the Starcovery and Openshorts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
Openshorts 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.
Starcovery
No confirmed install command for Starcovery yet — follow the setup steps linked from its listing page rather than a guessed package name.
Openshorts
No confirmed install command for Openshorts yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Starcovery is categorized under Social Media and uses an install path we have not confirmed yet. Openshorts belongs to Social Media and uses an install path we have not confirmed yet. Pick Starcovery for social media work and Openshorts for social media.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Starcovery has no declared pricing — check the project's own site. Openshorts has no declared pricing — check the project's own site. 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 starcovery and openshorts as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Starcovery has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Openshorts has 41/100 (Fair) with 2 views, 0 installs and 6,365 GitHub stars.