Full Alternative Asset Glossary — Alternative Asset Literacy — Retail MCP Resource

Full Alternative Asset Glossary is one of 2 resources on the Alternative Asset Literacy — Retail MCP server. Connect the server and your client can attach it as context.

by client

How to attach Full Alternative Asset Glossary from your client

• Claude Code Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary run in your project directory
• Claude Desktop Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary ~/.cursor/mcp.json
• VS Code Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary .vscode/mcp.json
• Zed Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary ~/.config/zed/settings.json
• Windsurf Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary ~/.codeium/windsurf/mcp_config.json
• Cline Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary ~/.gemini/settings.json
• Grok Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary .mcp.json (in your project root)
• ChatGPT Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary Settings → Connectors → Advanced → Developer mode
• Claude.ai Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary Settings → Connectors → Add custom connector
• LangChain Alternative Asset Literacy — Retail Resource/Full Alternative Asset Glossary pip install langchain-mcp-adapters

Other resources on this server

• Standard Disclosures

Alternative Asset Literacy — Retail 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.