Schema | Codex History Hub

Codex History Hub

Describes the environment variables required to run the server.

Name	Required	Description	Default
`HISTORY_HUB_DB`	No	Path to the SQLite database file for history-hub. Can be set via environment variable or --db argument.	data/history-hub.db

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
history_get_recent_contextB	Get a project overview plus recent primary conversation summaries. Subagents are excluded by default.
history_searchB	Search older cross-account history. Call only when the user explicitly asks to search past history, names an older date/source/topic, or recent context is insufficient.
history_get_threadB	Read a selected history thread after identifying it via recent context or search. Full mode should be used only when the user explicitly requests the full thread.
history_get_project_summaryA	Get the durable overview of a project without loading conversation transcripts.
history_update_project_summaryA	Update the confirmed durable project overview in the independent Hub only. Never writes to any source Codex account/session store.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smallpinksquare/codex-history-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server