flightlog
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLIGHTLOG_DB_PATH | No | Database file location | ~/.flightlog/flightlog.db |
| FLIGHTLOG_SYNC_URL | No | PostgreSQL connection string to enable remote sync | |
| FLIGHTLOG_SYNC_INTERVAL | No | Seconds between background sync cycles | 60 |
| FLIGHTLOG_SYNC_ACTIVE_ONLY | No | Only sync sessions with activity in the last 2 hours | true |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flightlog_searchA | Search YOUR past Claude Code conversations — every message, tool call, and thinking block from previous sessions. Use this to recall decisions, plans, code discussions, debugging sessions, or anything discussed in prior conversations that you no longer have in context. Returns matching snippets with session IDs and timestamps. |
| flightlog_get_sessionA | Retrieve the full transcript of a past Claude Code conversation. Use after flightlog_search to read the complete context of a session — see exactly what the user asked, what you answered, what tools were called, and what decisions were made. |
| flightlog_tailA | Get the last N messages from a Claude Code session, most recent first. Use this to check what an agent is currently doing without needing keywords. Much faster than flightlog_get_session for active sessions — returns only recent activity instead of the full transcript. |
| flightlog_list_sessionsB | Browse past Claude Code conversation sessions. Shows when each session happened, which project and git branch it was on, and a preview of the first user message. Use to find a specific past conversation. |
| flightlog_ingestA | Trigger re-indexing of Claude Code conversation logs. Normally runs automatically in near-realtime via file watching. Use this to force a full re-scan if needed. |
| flightlog_statsA | Show how many past conversations are indexed: total sessions, messages, content blocks, database size, compression ratio, and per-project breakdowns. |
| flightlog_delete_sessionsB | Delete indexed conversation sessions and all associated data. At least one filter is required. |
| flightlog_ingest_statusA | Check indexing status: whether the realtime file watcher is active, queue depth of pending files, and ingestion progress. |
| flightlog_rebuildA | Drop and recreate the entire conversation index from scratch. Use when the database is corrupted or schema has changed. |
| flightlog_syncA | Manually trigger sync of local conversation data to remote PostgreSQL. Only available when FLIGHTLOG_SYNC_URL is configured. Use for testing or forcing an immediate sync. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/RobHudson72/flightlog'
If you have feedback or need assistance with the MCP directory API, please join our Discord server