batpak/events — docs MCP Resource
batpak/events
is one of 50 resources on the
docs
MCP server. Connect the server and your client can attach it as context.
by client
How to attach batpak/events from your client
- Claude Code docs Resource/batpak/events run in your project directory
- Claude Desktop docs Resource/batpak/events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor docs Resource/batpak/events ~/.cursor/mcp.json
- VS Code docs Resource/batpak/events .vscode/mcp.json
- Zed docs Resource/batpak/events ~/.config/zed/settings.json
- Windsurf docs Resource/batpak/events ~/.codeium/windsurf/mcp_config.json
- Cline docs Resource/batpak/events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI docs Resource/batpak/events ~/.gemini/settings.json
- Grok docs Resource/batpak/events .mcp.json (in your project root)
- ChatGPT docs Resource/batpak/events Settings → Connectors → Advanced → Developer mode
- Claude.ai docs Resource/batpak/events Settings → Connectors → Add custom connector
- LangChain docs Resource/batpak/events pip install langchain-mcp-adapters
Other resources on this server
- liteship/architecture
- liteship/astro-runtime-model
- liteship/astro-static-mental-model
- liteship/audit
- liteship/authoring-model
- liteship/capsule-factory
- liteship/documentation-map
- liteship/getting-started
- liteship/glossary
- liteship/hosting
- liteship/package-surfaces
- liteship/overview
- liteship/roadmap
- liteship/skill
- liteship/status
- liteship/typedoc
- liteship/llms-full
- batpak/factory
- batpak/model
- batpak/invariants
- batpak/batteries
- batpak/terminals
- batpak/receipts
- batpak/circuits
- batpak/replay
- batpak/projections
- batpak/integration
- batpak/conformance
- batpak/claude
- batpak/documentation-map
- batpak/overview
- batpak/roadmap
- batpak/llms-full
- macroonz/overview
- macroonz/compiler
- macroonz/harness
- macroonz/macros
- macroonz/compiler/bounded
- macroonz/compiler/closure
- macroonz/compiler/codec
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.