founders-archive-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| founders_archive_statusA | Check whether the private transcript corpus and hybrid research index are ready. |
| search_foundersC | Find cited evidence for a strategic question. Run reframed and conflicting-view searches before synthesizing. |
| get_founders_passageA | Expand a cited passage with up to three neighboring passages from the same episode. |
| find_founders_episodeA | Find Founders episodes by exact episode number or partial title. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: status check, search for evidence, expand a passage, and locate an episode. No overlap or ambiguity between them.
All tools follow a consistent verb_noun snake_case pattern (search_founders, get_founders_passage, find_founders_episode) with the exception of founders_archive_status which uses a noun, but it still reads clearly and the pattern is uniform.
Four tools is well-scoped for this server's purpose. Each one earns its place, covering the essential research workflows without bloat.
The server covers status, search, passage expansion, and episode lookup, which are sufficient for core research tasks. A minor gap is the lack of a browse/list function for episodes, but the existing tools handle the primary use cases.