get_integration_status — Replo MCP Tool Read-only
get_integration_status
(get integration status) is one of 96 tools on the
Replo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_integration_status from your client
- Claude Code Replo get_integration_status run in your project directory
- Claude Desktop Replo get_integration_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Replo get_integration_status ~/.cursor/mcp.json
- VS Code Replo get_integration_status .vscode/mcp.json
- Zed Replo get_integration_status ~/.config/zed/settings.json
- Windsurf Replo get_integration_status ~/.codeium/windsurf/mcp_config.json
- Cline Replo get_integration_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Replo get_integration_status ~/.gemini/settings.json
- Grok Replo get_integration_status .mcp.json (in your project root)
- ChatGPT Replo get_integration_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Replo get_integration_status Settings → Connectors → Add custom connector
- LangChain Replo get_integration_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http replo https://api.replo.app/v1/mcpOther tools on this server
- get_agent_session
- resolve_agent_interaction
- abort_agent_session
- query_replo_analytics
- list_sites
- create_site
- update_site
- publish_site
- apply_brand_kit_to_site
- update_site_navigation
- update_site_metadata
- update_site_tracking
- list_tasks
- get_task
- delete_task
- get_branding
- update_brand
- create_artifact
- update_artifact
- generate_artifact
- show_artifact
- get_artifact_view_access
- get_artifact_report_context
- run_artifact_chart
- create_shared_preview
- revoke_shared_preview
- find_orders
- get_order
- find_assets
- upload_asset
- list_comment_threads
- get_comment_thread
- create_comment_thread
- resolve_comment_thread
- reply_to_comment_thread
- connect_custom_domain
- get_custom_domain_status
- verify_custom_domain
- report_bug
- submit_feature_request
- list_files
- get_file
- read_file
- create_file
- update_file
- get_file_sharing
- set_file_sharing
- create_api_key
- list_insights_reports
- get_insights_report
- query_insights_report
- find_products
- get_product
- create_product
- update_product
- set_product_inventory
- list_projects
- create_project
- get_project
- update_project
- create_site_page
- edit_site_page
- delete_site_page
- sightglass_find_ads
- sightglass_search_companies
- sightglass_get_company
- sightglass_get_company_activity
- sightglass_get_rankings
- sightglass_find_site_pages
- sightglass_get_site_page
- sightglass_get_ad
- sightglass_find_technologies
- sightglass_get_access
- sightglass_list_saved
- sightglass_create_board
- sightglass_update_board
- sightglass_delete_board
- sightglass_follow_companies
- sightglass_research_company
- sightglass_copy_creative_to_assets
- sightglass_find_campaigns
- sightglass_find_offers
- sightglass_find_angles
- sightglass_find_top_angles
- sightglass_find_personas
- sightglass_arena_compare
- sightglass_get_site_page_versions
- sightglass_xray
- sightglass_get_xray
- get_plan_options
- start_plan_upgrade
- sightglass_show
- connect_replo_account
- list_workspaces
- skills
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.