cognitive.report_outcome — Neotic MCP Prompt

cognitive.report_outcome is one of 3 prompts on the Neotic MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke cognitive.report_outcome from your client

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

Other prompts on this server

• cognitive.solve_with_guidance
• cognitive.contribute_experience

Neotic also offers 1 resource — 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 24 September 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.