pulsemcp Safe content atomic mcp-remote

Twitter Connect

The MCP Twitter Connect server provides a bridge to the Twitter API, allowing AI assistants to retrieve recent tweets from specified users. Built with Node.js and Express, it offers two endpoints: a standard REST endpoint (/tweets/:username) and an MCP-compliant endpoint (/mcp) that handles structured requests with proper versioning and error handling. The implementation uses Twitter's v2 API with bearer token authentication to search for recent tweets from a given username. This server is particularly useful for workflows requiring access to real-time Twitter content within AI assistant conversations without requiring direct Twitter API access.

Cognium trust score
50%
Tier
Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.

View full trust & usage report →

Metadata

Version
1.0.0
Skill type
atomic
Execution layer
mcp-remote
Category
social-media
Source
PulseMCP
Author type
human
Updated
2026-04-25
View source Find related skills

Use via MCP

MCP

Resolve Twitter Connect from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp
Swap --scope user for --scope project to commit it to .mcp.json.

Search SkillsRegistry