Preparing components...
Skip to content

Interactive reference demo. Token figures below are recorded examples, not a new benchmark.

Rolling green hills and wildflowers under a cloudy sky

Stop loading every tool.

An MCP server for your agent. Each task gets only the tools it calls, in order. Nothing else in context.

An MCP server that picks your agent's tools.

It maps your MCP servers into a graph and hands back only the tools a task needs.

  1. 01

    Connect

    Add one MCP server to your agent.

  2. 02

    Ask

    Your agent describes the task.

  3. 03

    Get the plan

    Just the tools it calls, in order.

One task. Only the tools it calls.

in call order2 calls
  1. 1
    1githublist_branches
  2. 2
    2githubcreate_pull_request
tokens in context110,238
down from 110,238
vector top- 5 , same task
search_pull_requests
search_issues
search_orgs
read_graph
jira_assign_issue

Sounds right. Can't run: no branch for the PR.

Missing prerequisite
github/list_branches

Similarity is not callability.

Vector search finds tools that sound right. Switchboard finds the chain that runs.

Vector search1,488 tokens
githubsearch_pull_requests
githubsearch_issues
githubsearch_orgs
memoryread_graph
atlassianjira_assign_issue
Missing prerequisite
github/list_branches

No order. A prerequisite is missing.

Switchboard304 tokens
1githublist_branches
2githubcreate_pull_request

In call order. Every input is produced by an earlier step.

Why a graph →

All 420 tools, one graph.

Open the explorer
atlassiangithubsupabasefirecrawlplaywrightnotiongmailfilesystemgitgoogle-calendargitlabmemoryslackgoogle-mapspuppeteerlineartimebrave-searchfetchpostgres

Guard

Three safe tools. One unsafe chain.

See the guard →

Bench

Kill the database. Watch it come back.

See the numbers →

Search Switchboard

Search the docs, plan a task, or jump to a page