Twitter X Automation vs UGC Agent
A side-by-side look at the Twitter X Automation and UGC Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
U
UGC AgentSocial MediaFind Instagram and TikTok UGC creators with public emails, and see which brands run UGC.25EmergingAuth: not declaredVerdict: choose Twitter X Automation for social media work as a local process; choose UGC Agent for social media. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Twitter X Automation when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | U UGC Agent | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 51/100 · Good | 25/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 591 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Twitter X Automation | View UGC Agent |
Tools & capabilities
Twitter X Automation tools
No tool names declared yet. Check the project README from the listing page.
UGC Agent 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.
Twitter X Automation
{
"mcpServers": {
"twitter-x-automation": {
"command": "npx",
"args": [
"-y",
"xactions"
]
}
}
}
UGC Agent
No confirmed install command for UGC Agent yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Twitter X Automation is categorized under Social Media and uses a local stdio subprocess. UGC Agent belongs to Social Media and uses an install path we have not confirmed yet. Pick Twitter X Automation for social media work and UGC Agent for social media.
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. UGC Agent has no confirmed install command yet — follow its own setup instructions.
Twitter X Automation has no declared pricing — check the project's own site. UGC Agent 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 twitter-x-automation and ugc-agent as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Twitter X Automation has a quality signal of 51/100 (Good) with 1 views, 0 installs and 591 GitHub stars. UGC Agent has 25/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.