Diagrams · Fig. 08

Two jobs, two packages

Installing the directory client does not install the gate.

Two jobs, two packagesTwo different jobs. Job one is the gate, installed from PyPI as mcpindex-gate: it runs in your call path, it can hold a call, and it cannot tell you what to install. Job two is the directory client, installed from npm as mcp-server-mcpindex or connected remotely: it runs beside your agent as an MCP server, it can search, recommend and look up an advisory verdict, and it cannot stop a call. Installing job two does not install job one. The mcp-index SDK and Mastra binding let you embed either job in your own code.JOB 1 · THE GATEmcpindex-gatePYPI · UV / PIPRUNSin your call pathCANHOLD a callCANNOTtell you what to installJOB 2 · THE DIRECTORY CLIENTmcp-server-mcpindexNPM · OR REMOTERUNSbeside your agent, as an MCP serverCANsearch · recommend · look up a verdictCANNOTstop a callINSTALLING JOB 2 DOES NOT INSTALL JOB 1. DIFFERENT PACKAGE, DIFFERENT JOB.@mcp-index/sdk · @mcp-index/mastraembed either job in your own code
Fig. 08 · Installing the directory client does not install the gate.
Read Fig. 08 as text
        JOB 1 - THE GATE          |        JOB 2 - THE DIRECTORY CLIENT
  ------------------------------  |  ------------------------------------------
  uv / pip:  mcpindex-gate        |  npm:  mcp-server-mcpindex
                                  |        or remote: mcpindex.ai/api/mcp
  runs   in your call path        |  runs   beside your agent, as an MCP server
  can    HOLD a call              |  can    search - recommend - look up a verdict
  cannot tell you what to install |  cannot stop a call

  ! installing job 2 does not install job 1. different package, different job.
  ---------------------------------------------------------------------------
  @mcp-index/sdk - @mcp-index/mastra   embed either job in your own code
What the figure says

Two different jobs. Job one is the gate, installed from PyPI as mcpindex-gate: it runs in your call path, it can hold a call, and it cannot tell you what to install. Job two is the directory client, installed from npm as mcp-server-mcpindex or connected remotely: it runs beside your agent as an MCP server, it can search, recommend and look up an advisory verdict, and it cannot stop a call. Installing job two does not install job one. The mcp-index SDK and Mastra binding let you embed either job in your own code.

Where this is explained
/install/which-mcpindex
Use this diagram

Licensed CC BY 4.0. Use it anywhere, including commercially. Keep the credit.

Credit line (HTML)

Paste under the figure. That is the whole licence obligation.

<a href="https://mcpindex.ai/diagrams/two-jobs-two-packages">Two jobs, two packages - mcpindex.ai</a> (CC BY 4.0)
Direct SVG

Standalone image/svg+xml. Vector, editable, no stylesheet needed.

https://mcpindex.ai/diagrams/two-jobs-two-packages/svg

Last reviewed 2026-07-27 · derived live from PACKAGES · never hand-typed

Questions this answers

mcpindex gate vs directory &middot; mcpindex-gate vs mcp-server-mcpindex &middot; which mcpindex package