| name | tautulli |
| description | Monitor and analyze Plex Media Server usage via Tautulli analytics API. Use when the user asks to "check Tautulli", "Plex analytics", "watch statistics", "viewing trends", "watch time", "who's been watching", "Plex history", "watch history", "most watched", "user activity", "library stats", "plays by platform", "stream analytics", "concurrent streams", "stream limit", "how many streams", "transcode vs direct play", or mentions Tautulli/Plex monitoring and analytics. Prefer this over the plex skill for historical data, usage trends, and statistics. |
Tautulli Analytics Skill
Monitor and analyze Plex Media Server usage through Tautulli's comprehensive analytics API. Track current streams, historical playback data, user activity, and library statistics.
Purpose
This skill provides read-only access to Tautulli analytics:
- Monitor current activity and active streams
- View playback history with detailed filtering
- Track user statistics and viewing patterns
- Analyze library statistics and popular content
- View recently added media with metadata
- Monitor concurrent stream limits and bandwidth
- Analyze usage by time, platform, and stream type
- Track server and library performance metrics
All operations are GET-only and safe for monitoring and analytics.
Note: This skill complements the plex skill by adding analytics and historical data that Plex Media Server doesn't expose directly.
Setup
Add credentials to ~/.config/overseerr-mcp/.env (or ~/.config/overseerr-mcp/.env). Run the config-media-stack skill to configure automatically.
TAUTULLI_URL="http://192.168.1.100:8181"
TAUTULLI_API_KEY="<your_tautulli_api_key>"
TAUTULLI_URL: Your Tautulli server URL with port (default: 8181)
TAUTULLI_API_KEY: Your Tautulli API key
Getting your API key:
- Open Tautulli web UI
- Go to Settings → Web Interface → API
- Enable "API enabled"
- Copy the API key
- Optionally set API HTTP Basic Authentication if desired
Commands
All commands use the tautulli-api wrapper script and return JSON output.
The helper script is located at: skills/tautulli/scripts/tautulli-api
Server Information
Get server identity and version:
bash skills/tautulli/scripts/tautulli-api server-info
Current Activity
Monitor active streams and current playback:
bash skills/tautulli/scripts/tautulli-api activity
Returns: Current streams with user, media, player, bandwidth, transcode info
Playback History
View historical playback data:
bash skills/tautulli/scripts/tautulli-api history
bash skills/tautulli/scripts/tautulli-api history --user "username" --limit 50
bash skills/tautulli/scripts/tautulli-api history --days 7 --media-type movie
bash skills/tautulli/scripts/tautulli-api history --section-id 1 --limit 100
bash skills/tautulli/scripts/tautulli-api history --search "Inception"
Parameters:
--user <username>: Filter by username
--section-id <id>: Filter by library section
--media-type <type>: Filter by movie, episode, track, etc.
--days <n>: History from last N days
--limit <n>: Maximum results (default: 25)
--search <query>: Search in titles
User Statistics
Track user activity and viewing patterns:
bash skills/tautulli/scripts/tautulli-api user-stats
bash skills/tautulli/scripts/tautulli-api user-stats --user "username"
bash skills/tautulli/scripts/tautulli-api user-stats --sort-by plays --limit 10
Parameters:
--user <username>: Specific user statistics
--sort-by <metric>: Sort by plays, duration, last_seen
--limit <n>: Maximum results
--days <n>: Stats from last N days
Library Statistics
Analyze library usage and popular content:
bash skills/tautulli/scripts/tautulli-api libraries
bash skills/tautulli/scripts/tautulli-api library-stats --section-id 1
bash skills/tautulli/scripts/tautulli-api popular --section-id 1 --limit 10
bash skills/tautulli/scripts/tautulli-api popular --media-type movie --days 30
bash skills/tautulli/scripts/tautulli-api popular --media-type show --days 30
Parameters:
--section-id <id>: Specific library section
--media-type <type>: movie (default), show, or music — selects which popularity stat to query
--days <n>: Timeframe for popularity
--limit <n>: Maximum results
Recently Added
View recently added media with rich metadata:
bash skills/tautulli/scripts/tautulli-api recent
bash skills/tautulli/scripts/tautulli-api recent --section-id 1 --limit 50
bash skills/tautulli/scripts/tautulli-api recent --media-type movie --days 7
Home Statistics
Get homepage dashboard statistics:
bash skills/tautulli/scripts/tautulli-api home-stats
bash skills/tautulli/scripts/tautulli-api home-stats --days 30
Stream Analytics
Analyze stream types and platform usage:
bash skills/tautulli/scripts/tautulli-api plays-by-stream --days 30
bash skills/tautulli/scripts/tautulli-api plays-by-platform --days 30
bash skills/tautulli/scripts/tautulli-api plays-by-date --days 30
bash skills/tautulli/scripts/tautulli-api plays-by-hour --days 7
bash skills/tautulli/scripts/tautulli-api plays-by-day --days 30
Concurrent Streams
Monitor concurrent stream patterns by stream type (direct play vs transcode):
bash skills/tautulli/scripts/tautulli-api concurrent-streams --days 30
bash skills/tautulli/scripts/tautulli-api concurrent-streams --days 7
Media Metadata
Get detailed metadata for specific media:
bash skills/tautulli/scripts/tautulli-api metadata --rating-key 12345
bash skills/tautulli/scripts/tautulli-api metadata --guid "plex://movie/5d776..."
Workflow
When the user asks about Plex analytics:
- "Who's watching right now?" → Run
activity
- "What are the most watched movies?" → Run
popular --media-type movie --days 30
- "Show me recent watch history" → Run
history --limit 25
- "How much has [user] watched this week?" → Run
user-stats --user "username" --days 7
- "What's new in my library?" → Run
recent --limit 10
- "When do people watch most?" → Run
plays-by-hour --days 30
- "Are we hitting stream limits?" → Run
concurrent-streams --days 7
Activity Monitoring Flow
- Check current activity for active streams
- If issues detected (buffering, transcoding), investigate specific session
- Review user's watch history to understand patterns
- Check library statistics to identify popular content
- Analyze stream types to optimize server settings
Analytics Flow
- Get home statistics for overview
- Drill into specific libraries with library-stats
- Identify popular content with popular command
- Analyze user behavior with user-stats
- Review temporal patterns with plays-by-hour/date/day
- Monitor platform distribution with plays-by-platform
Output Format
All commands return JSON with standard Tautulli response structure:
{
"response": {
"result": "success",
"message": null,
"data": { ... }
}
}
Use jq to extract and format data:
bash skills/tautulli/scripts/tautulli-api activity | jq '.response.data'
bash skills/tautulli/scripts/tautulli-api history | jq '.response.data.data[] | {user: .friendly_name, title: .full_title, date: .date}'
Notes
- Requires network access to your Tautulli server
- All operations are read-only GET requests
- Tautulli must be connected to your Plex Media Server
- Library section IDs match Plex library section keys
- Historical data depends on Tautulli's configured retention period
- Some statistics require sufficient historical data to be meaningful
- Response times may vary based on database size and query complexity
- Rating keys are Plex's unique identifiers for media items
- User-friendly names are shown by default (can show usernames with flags)
Integration with Plex Skill
This skill complements the plex skill:
- Plex skill: Real-time server state (libraries, search, sessions)
- Tautulli skill: Historical analytics (trends, statistics, watch history)
Use both together:
- Find content with
plex skill search
- Check popularity with
tautulli skill analytics
- Monitor current playback with either skill
- Analyze viewing patterns with
tautulli skill
Multiple Servers
To use multiple Tautulli instances (monitoring different Plex servers):
bash skills/tautulli/scripts/tautulli-api activity
TAUTULLI_URL="http://server2:8181" TAUTULLI_API_KEY="key2" \
bash skills/tautulli/scripts/tautulli-api activity
The plugin config only supports one Tautulli instance. Multiple-server usage requires inline env overrides as shown above.
Reference
For detailed API reference, see:
Agent Tool Usage Requirements
When running script commands via the zsh tool, always pass pty: true — without it, command output will be suppressed even though the command executes successfully.