Chaparral Software MCP MCP Resources

Chaparral Software MCP offers 25 resources. A resource is data the server exposes for a client to attach as context — a file, a page, an API response — rather than an action. Each has its own page, per client.

• Chaparral Software Credentials
• Client History
• Pass pointers, verify content — A dispatch-authorship discipline for mu…
• Why AI Projects Fail — What the Evidence Says When You Trace the Citati…
• The Moat Is the Harness — What the Claude Code Leak Really Means
• Fog — Navigating AI Disruption Without a Map
• The Twenty Percent — What AI Can't Build (Yet)
• The Garden Timer — When Nothing Works Anymore
• Ship the constraint
• Primary-source terminal authority
• Role separation is mechanical, not cultural
• Perpetual tomorrow
• Stage names are not stage contracts
• Code is increasingly ephemeral
• Context in the window is not attention in focus
• What 47 analyses of the Claude Code leak missed
• Don't infer what you can detect
• Response budgets: be a good citizen in someone else's context window
• Metadata now, enforcement later
• Self-correction is not verification
• The introspection loop
• Don't vibe code the orchestration layer
• Schema.org @id references across pages
• CSS class names as documentation
• Variable fonts: one file, every weight

Chaparral Software MCP also offers 2 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.