Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mcp-assistant.in/llms.txt

Use this file to discover all available pages before exploring further.

​
New features

​
mcp_list_servers meta-tool

A new diagnostic meta-tool lets the LLM inspect which MCP servers are currently connected and how many tools each exposes. Use it when mcp_search_tools returns no matches — the model can list active servers, then retry the search scoped to a specific serverId or serverName. The Tool Router now ships 5 meta-tools by default.

​
Server-scoped search and deterministic listing

The primary search meta-tool has been renamed from mcp_search_tool_bm25 to mcp_search_tools and gained two major capabilities:
  • Server scoping — pass serverId (exact) or serverName (case-insensitive fragment) to restrict results to a single connected MCP server. Useful for resolving cross-server tool name conflicts.
  • Deterministic listing — pass operation: "list" to enumerate every tool from a server with pagination metadata (totalCount, returnedCount, nextCursor). Ideal for “show me all tools from Notion” requests.
The same scoping fields work with select:<name> lookups, so the LLM can disambiguate when multiple servers expose tools with similar names.

​
Published ToolRouter benchmarks

We’ve published reproducible benchmarks measuring ToolRouter’s context efficiency on real MCP deployments. Highlights from a live run with 128 tools across 6 servers (Supabase, Exa, Notion, DeepWiki, Neon, Zapier):
  • 98.76% token reduction at idle vs. loading every tool schema upfront
  • 96.80% reduction even after discovering and loading 3 full tool schemas
  • ~0.11 ms average search latency

​
Updates

​
mcp_get_tool_schema and mcp_execute_tool now accept serverId

Both meta-tools now take serverId (exact match) instead of serverName for routing, making schema lookups and executions unambiguous when multiple servers expose tools with the same name. Search results return both serverId and serverName so the model can pass the right value through.

​
Bug fixes

  • Exact tool namespace matching — Fixed a regression where fully-qualified tool names (e.g. serverId:toolName) could match the wrong tool when another server’s name was a substring. Lookups now resolve to the correct server.
  • Server name fragment selection — Fixed an issue where serverName fragments could miss valid servers due to inconsistent normalization. Fragment matching is now case-insensitive and consistent across search, listing, and select: lookups.