A side-by-side look at the LamaTok and Twitter data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose LamaTok for social media work as a local process; choose Twitter data for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose LamaTok when
You need dedicated capabilities in the Social Media domain.
No tool names declared yet. Check the project README from the listing page.
Twitter data 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.
LamaTok is categorized under Social Media and uses a local stdio subprocess. Twitter data belongs to Social Media and uses a remote HTTP/SSE transport. Pick LamaTok for social media work and Twitter data 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.
LamaTok has no declared pricing — check the project's own site. Twitter data 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 lamatok and relayx-x-twitter-data as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LamaTok has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Twitter data has 25/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.