case-chronology-mcp
by medelman17
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_eventC | Add a chronology event with automatic date parsing |
| parse_documentC | Parse a document and extract potential chronology events |
| search_timelineC | Search chronology by date range, parties, keywords, or tags |
| get_timeline_summaryB | Get summary statistics about the chronology |
| export_chronologyC | Export chronology in various formats |
| update_eventB | Update an existing chronology event |
| delete_eventC | Delete a chronology event |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_schema | Provide information about the chronology data structure |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/medelman17/case-chronology-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server