TwittrAPI vs StoriesIG Instagram MCP
A side-by-side look at the TwittrAPI and StoriesIG Instagram MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TwittrAPISocial Media · Local subprocess (stdio)Read public Twitter/X data: tweets, profiles, followers, search. No X developer account.33EmergingAuth: not declaredS
StoriesIG Instagram MCPSocial Media · Remote HTTP/SSEPublic Instagram data for AI agents: profiles, posts, reels, stories, highlights, comments and more38FairAuth: not declaredVerdict: choose TwittrAPI for social media work as a local process; choose StoriesIG Instagram MCP 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?
TChoose TwittrAPI when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
SChoose StoriesIG Instagram MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T TwittrAPI | S StoriesIG Instagram MCP |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 33/100 · Emerging | 38/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 | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View TwittrAPI | View StoriesIG Instagram MCP |
Tools & capabilities
TwittrAPI tools
No tool names declared yet. Check the project README from the listing page.
StoriesIG Instagram MCP 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.
TwittrAPI
{
"mcpServers": {
"twittrapi": {
"command": "npx",
"args": [
"-y",
"twittrapi-mcp"
]
}
}
}
StoriesIG Instagram MCP
{
"mcpServers": {
"storiesig-instagram-mcp": {
"url": "https://storiesig.info/en/mcp/"
}
}
}
Frequently asked questions
TwittrAPI is categorized under Social Media and uses a local stdio subprocess. StoriesIG Instagram MCP belongs to Social Media and uses a remote HTTP/SSE transport. Pick TwittrAPI for social media work and StoriesIG Instagram MCP 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.
TwittrAPI has no declared pricing — check the project's own site. StoriesIG Instagram MCP 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 twittrapi and storiesig-instagram-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TwittrAPI has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. StoriesIG Instagram MCP has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.