TwitterAPI.io MCP Server
A Model Context Protocol (MCP) server that provides LLM applications with access to Twitter data through the TwitterAPI.io service. This server enables AI assistants like Claude to retrieve and analyze tweets, user profiles, and other Twitter data in a structured way.
🚀 Features
Resources
- Tweet data by ID (
tweet://{tweet_id}) - Tweet replies (
tweet://{tweet_id}/replies) - Tweet retweeters (
tweet://{tweet_id}/retweeters) - User profiles (
user://{username}) - User tweets (
user://{username}/tweets) - User followers (
user://{username}/followers) - User following (
user://{username}/following)
Tools
- Basic Twitter operations (get tweet, get user profile, search tweets)
📋 Requirements
- Python 3.8 or higher
- TwitterAPI.io API key
🔧 Installation
Option 1: Direct Installation from PyPI (Recommended)
# Install with pip
pip install twitterapi-mcp
# or with uv for better performance
uv pip install twitterapi-mcp
Option 2: Use with MCP in Claude Desktop (No Installation)
You can use the server directly through uv run by adding to your .mcp.json file:
"twitterapi-mcp": {
"command": "uv",
"args": [
"run",
"twitterapi-mcp"
],
"env": {
"TWITTER_API_KEY": "your_api_key_here"
}
}
Option 3: From Source
- Clone this repository:
git clone https://github.com/DevRico003/twitterapi.io-mcp.git
cd twitterapi.io-mcp
- Install as development package:
pip install -e .
- Configure your TwitterAPI.io API key using environment variables or a
.envfile:
TWITTER_API_KEY=your_api_key_here
LOG_LEVEL=INFO
CACHE_TTL=3600
MAX_TWEETS=100
🚀 Usage
Running the Server
Run directly with Python:
# Run the server package as a module
python -m twitterapi_server
Or use the MCP development mode:
mcp dev twitterapi_server
Install in Claude Desktop
# If you have the package installed:
mcp install -m twitterapi-mcp --name "Twitter API"
# Or directly from the code:
mcp install twitterapi_server --name "Twitter API"
⚙️ Configuration
The server supports the following environment variables:
TWITTER_API_KEY(required): Your TwitterAPI.io API keyLOG_LEVEL(optional): Logging level (default: INFO)CACHE_TTL(optional): Cache timeout in seconds (default: 3600/1 hour)MAX_TWEETS(optional): Maximum tweets per request (default: 100)
📁 Project Structure
.
├── .gitignore
├── LICENSE
├── MANIFEST.in
├── README.md # This file
├── pyproject.toml # Project configuration and dependencies
├── requirements.txt # Dependencies (alternative format)
├── setup.py # Build script (legacy compatibility)
├── twitterapi/ # Main package source code
│ ├── __init__.py
│ ├── api_client.py
│ ├── config.py
│ ├── mcp_server.py
│ ├── utils.py
│ ├── resources/
│ │ ├── __init__.py
│ │ ├── tweet_resources.py
│ │ └── user_resources.py
│ └── tools/
│ ├── __init__.py
│ └── basic_tools.py
└── twitterapi_server/ # Server entry point package
└── __init__.py # Contains main() function
🧪 Testing
Run the tests with pytest:
## 📦 Publishing to PyPI (Developer Notes)
To publish a new version of this package to PyPI:
1. **Increment Version:** Update the `version` number in `pyproject.toml`.
2. **Install Tools:** Make sure you have the necessary tools installed:
```bash
pip install --upgrade build twine
```
3. **Configure Credentials:** Ensure you have a `.pypirc` file in your home directory (`~/.pypirc`) configured with your PyPI API token or username/password. Example:
```ini
[pypi]
username = __token__
password = pypi-your-api-token-here
```
4. **Build the Package:** Generate the distribution archives:
```bash
python -m build
```
This will create `sdist` (.tar.gz) and `wheel` (.whl) files in the `dist/` directory.
5. **Upload to PyPI:** Upload the generated files using twine:
```bash
# Replace X.Y.Z with the new version number
python -m twine upload dist/twitterapi_mcp-X.Y.Z*
# Or upload all files in dist/ (be careful if old versions exist)
# python -m twine upload dist/*
```
python -m pytest
You can run specific test modules:
python -m pytest tests/test_utils.py
python -m pytest tests/test_api_client.py
📊 API Cost Considerations
TwitterAPI.io charges approximately $0.15 per 1,000 tweets retrieved. This server implements caching with a configurable TTL to reduce API costs while maintaining fresh data. The cache is particularly effective for frequently monitored influencers and popular searches.
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for twitterapi-mcp 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| twitterapi_mcp-0.1.4.tar.gz | 17.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| twitterapi_mcp-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.4 kB
Release files / twitterapi_mcp-0.1.4.tar.gz
| Download URL | twitterapi_mcp-0.1.4.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62d528bf572c431a5ff0cbdbbb2b1663946666ac6c4a52421b3c1903d2a0580a
|
|
BLAKE2b-256 checksum How to use checksums |
9cfed5e95d6487d76a4b18a5f2389256c041b5399312870330b5f336613d55f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.0
|
Release files / twitterapi_mcp-0.1.4-py3-none-any.whl
| Download URL | twitterapi_mcp-0.1.4-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11d0998caba4484f9e8b0e84c492d882da21ea5302fb971ffc28d4aabea29c7d
|
|
BLAKE2b-256 checksum How to use checksums |
dce5bae0f993433df0c931b9319d0c087fbfa4df41cb9f641345b946d95dd344
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.0
|
Security for twitterapi-mcp 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.