Question 1

How do I authenticate with Twitter/X?

Accepted Answer

To authenticate with Twitter/X, you need to provide the following credentials via HTTP headers:

**Required:**
- `X-Twitter-Token`: Twitter/X API token or access token

Question 2

What are the rate limits?

Accepted Answer

Rate limits are determined by the Twitter/X API. The MCP server passes through your credentials and respects the API's rate limits. Check Twitter/X's documentation for specific limits based on your plan.

Question 3

How are errors handled?

Accepted Answer

Errors from the Twitter/X API are returned with descriptive messages. Common errors include authentication failures (invalid or expired tokens), rate limiting, and permission errors. Check the error message for specific details and troubleshooting steps.

Question 4

Is my data secure?

Accepted Answer

Your credentials are passed via HTTP headers and are not stored by the MCP server. All communication uses HTTPS encryption. The server acts as a proxy and does not log or retain your data beyond what's needed for the request.

Question 5

What can I do with the Twitter/X MCP server?

Accepted Answer

The Twitter/X MCP server allows you to interact with Twitter/X's API through natural language. Common use cases include retrieving data, creating and updating records, searching, and automating workflows. See the available tools for specific capabilities.

Question 6

What permissions does my API token need?

Accepted Answer

The required permissions depend on which tools you want to use. For read-only operations, basic read access is sufficient. For creating or modifying data, you'll need write permissions. Check Twitter/X's documentation for specific scopes and permissions.

Twitter/X

Frequently Asked Questions

Still have questions?