get_weekly_signal_memo — AIOProductOS MCP MCP Tool Read-only
get_weekly_signal_memo
(get weekly signal memo) is one of 71 tools on the
AIOProductOS MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_weekly_signal_memo from your client
- Claude Code AIOProductOS MCP get_weekly_signal_memo run in your project directory
- Claude Desktop AIOProductOS MCP get_weekly_signal_memo ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AIOProductOS MCP get_weekly_signal_memo ~/.cursor/mcp.json
- VS Code AIOProductOS MCP get_weekly_signal_memo .vscode/mcp.json
- Zed AIOProductOS MCP get_weekly_signal_memo ~/.config/zed/settings.json
- Windsurf AIOProductOS MCP get_weekly_signal_memo ~/.codeium/windsurf/mcp_config.json
- Cline AIOProductOS MCP get_weekly_signal_memo ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AIOProductOS MCP get_weekly_signal_memo ~/.gemini/settings.json
- Grok AIOProductOS MCP get_weekly_signal_memo .mcp.json (in your project root)
- ChatGPT AIOProductOS MCP get_weekly_signal_memo Settings → Connectors → Advanced → Developer mode
- Claude.ai AIOProductOS MCP get_weekly_signal_memo Settings → Connectors → Add custom connector
- LangChain AIOProductOS MCP get_weekly_signal_memo pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://platform.aioproductos.com/api/mcpOther tools on this server
- get_pm_playbook
- whoami
- pm_meta
- get_product_brain
- get_roadmap_drift
- get_customer_360
- analyze_nps
- analyze_nrr
- analyze_funnel
- get_retention
- analyze_paths
- list_tasks
- get_task
- create_task
- create_feature
- create_objective
- create_sprint
- create_page
- update_feature
- update_objective
- update_key_result
- update_sprint
- update_page
- list_initiatives
- create_initiative
- update_initiative
- list_ideas
- create_idea
- update_idea
- vote_idea
- promote_idea
- create_release
- update_release
- create_experiment
- update_experiment
- list_decisions
- create_decision
- update_decision
- delete_task
- post_to_channel
- reply_in_channel
- reply_to_conversation
- add_note
- resolve_conversation
- cancel_booking
- reschedule_booking
- review_artifact
- list_artifact_versions
- revert_to_version
- update_task
- comment_on_task
- capture_insight
- list_conversations
- get_conversation
- list_insights
- list_features
- list_objectives
- list_experiments
- list_releases
- list_pages
- get_page
- get_codebase_map
- list_sprints
- list_channels
- read_channel
- list_bookings
- get_device_candidates
- list_identity_merges
- merge_end_users
- unmerge_end_users
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.