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