Server Details
UPDATED 9/1/2025! NEW TOOLS! Use the Redis Stream tools with n8n MCP Client Node for use anywhere!…
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
21 toolscleanup_processed_streamsTry in Inspector
Clean up processed entries from Redis streams
| Name | Required | Description | Default |
|---|---|---|---|
| dryRun | No | Preview cleanup without executing | |
| streamName | No | Stream name to clean | events:raw |
configure_auto_saveTry in Inspector
Configure automatic context saving with custom frequency
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Topic to auto-save | |
| enabled | No | Enable/disable auto-save | |
| frequency | No | Save frequency: 1min, 5min, 10min, 30min, 1hour, daily, or cron expression | 5min |
delete_contextTry in Inspector
Delete context for a specific topic
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Topic to delete |
emergency_backup_streamTry in Inspector
Create emergency backup of Redis stream data to prevent data loss
| Name | Required | Description | Default |
|---|---|---|---|
| streamName | No | Stream to backup | events:raw |
| backupLocation | No | Backup identifier | emergency_backup |
export_contextsTry in Inspector
Export all contexts to JSON format
| Name | Required | Description | Default |
|---|---|---|---|
| topics | No | Specific topics to export (empty for all) |
find_similar_eventsTry in Inspector
Find semantically similar events using vector search
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum results to return | |
| description | Yes | Description of what to search for |
get_auto_save_statusTry in Inspector
Get current auto-save configuration and status
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Topic to check auto-save status |
get_circuit_breaker_statusTry in Inspector
Get current circuit breaker status and failure counts
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_contextTry in Inspector
Get or create context for a topic or project
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Topic or project name | |
| autoCreate | No | Automatically create if not found |
get_context_historyTry in Inspector
Get history of updates for a topic
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum history entries | |
| topic | Yes | Topic to get history for |
get_stream_contextTry in Inspector
Get context data directly from Redis events:raw stream
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum entries to return | |
| topic | Yes | Context topic to search for |
get_stream_healthTry in Inspector
Get health status of Redis streams and processing pipeline
| Name | Required | Description | Default |
|---|---|---|---|
| streamName | No | Stream name to check | events:raw |
get_temporal_patternsTry in Inspector
Analyze temporal patterns in events
| Name | Required | Description | Default |
|---|---|---|---|
| groupBy | No | Group by: hour, day, timeOfDay | hour |
| timeframe | No | Timeframe: 1h, 24h, 7d, 30d | 24h |
list_topicsTry in Inspector
List all available topics/projects
| Name | Required | Description | Default |
|---|---|---|---|
| pattern | No | Optional filter pattern | * |
search_contextTry in Inspector
Search for similar contexts using semantic search
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum results to return | |
| query | Yes | Search query |
search_person_historyTry in Inspector
Search for all interactions with a specific person
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Person's name or email to search for | |
| limit | No | Maximum results to return |
trigger_recovery_scanTry in Inspector
Manually trigger a recovery scan for stuck entries
| Name | Required | Description | Default |
|---|---|---|---|
| forceReset | No | Force reset circuit breakers before scan |
update_contextTry in Inspector
Update or add context for a topic or project
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Update mode | append |
| topic | Yes | Topic or project name | |
| context | No | Context data to store or append |
update_processing_statusTry in Inspector
Update processing status for a stream entry
| Name | Required | Description | Default |
|---|---|---|---|
| pgStatus | No | PostgreSQL processing status | |
| streamId | Yes | Stream entry ID to update | |
| errorDetails | No | Error details if failed | |
| qdrantStatus | No | Qdrant processing status |
update_stream_contextTry in Inspector
Write context data directly to Redis events:raw stream
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Context topic | |
| context | No | Context data to store | |
| metadata | No | Additional metadata |
verify_data_integrityTry in Inspector
Verify data integrity across Redis, PostgreSQL, and Qdrant
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Specific topic to verify (all if not specified) | |
| skipVector | No | Skip vector verification for faster check |
FAQ
How do I claim this server?
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
What are the benefits of claiming a server?
- Control your server's listing on Glama, including description and metadata
- Receive usage reports showing how your server is being used
- Get monitoring and health status updates for your server