marketing-plan — Sharebench MCP Resource
marketing-plan
is one of 93 resources on the
Sharebench
MCP server. Connect the server and your client can attach it as context.
by client
How to attach marketing-plan from your client
- Claude Code Sharebench Resource/marketing-plan run in your project directory
- Claude Desktop Sharebench Resource/marketing-plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sharebench Resource/marketing-plan ~/.cursor/mcp.json
- VS Code Sharebench Resource/marketing-plan .vscode/mcp.json
- Zed Sharebench Resource/marketing-plan ~/.config/zed/settings.json
- Windsurf Sharebench Resource/marketing-plan ~/.codeium/windsurf/mcp_config.json
- Cline Sharebench Resource/marketing-plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sharebench Resource/marketing-plan ~/.gemini/settings.json
- Grok Sharebench Resource/marketing-plan .mcp.json (in your project root)
- ChatGPT Sharebench Resource/marketing-plan Settings → Connectors → Advanced → Developer mode
- Claude.ai Sharebench Resource/marketing-plan Settings → Connectors → Add custom connector
- LangChain Sharebench Resource/marketing-plan pip install langchain-mcp-adapters
Other resources on this server
- launch
- launch-strategy
- ai-seo
- marketing-ideas
- micro-saas-launcher
- go-to-market-planner
- schema
- security-compliance-compliance-check
- customer-support
- skill-creator
- emails
- gtm-strategy
- product-launch-checklist
- build-automation
- cold-email
- ticket-triage
- campaign-planner
- bash-pro
- documentation
- aeo-optimizer
- social-media-strategy
- onboarding
- draft-response
- onboarding-playbook
- content-marketer
- fsi-compliance-checker
- bats-testing-patterns
- seo-geo
- launch-readiness
- iso42001-specialist
- database-migration
- tensorflow-and-deep-learning-rules
- docx
- qbr-builder
- sop-builder
- seo-aeo-meta-description-generator
- saas-mvp-launcher
- email-campaign
- design-clinical-campaign
- ra-qm-skills
Read from the server itself, by connecting to it and calling resources/list on 24 September 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.