ClipMyApp MCP vs Tin
A side-by-side look at the ClipMyApp MCP and Tin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
ClipMyApp MCPMarketing · Remote HTTP/SSEHosted MCP server for app founders and marketing teams to create, review, edit, approve or reject, and schedule app videos, memes, and carousels from AI assistants. Scoped OAuth and explicit confirmation keep publishing and spend under the account owner control.50GoodAuth: oauth 2.0Verdict: choose ClipMyApp MCP for marketing work over a hosted endpoint; choose Tin for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose ClipMyApp MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose Tin when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C ClipMyApp MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 50/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 263 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View ClipMyApp MCP | View Tin |
Tools & capabilities
ClipMyApp MCP tools
No tool names declared yet. Check the project README from the listing page.
Tin 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.
ClipMyApp MCP
{
"mcpServers": {
"clipmyapp-mcp": {
"url": "https://api.clipmyapp.com/mcp"
}
}
}
Tin
{
"mcpServers": {
"tin": {
"url": "https://app.tin.computer/mcp"
}
}
}
Frequently asked questions
ClipMyApp MCP is categorized under Marketing and uses a remote HTTP/SSE transport. Tin belongs to Marketing and uses a remote HTTP/SSE transport. Pick ClipMyApp MCP for marketing work and Tin for marketing.
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.
ClipMyApp MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Tin 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 clipmyapp-mcp and tin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ClipMyApp MCP has a quality signal of 50/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Tin has 45/100 (Fair) with 1 views, 0 installs and 263 GitHub stars.