Twitter MCP Server

Created By
gkydeva year ago
A Unofficial Twitter MCP Server with cookie auth.
Overview

What is Twitter MCP Server?

Twitter MCP Server is an unofficial Model Context Protocol (MCP) server that allows AI assistants to interact with Twitter using cookie-based authentication through the twikit library.

How to use Twitter MCP Server?

To use the server, clone the repository, install the dependencies, and run the server. You will need to provide Twitter cookies (ct0 and auth_token) in each tool call for authentication.

Key features of Twitter MCP Server?

  • Cookie Authentication for secure access
  • Session Caching for efficiency
  • Access to user timelines and tweets
  • User information retrieval
  • Tweet management including posting, liking, and retweeting
  • Search functionality for tweets

Use cases of Twitter MCP Server?

  1. Automating tweet posting and management for social media bots.
  2. Retrieving user statistics and profiles for analytics.
  3. Searching for tweets based on specific queries for research purposes.

FAQ from Twitter MCP Server?

  • Is this server officially supported by Twitter?

No, it uses an unofficial API and is intended for educational and experimental purposes only.

  • How do I obtain the Twitter cookies?

You can get the cookies by logging into Twitter, opening Developer Tools, and copying the ct0 and auth_token values from the cookies section.

  • What happens if my cookies expire?

You will need to obtain new cookies and re-authenticate using the authenticate tool.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gkydev
Star
2
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago