📌 For Operators. This guide walks you through the full end-to-end process of connecting Twitter/X to Poke using a self-hosted MCP server on Railway. Written to be shareable — feel free to pass this along.

Overview

Poke supports custom MCP (Model Context Protocol) servers, which lets you extend it with any tool — including Twitter/X. Because Twitter/X's API requires a paid developer account and OAuth credentials, there are a few moving parts to wire together. This guide covers every step.

What you'll end up with: A Railway-hosted MCP server that authenticates with your Twitter/X account and exposes Twitter tools (search, post, DMs, etc.) directly inside Poke.

Time to complete: ~30–45 minutes.

Section 1: Twitter Developer Portal Setup

1.1 Create a Developer Account

  1. Go to developer.twitter.com and sign in with your X account.
  2. Apply for a developer account if you don't have one. Basic tier ($0) is fine for read access; for write access (posting tweets, DMs), you'll need Basic paid access — more on this in Section 4.
  3. Once approved, you'll land on the Developer Portal dashboard.

1.2 Create a Project and App

  1. In the dashboard, click Projects & Apps → New Project.
  2. Name your project (e.g. poke-mcp) and select a use case ("Making a bot" or "Exploring the API" both work).
  3. Create an App within the project. Give it a name (e.g. x-twitter-mcp).

1.3 Set App Permissions

  1. Inside your App, go to Settings → User authentication settings.
  2. Enable OAuth 2.0.
  3. Set App permissions based on what you need: