Summary
The Conversation Archives MCP server provides read-only access to archived message summaries for a conversation. Archives are automatically created periodically to preserve conversation context while managing memory. Requires conversation API key for authentication.Authentication
This server requires a conversation API key. The key is automatically provided when tools are called within an Agentic Loop.Automatic in Agentic Loops: When using this server within an Agentic Loop, the conversation API key is provided automatically - no manual setup required.
Use Cases
Recalling Past Conversations
User: “What did we talk about last week?” Tool Calls:- Time:
relative-timewith expression “last week” → Returns date range list-archiveswith start_date and end_date from time toolget-archivefor specific archives to show full summaries
Finding Specific Information
User: “Didn’t you recommend a restaurant in our conversation a few days ago?” Tool Calls:- Time:
relative-timewith expression “3 days ago” → Returns specific date get-archivewith date parameter- Parse archive for restaurant recommendation
Browsing Conversation History
User: “Show me a summary of our recent conversations” Tool Calls:list-archiveswith limit 10 → Shows last 10 archive summaries
Available Tools
list-archives
List archived message summaries for the authenticated conversation.| Parameter | Type | Required | Description |
|---|---|---|---|
start_date | string | No | Filter archives from this date (YYYY-MM-DD format) |
end_date | string | No | Filter archives until this date (YYYY-MM-DD format) |
limit | integer | No | Maximum number of archives to return (1-100, default: 30) |
Combine with Time Utilities: Use the Time MCP server’s
relative-time or today tools to convert natural language dates (“last week”, “last month”) to YYYY-MM-DD format for filtering.get-archive
Retrieve the full details of a specific archive by ID or date.| Parameter | Type | Required | Description |
|---|---|---|---|
archive_id | integer | No* | The specific archive ID to retrieve |
date | string | No* | Fetch the archive for a specific date (YYYY-MM-DD format) |
Either/Or Requirement: You must provide either
archive_id or date, but not both.Archive Not Found: If no archive exists for the specified ID or date, an error is returned.
Common Workflows
Recalling Recent Context
Parse User's Time Reference
Use Time:
relative-time to convert “last week”, “3 days ago”, etc. to datesSearching for Specific Information
Browsing History
Archive Generation
Archives are automatically created by the platform to preserve conversation context:When Archives Are Created
- Periodically: Archives are generated at regular intervals (typically daily)
- Context Management: When conversation history exceeds configured limits
- Manual Archival: System administrators can trigger archive creation
What’s Included
- Message Summaries: AI-generated summaries of conversation segments
- Message Count: Total number of messages in the archive
- Date: The date range covered by the archive
- Metadata: Additional context (JSON format, optional)
What’s Not Included
Archives contain summaries, not the original messages. The original message text is not preserved in archives for privacy and storage efficiency.Read-Only Access: This MCP server only provides read access to archives. Archives cannot be created, modified, or deleted via these tools.
Integration with Time Utilities
The Conversation Archives server works seamlessly with the Time Utilities MCP server for date-based filtering:Example: “Show me last month’s archives”
Example: “What did we discuss 3 days ago?”
Tips & Best Practices
- Always use Time tools to convert natural language dates to YYYY-MM-DD format before querying archives
- List before getting - Use
list-archivesfirst to see what’s available, thenget-archivefor specific summaries - Date format is strict - Use YYYY-MM-DD format only (e.g., “2026-02-04”, not “Feb 4, 2026” or “2/4/2026”)
- Archives are summaries - The original message text is not preserved; only AI-generated summaries
- Recent conversations may not yet have archives - Archives are typically generated daily
- Use date ranges to narrow results when searching for specific topics
Date Filtering Best Practices
Good:Archive Retention
Archives are retained according to the platform’s data retention policies:- Standard Retention: Archives are typically retained indefinitely for the lifetime of the conversation
- Privacy: Archives are conversation-specific and only accessible with the conversation’s API key
- No Deletion: The MCP server does not provide tools for deleting archives
Privacy Note: Archives are scoped to individual conversations. The conversation API key ensures that archives are only accessible within their original conversation context.
Error Handling
Common errors and how to handle them:Archive Not Found
Error: “No archive found for date 2026-02-04” Cause: Either no archive exists for that date, or it hasn’t been generated yet. Solution:- Use
list-archivesto see which dates have archives - Check if the date is very recent (archives are generated periodically)
- Verify the date format is correct (YYYY-MM-DD)
Invalid Date Format
Error: “Invalid date format” Cause: Date parameter is not in YYYY-MM-DD format. Solution:- Use Time:
relative-timeortodayto get properly formatted dates - Ensure format is YYYY-MM-DD (e.g., “2026-02-04”, not “Feb 4” or “2/4/2026”)
Unauthorized
Error: “Unauthorized” Cause: Conversation API key is missing or invalid. Solution:- Ensure the MCP server is being called within an Agentic Loop (which provides the key automatically)
- Verify the conversation API key is valid and hasn’t been revoked
API Reference
View the complete API specification for Conversation Archives MCP server endpoints