CSS class names as documentation — Chaparral Software MCP MCP Resource
CSS class names as documentation
is one of 25 resources on the
Chaparral Software MCP
MCP server. Connect the server and your client can attach it as context.
by client
How to attach CSS class names as documentation from your client
- Claude Code Chaparral Software MCP Resource/CSS class names as documentation run in your project directory
- Claude Desktop Chaparral Software MCP Resource/CSS class names as documentation ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Chaparral Software MCP Resource/CSS class names as documentation ~/.cursor/mcp.json
- VS Code Chaparral Software MCP Resource/CSS class names as documentation .vscode/mcp.json
- Zed Chaparral Software MCP Resource/CSS class names as documentation ~/.config/zed/settings.json
- Windsurf Chaparral Software MCP Resource/CSS class names as documentation ~/.codeium/windsurf/mcp_config.json
- Cline Chaparral Software MCP Resource/CSS class names as documentation ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Chaparral Software MCP Resource/CSS class names as documentation ~/.gemini/settings.json
- Grok Chaparral Software MCP Resource/CSS class names as documentation .mcp.json (in your project root)
- ChatGPT Chaparral Software MCP Resource/CSS class names as documentation Settings → Connectors → Advanced → Developer mode
- Claude.ai Chaparral Software MCP Resource/CSS class names as documentation Settings → Connectors → Add custom connector
- LangChain Chaparral Software MCP Resource/CSS class names as documentation pip install langchain-mcp-adapters
Other resources on this server
- 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
- 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.