Skip to content
Kitbay
MCP server

twitter-api-safe-mcp

Runs locallyMITUpdated on Nov 13, 2026116GitHub starsCan change dataNeeds an API key

An MCP server from fa0311's twitter-api-safe project that sends requests to X's internal web app API through a browser where the user is signed in to X, rather than through X's public developer API.

What it does

An MCP server from fa0311's twitter-api-safe project that sends requests to X's internal web app API through a browser where the user is signed in to X, rather than through X's public developer API. A bridge script is injected into the X page so requests use the page's own client, cookies and request headers; the agent sees only a catalogue of recorded operations and never the credentials. The MCP package runs the project's HTTP relay and dashboard in the same process and offers two tools: list the browser profiles and send an API request. Profiles are either Playwright-managed browser profiles or a running Chromium reached over the DevTools protocol. Using a signed-in session in this way may conflict with X's terms.

Capabilities

  • Call X web app endpoints through a signed-in browser
  • Read timelines and run searches
  • Switch between browser profiles