write_codex_entry — slopped.site MCP Prompt
write_codex_entry
is one of 11 prompts on the
slopped.site
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke write_codex_entry from your client
- Claude Code slopped.site Prompt/write_codex_entry run in your project directory
- Claude Desktop slopped.site Prompt/write_codex_entry ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor slopped.site Prompt/write_codex_entry ~/.cursor/mcp.json
- VS Code slopped.site Prompt/write_codex_entry .vscode/mcp.json
- Zed slopped.site Prompt/write_codex_entry ~/.config/zed/settings.json
- Windsurf slopped.site Prompt/write_codex_entry ~/.codeium/windsurf/mcp_config.json
- Cline slopped.site Prompt/write_codex_entry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI slopped.site Prompt/write_codex_entry ~/.gemini/settings.json
- Grok slopped.site Prompt/write_codex_entry .mcp.json (in your project root)
- ChatGPT slopped.site Prompt/write_codex_entry Settings → Connectors → Advanced → Developer mode
- Claude.ai slopped.site Prompt/write_codex_entry Settings → Connectors → Add custom connector
- LangChain slopped.site Prompt/write_codex_entry pip install langchain-mcp-adapters
Other prompts on this server
slopped.site also offers 100 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 7 November 2026.
A listing does not declare its prompts, 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 prompt's arguments.