internal_linking_plan — Seonix MCP Prompt
internal_linking_plan
is one of 11 prompts on the
Seonix
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke internal_linking_plan from your client
- Claude Code Seonix Prompt/internal_linking_plan run in your project directory
- Claude Desktop Seonix Prompt/internal_linking_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Seonix Prompt/internal_linking_plan ~/.cursor/mcp.json
- VS Code Seonix Prompt/internal_linking_plan .vscode/mcp.json
- Zed Seonix Prompt/internal_linking_plan ~/.config/zed/settings.json
- Windsurf Seonix Prompt/internal_linking_plan ~/.codeium/windsurf/mcp_config.json
- Cline Seonix Prompt/internal_linking_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Seonix Prompt/internal_linking_plan ~/.gemini/settings.json
- Grok Seonix Prompt/internal_linking_plan .mcp.json (in your project root)
- ChatGPT Seonix Prompt/internal_linking_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai Seonix Prompt/internal_linking_plan Settings → Connectors → Add custom connector
- LangChain Seonix Prompt/internal_linking_plan pip install langchain-mcp-adapters
Other prompts on this server
Seonix also offers 5 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 14 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.