Skip to main content
Glama
discountry

x-post-mcp

by discountry
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

x-post-mcp

A minimal MCP server for posting tweets to X (Twitter) via API v2. Zero runtime dependencies.

Installation

npm install -g x-post-mcp
# or
npx x-post-mcp

Related MCP server: x-mcp

Configuration

Add to your MCP client configuration:

{
  "mcpServers": {
    "x-post-mcp": {
      "command": "npx",
      "args": ["x-post-mcp"],
      "env": {
        "X_BEARER_TOKEN": "<your-bearer-token>"
      }
    }
  }
}

Getting a Bearer Token

See the detailed step-by-step guide: English | 中文

Quick overview:

  1. Go to X Developer Portal

  2. Create a project and app

  3. Configure User Authentication with Read and write permission

  4. Generate OAuth 2.0 Token with tweet.read, tweet.write, users.read, offline.access scopes

Recommended: Use auto-refresh configuration with X_CLIENT_ID, X_CLIENT_SECRET, and X_REFRESH_TOKEN to avoid manual token refresh every 2 hours.

Tool

send_tweet

Post a new tweet to X.

Parameter

Type

Required

Description

text

string

✓

Tweet content

reply_to_tweet_id

string

Tweet ID to reply to

quote_tweet_id

string

Tweet ID to quote

Skill Example

You can create a skill file to help AI agents use this MCP. Save as .claude/skills/post-tweet.md:

# Post Tweet Skill

Post a tweet to X (Twitter) using the x-post-mcp server.

## Instructions

1. Confirm the tweet content with the user before posting
2. Call the `send_tweet` tool with the user's message
3. Report the result back to the user

## Examples

**Simple tweet:**
User: 帮我发一条推文：Hello World!
Assistant: [calls send_tweet with text: "Hello World!"]

**Reply to a tweet:**
User: 回复这条推文 1234567890：感谢分享！
Assistant: [calls send_tweet with text: "感谢分享!", reply_to_tweet_id: "1234567890"]

**Quote tweet:**
User: 引用推文 1234567890 并评论：这个观点很有意思
Assistant: [calls send_tweet with text: "这个观点很有意思", quote_tweet_id: "1234567890"]

License

MIT

Available Tools

1 tool
send_tweetA

Post a new tweet to X (Twitter)

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesThe content of the tweet
quote_tweet_idNoOptional: Tweet ID to quote
reply_to_tweet_idNoOptional: Tweet ID to reply to

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the behavioral disclosure burden. It accurately conveys the core behavior (creating and publishing a tweet) but does not mention side effects, authentication requirements, rate limits, or irreversibility. For a simple, well-known action this is acceptable but not richly transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with zero filler. Every word contributes meaning, and it is appropriately sized for a straightforward action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, full schema coverage, and absence of an output schema, the description plus schema is enough for an agent to invoke the tool correctly. It could mention response/error behavior, but that omission is minor for a basic create operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all three parameters (text, quote_tweet_id, reply_to_tweet_id). The description adds no extra parameter-level detail, meriting the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Post a new tweet to X (Twitter)' uses a specific verb (post) and a specific resource (tweet on X/Twitter), making the tool's function immediately clear. It is not a tautology and needs no sibling differentiation because no siblings exist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The action is unambiguous — the tool is for creating a new tweet. There are no sibling tools to contrast with and no prerequisites to list, so the description's clear context is sufficient, even though it doesn't explicitly state 'use when...' or mention exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.1.0
    • First observedsend_tweet
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlapping purposes. The tool's purpose is clear and unique.

Naming Consistency5/5

The single tool name 'send_tweet' follows a clear verb_noun pattern and is consistent. With only one tool, there are no inconsistencies to evaluate.

Tool Count4/5

One tool is slightly below the typical well-scoped range, but it is reasonable for a narrowly focused posting service. The count feels minimal yet sufficient for the stated purpose.

Completeness4/5

The tool covers the core action of posting a tweet, which is the server's stated purpose. Minor gaps exist, such as no ability to delete or read tweets, but these are not essential for a post-only tool and can be worked around.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • X(Twitter) V2 MCP Server

    NexusX-MCP
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server for interacting with the Twitter/X API v2, enabling AI assistants to retrieve tweets, post content, reply, quote, and more programmatically.
    2,013
    13
    MIT

  • x-mcp

    khajaphysist
    F
    license
    A
    quality
    D
    maintenance
    An MCP server for interacting with X/Twitter, enabling posting tweets, searching, user info, timeline, liking, retweeting, and deleting tweets.
    7
    16
    1
    -

  • x-mcp-server

    HosakaKeigo
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that enables posting tweets, reading timelines, searching posts, and interacting with X (Twitter) API.
    15
    2
    MIT

  • X-MCP

    mhqamx
    F
    license
    A
    quality
    D
    maintenance
    A Node.js MCP server for X/Twitter that enables user profile queries, tweet search, tweet detail retrieval, and media downloads (images, videos, GIFs) via X's Web GraphQL API.
    6
    2
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/discountry/x-post-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server