[Feature Request] Configurable MCP Tool Selection to Reduce Context Overhead

Resolved 💬 3 comments Opened Sep 24, 2025 by ryx2 Closed Jan 6, 2026

Bug Description
Can we add the option to not include some of the tools from MCP? Currently, I have 19.3k tokens getting wasted from extra mcp tools. I do want some of the tools from these MCP tools, just not all of them! I'd like to take a fraction so I can free up 15k tokens of context

MCP tools · /mcp
└ mcp__ide__getDiagnostics (ide): 428 tokens
└ mcp__ide__executeCode (ide): 499 tokens
└ mcp__logfire__find_exceptions_in_file (logfire): 488 tokens
└ mcp__logfire__arbitrary_query (logfire): 496 tokens
└ mcp__logfire__sql_reference (logfire): 405 tokens
└ mcp__logfire__get_logfire_records_schema (logfire): 394 tokens
└ mcp__logfire__logfire_link (logfire): 436 tokens
└ mcp__neon__list_projects (neon): 577 tokens
└ mcp__neon__create_project (neon): 478 tokens
└ mcp__neon__delete_project (neon): 448 tokens
└ mcp__neon__describe_project (neon): 449 tokens
└ mcp__neon__run_sql (neon): 645 tokens
└ mcp__neon__run_sql_transaction (neon): 668 tokens
└ mcp__neon__describe_table_schema (neon): 560 tokens
└ mcp__neon__get_database_tables (neon): 521 tokens
└ mcp__neon__create_branch (neon): 477 tokens
└ mcp__neon__prepare_database_migration (neon): 1.8k tokens
└ mcp__neon__complete_database_migration (neon): 479 tokens
└ mcp__neon__describe_branch (neon): 529 tokens
└ mcp__neon__delete_branch (neon): 481 tokens
└ mcp__neon__get_connection_string (neon): 621 tokens
└ mcp__neon__provision_neon_auth (neon): 2.2k tokens
└ mcp__neon__explain_sql_statement (neon): 603 tokens
└ mcp__neon__prepare_query_tuning (neon): 2.2k tokens
└ mcp__neon__complete_query_tuning (neon): 1.2k tokens
└ mcp__neon__list_slow_queries (neon): 711 tokens
└ mcp__neon__list_branch_computes (neon): 491 tokens

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 1.0.120
  • Feedback ID: fa596414-1135-457e-a31e-43169a3a6c88

Errors

[]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗