Gam Seller MCP Node vs Tin
A side-by-side look at the Gam Seller MCP Node and Tin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gam Seller MCP Node for marketing work as a local process; 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?
Choose Gam Seller MCP Node when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MCP_CONFIG_DIR, MCP_REQUIRE_IDEMPOTENCY_KEY.
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 | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 44/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MCP_CONFIG_DIRMCP_REQUIRE_IDEMPOTENCY_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 264 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gam Seller MCP Node | View Tin |
Tools & capabilities
Gam Seller MCP Node 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.
Gam Seller MCP Node
{
"mcpServers": {
"gam-seller-mcp-node": {
"command": "npx",
"args": [
"-y",
"gam-seller-mcp-node"
],
"env": {
"MCP_CONFIG_DIR": "YOUR_MCP_CONFIG_DIR_HERE",
"MCP_REQUIRE_IDEMPOTENCY_KEY": "YOUR_MCP_REQUIRE_IDEMPOTENCY_KEY_HERE"
}
}
}
}
Tin
{
"mcpServers": {
"tin": {
"url": "https://app.tin.computer/mcp"
}
}
}
Frequently asked questions
Gam Seller MCP Node is categorized under Marketing and uses a local stdio subprocess. Tin belongs to Marketing and uses a remote HTTP/SSE transport. Pick Gam Seller MCP Node 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.
Gam Seller MCP Node has no declared pricing — check the project's own site. 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 gam-seller-mcp-node and tin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gam Seller MCP Node has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Tin has 45/100 (Fair) with 1 views, 0 installs and 264 GitHub stars.