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