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