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