thinkneo_start_trace — ThinkNEO Control Plane MCP Tool
thinkneo_start_trace
(thinkneo start trace) is one of 68 tools on the
ThinkNEO Control Plane
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call thinkneo_start_trace from your client
- Claude Code ThinkNEO Control Plane thinkneo_start_trace run in your project directory
- Claude Desktop ThinkNEO Control Plane thinkneo_start_trace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ThinkNEO Control Plane thinkneo_start_trace ~/.cursor/mcp.json
- VS Code ThinkNEO Control Plane thinkneo_start_trace .vscode/mcp.json
- Zed ThinkNEO Control Plane thinkneo_start_trace ~/.config/zed/settings.json
- Windsurf ThinkNEO Control Plane thinkneo_start_trace ~/.codeium/windsurf/mcp_config.json
- Cline ThinkNEO Control Plane thinkneo_start_trace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ThinkNEO Control Plane thinkneo_start_trace ~/.gemini/settings.json
- Grok ThinkNEO Control Plane thinkneo_start_trace .mcp.json (in your project root)
- ChatGPT ThinkNEO Control Plane thinkneo_start_trace Settings → Connectors → Advanced → Developer mode
- Claude.ai ThinkNEO Control Plane thinkneo_start_trace Settings → Connectors → Add custom connector
- LangChain ThinkNEO Control Plane thinkneo_start_trace pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http control-plane https://mcp.thinkneo.ai/mcpOther tools on this server
- thinkneo_check_spend
- thinkneo_complete
- thinkneo_read_memory
- thinkneo_write_memory
- thinkneo_evaluate_guardrail
- thinkneo_check
- thinkneo_check_policy
- thinkneo_get_budget_status
- thinkneo_list_alerts
- thinkneo_get_compliance_status
- thinkneo_provider_status
- thinkneo_schedule_demo
- thinkneo_usage
- thinkneo_route_model
- thinkneo_get_savings_report
- thinkneo_simulate_savings
- thinkneo_evaluate_trust_score
- thinkneo_get_trust_badge
- thinkneo_registry_search
- thinkneo_registry_get
- thinkneo_registry_publish
- thinkneo_registry_review
- thinkneo_registry_install
- thinkneo_bridge_mcp_to_a2a
- thinkneo_bridge_a2a_to_mcp
- thinkneo_bridge_generate_agent_card
- thinkneo_bridge_list_mappings
- thinkneo_log_event
- thinkneo_end_trace
- thinkneo_get_trace
- thinkneo_get_observability_dashboard
- thinkneo_set_baseline
- thinkneo_log_decision
- thinkneo_log_risk_avoidance
- thinkneo_decision_cost
- thinkneo_agent_roi
- thinkneo_business_impact
- thinkneo_a2a_log
- thinkneo_a2a_policy
- thinkneo_a2a_flow
- thinkneo_a2a_audit
- thinkneo_detect_waste
- thinkneo_register_claim
- thinkneo_verify_claim
- thinkneo_get_proof
- thinkneo_verification_dashboard
- thinkneo_benchmark_report
- thinkneo_benchmark_compare
- thinkneo_router_explain
- thinkneo_compliance_generate
- thinkneo_sla_define
- thinkneo_sla_status
- thinkneo_sla_breaches
- thinkneo_sla_dashboard
- thinkneo_audit_export
- thinkneo_compare_models
- thinkneo_count_tokens
- thinkneo_optimize_prompt
- thinkneo_rotate_key
- thinkneo_manage_secrets
- thinkneo_cache_status
- thinkneo_detect_injection
- thinkneo_check_pii_international
- thinkneo_alert_rule_list
- thinkneo_alert_rule_create
- thinkneo_alert_rule_delete
- thinkneo_alert_rule_test
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.