get_proposal — canton ccpedia MCP Tool Read-only
get_proposal
(get proposal) is one of 104 tools on the
canton ccpedia
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_proposal from your client
- Claude Code canton ccpedia get_proposal run in your project directory
- Claude Desktop canton ccpedia get_proposal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor canton ccpedia get_proposal ~/.cursor/mcp.json
- VS Code canton ccpedia get_proposal .vscode/mcp.json
- Zed canton ccpedia get_proposal ~/.config/zed/settings.json
- Windsurf canton ccpedia get_proposal ~/.codeium/windsurf/mcp_config.json
- Cline canton ccpedia get_proposal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI canton ccpedia get_proposal ~/.gemini/settings.json
- Grok canton ccpedia get_proposal .mcp.json (in your project root)
- ChatGPT canton ccpedia get_proposal Settings → Connectors → Advanced → Developer mode
- Claude.ai canton ccpedia get_proposal Settings → Connectors → Add custom connector
- LangChain canton ccpedia get_proposal pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http canton-ccpedia https://ccpedia.xyz/mcpOther tools on this server
- search
- get_cip
- list_cips
- get_discussion
- get_whitepaper
- list_whitepapers
- get_trending
- get_radar
- get_proposals
- get_doc
- get_cip_history
- get_cip_attachments
- get_cip_mentions
- get_recent_changes
- get_network_stats
- get_token_market
- get_asset_supply
- get_defi_pools
- list_ecosystem_projects
- get_network_state
- list_repos
- list_github_discussions
- get_github_discussion
- get_video
- list_videos
- get_validator_fleet
- get_validator
- get_upcoming_deadlines
- list_governance_votes
- get_governance_vote
- list_votes_by_sv
- get_cip_vote_outcome
- get_cip_votes
- list_mailing_threads
- get_mailing_thread
- get_foundation_info
- semantic_search
- check_deprecation
- get_started_guide
- get_faq
- get_api_reference
- compare_to_evm
- migrate_lookup
- list_deprecations
- get_current_versions
- get_cip_citations
- get_kb_drift
- diagnose_error
- get_breaking_changes
- get_recurring_issue_fingerprint
- list_featured_apps
- get_app_metrics
- find_apps_by_pattern
- get_upgrade_status
- get_sv_schedule
- get_upcoming_operations
- get_recent_deployments
- detect_cip_dependency_chain
- compare_governance_outcomes
- get_sdk_changelog
- search_community
- search_github_issues
- list_blog_posts
- get_blog_post
- search_talks
- find_known_issues
- find_cip_for_feature
- get_cip_implementation_status
- get_latest_release
- search_release_notes
- find_security_patches
- get_npm_packages
- find_similar_projects
- search_mailing_list
- find_maintainer_guidance
- get_issue_status
- find_code_examples
- get_funding_landscape
- get_proposal_milestones
- get_ecosystem_gaps
- detect_builder_overlap
- proposal_success_predictor
- list_rfps
- find_rfp_for_idea
- list_proposals_needing_champion
- get_proposal_discussion
- get_proposal_file
- search_dev_fund
- get_dev_fund_activity
- get_dev_fund_lifecycle
- list_stuck_proposals
- find_duplicate_proposals
- get_dev_fund_person
- full_context
- community_consensus
- find_expert
- detect_drift
- learning_path
- outdated_guidance_detector
- ecosystem_dependency_graph
- find_collaboration_opportunities
- list_canton_mcps
- call_canton_mcp
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.