Skip to main content
Glama
deenesjakoruzh
nihar777

apollo-cache-copilot

by nihar777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apollo-cache-copilot

CI TypeScript Tested with Vitest License: ISC MCP

Copiloto de IA y servidor MCP para diagnosticar defectos de normalización de InMemoryCache de Apollo, diseñado para React Native, donde Apollo DevTools no existe.

El problema

Apollo Client normaliza cada resultado en un mapa plano de entidades __typename:id y almacena referencias cruzadas como punteros { "__ref": "Type:id" }. Esa normalización es invisible en el momento de la escritura y solo falla en el momento de la lectura, normalmente en una pantalla lejos de la mutación que la causó. Tres clases de fallos dominan, y los tres son silenciosos:

Defecto

Lo que hace Apollo

Síntoma

Puntero huérfano — { __ref: "User:99" } sin User:99 en el almacén

Devuelve undefined para el campo

Fila en blanco, sin excepción

Falta __typename / id

No puede calcular una clave de caché, almacena el objeto en línea

Se renderiza bien, luego diverge en la segunda escritura

Deriva de tipo/clave — keyFields no coincide con la carga del servidor

Misma entidad lógica bajo dos claves

Elementos de lista duplicados, lecturas obsoletas

React Native empeora cada uno de ellos:

  • Sin Apollo DevTools. La extensión del navegador es el depurador principal de caché y no existe en RN. El recurso es console.log(JSON.stringify(client.cache.extract())) y leer un blob de varios megabytes a simple vista.

  • Caché persistente. apollo3-cache-persist + AsyncStorage significa que una caché corrupta sobrevive al reinicio de la aplicación — persistente, y reproducible solo en el dispositivo del usuario.

  • Mutaciones offline-first. Las respuestas optimistas escriben entidades parciales por diseño, que es exactamente la forma que provoca los defectos 1 y 2.

  • Sesiones largas. Las aplicaciones móviles permanecen residentes durante días, por lo que la deriva se acumula mucho más que en una pestaña del navegador.

Related MCP server: mcp-rn-devtools

La solución

La detección es determinista. La explicación es trabajo del modelo.

  1. Un analizador de caché que recorre la salida de cache.extract() e informa defectos estructurales con rutas exactas (User:1.avatar → Avatar:99). Recorrido de grafo simple — sin modelo involucrado, sin adivinanzas, funciona en una instantánea de 10MB.

  2. Un servidor MCP que expone ese analizador al agente con el que el desarrollador ya está hablando. El agente solicita hallazgos más el subgrafo relevante, por lo que nunca tiene que mantener toda la caché en contexto.

El diagnóstico pasa de "pegar un blob de 10MB y entrecerrar los ojos" a una conversación.

Arquitectura

flowchart TD
    subgraph client["MCP client — Claude Desktop / Cursor"]
        A["Agent (the LLM)"]
    end

    subgraph server["apollo-cache-copilot (stdio process)"]
        T["StdioServerTransport<br/>apollo-copilot mcp"]
        R["Tool registry<br/>inspect_dangling_refs<br/>patch_cache<br/>diagnose_cache_graph"]
        Z["Zod schemas<br/>parse in, shape out"]

        subgraph g["cacheAgentGraph (LangGraph, LLM-free)"]
            I["inspectorNode<br/>writes findings"]
            RE["reasonerNode<br/>writes proposedPatches"]
            P["patcherNode<br/>writes narration"]
            I --> RE --> P
        end

        TOOL1["inspectDanglingRefs()<br/>pure, on a snapshot"]
        TOOL2["patchCache()<br/>modify / evict / gc"]

        T --> R --> Z --> I
        I -.->|calls| TOOL1
        P -.->|plans for| TOOL2
    end

    A <-->|"JSON-RPC 2.0 over stdio"| T
    TOOL1 --- CACHE["cache.extract() snapshot"]
    TOOL2 --- LIVE["live ApolloCache"]

ASCII, lo mismo:

  MCP client (Claude Desktop, Cursor, any stdio client)
        │  JSON-RPC 2.0  ▲
        ▼   over stdio   │  stdout IS the protocol channel —
  ┌─────────────────────────────────┐   all logs go to stderr
  │ StdioServerTransport            │
  ├─────────────────────────────────┤
  │ tools: inspect_dangling_refs    │  read-only
  │        patch_cache              │  mutating (dryRun available)
  │        diagnose_cache_graph     │  read-only, plans only
  ├─────────────────────────────────┤
  │ Zod schemas — parse at the edge │
  └───────────────┬─────────────────┘
                  ▼
  ┌─────────────────────────────────────────────────────┐
  │  cacheAgentGraph  (LangGraph, deliberately LLM-free)│
  │                                                     │
  │  INSPECTOR ──────► REASONER ──────► PATCHER         │
  │  walks the store   maps findings    narrates the     │
  │  → findings[]      → patch ops      plan             │
  │      │                  │                            │
  │      │ owns `findings`  │ owns `proposedPatches`      │
  └──────┼──────────────────┼────────────────────────────┘
         ▼                  ▼
  inspectDanglingRefs()   patchCache()
  pure, on a snapshot     cache.modify / evict / gc on a live cache

Cada nodo del grafo posee exactamente un canal de estado — el inspector escribe findings, el razonador escribe proposedPatches, el parcheador escribe messages. Solo messages se acumula; volver a ejecutar un nodo re-analiza la misma caché, por lo que añadir en otro lugar duplicaría cada hallazgo en la segunda pasada.

¿Por qué no hay LLM en el grafo? Cada defecto que detecta este copiloto tiene una reparación mecánica (podar el puntero, expulsar el huérfano). Un modelo añadiría latencia, costo y no determinismo a una decisión que un switch ya toma correctamente. El grafo se gana su lugar como orquestación; el modelo vive en el cliente MCP, donde correlaciona un hallazgo con la mutación o fragmento que lo escribió.

Instalación

npm install @indianic/apollo-cache-copilot
# or, from a checkout
npm install && npm run build

Requiere Node.js ≥ 20 (vitest 4 y @langchain/core lo requieren; CI cubre 20 y 22). @apollo/client (v3.8+ o v4), react y react-native son dependencias peer — el paquete usa las copias de tu aplicación.

Uso de la biblioteca

Solo ESM. El paquete incluye tipos.

inspectDanglingRefs — auditar una instantánea

Pura y síncrona. Toma la salida de cache.extract(), devuelve hallazgos y estadísticas.

import { inspectDanglingRefs } from 'apollo-cache-copilot';

const { findings, stats } = inspectDanglingRefs({
  cache: client.cache.extract(),
  // all optional:
  rootIds: ['ROOT_QUERY', 'ROOT_MUTATION'], // reachability roots
  includeUnreachable: true,                  // report gc candidates
  includeNormalizationGaps: true,            // report un-keyable inline objects
});

console.log(stats);
// { entityCount: 4, refCount: 3, danglingCount: 1, unreachableCount: 1 }

for (const f of findings) {
  console.log(f.kind, f.path, f.danglingRef ?? '');
  // ORPHANED_REF  User:1.avatar  Avatar:99
  // UNREACHABLE_ENTITY  Post:7
}

Tipos de hallazgo: ORPHANED_REF, UNREACHABLE_ENTITY, MISSING_TYPENAME, MISSING_ID. Cada hallazgo lleva una ruta de caché exacta.

patchCache — aplicar reparaciones a una caché en vivo

Las operaciones son descriptores declarativos para que sobrevivan un salto JSON; la herramienta los rehidrata en las funciones que cache.modify quiere. Ordenadas, y los fallos se registran en lugar de lanzarse, para que una clave incorrecta en medio del lote no pueda dejar la caché a medio parchear.

import { patchCache } from 'apollo-cache-copilot';

const { dryRun, results, collected } = patchCache(client.cache, {
  operations: [
    // drop dangling refs from a list field
    { type: 'modify', id: 'User:1', fields: { posts: { action: 'PRUNE_DANGLING_REFS' } } },
    // delete / invalidate / overwrite a field
    { type: 'modify', id: 'User:1', fields: { avatar: { action: 'DELETE' } } },
    { type: 'modify', id: 'User:1', fields: { bio: { action: 'SET', value: 'unset' } } },
    // evict an entity, or one field of it
    { type: 'evict', id: 'Post:7' },
    { type: 'evict', id: 'ROOT_QUERY', fieldName: 'user', args: { id: '1' } },
  ],
  gc: true,       // run cache.gc() once, after everything lands
  dryRun: false,  // true = validate only, cache untouched
});

results.forEach((r) => console.log(r.changed, r.error ?? ''));
console.log('collected:', collected); // keys gc() removed

Acciones de campo: DELETE, INVALIDATE, SET (con value), PRUNE_DANGLING_REFS.

cacheAgentGraph — inspeccionar → razonar → planificar

El LangGraph compilado. Devuelve hallazgos, las operaciones de parche que aplicaría y narración paso a paso. Nunca muta — alimenta proposedPatches a patchCache cuando los hayas revisado.

import { cacheAgentGraph } from 'apollo-cache-copilot';

const state = await cacheAgentGraph.invoke({ cacheState: client.cache.extract() });

state.messages.forEach((m) => console.log(String(m.content)));
// 2 findings: 1 orphaned ref, 1 unreachable entity.
// ...

// Review, then apply:
patchCache(client.cache, { operations: state.proposedPatches });

También se exportan: buildCacheAgentGraph() (constructor sin compilar), los nodos individuales inspectorNode / reasonerNode / patcherNode, CacheAgentAnnotation, cada esquema Zod (InspectDanglingRefsInputSchema, PatchCacheInputSchema, …) y su tipo inferido, además de la superficie MCP (createServer, startStdioServer, runInspectDanglingRefs, runPatchCache, runDiagnoseCacheGraph).

Uso de CLI

apollo-copilot [mcp]          Start the stdio MCP server (default when no args)
apollo-copilot inspect FILE   Diagnose a JSON cache snapshot and print findings

apollo-copilot inspect <archivo>

Vuelca la caché de tu aplicación y luego léela:

// in the RN app
console.log(JSON.stringify(client.cache.extract()));
npx -y -p @indianic/apollo-cache-copilot apollo-copilot inspect ./cache-snapshot.json
━━ Cache Diagnostic ━━

Entities: 4 | Refs: 3 | Dangling: 1 | Unreachable: 1

⚠  ORPHANED_REF (1)
   • User:1.avatar → Avatar:99
     Points at "Avatar:99", which is not in the cache. Reads here return undefined.

🗑  UNREACHABLE_ENTITY (1)
   • Post:7
     No root reaches this entity; cache.gc() would collect it.

Una caché limpia imprime ✓ Cache is clean: no findings.

Códigos de salida: 0 éxito, 1 fallo inesperado, 2 entrada incorrecta (archivo faltante, archivo ilegible, JSON inválido, comando desconocido).

apollo-copilot mcp

Inicia el servidor MCP en stdio y se bloquea. Solo es útil cuando un cliente MCP posee el proceso — ver más abajo. apollo-copilot-mcp es un alias heredado para lo mismo.

stdout es el canal de protocolo. El servidor no escribe nada más que JSON-RPC a stdout; todos los diagnósticos van a stderr. Nunca añadas un console.log a esta ruta.

Configuración de MCP

Herramientas expuestas

Herramienta

Entrada

Comportamiento

inspect_dangling_refs

cache, opcional rootIds / includeUnreachable / includeNormalizationGaps

Solo lectura. Devuelve findings + stats.

diagnose_cache_graph

cache

Solo lectura. Ejecuta el grafo completo. Devuelve findings, proposedPatches, narration. Solo planifica.

patch_cache

cache, operations, gc, dryRun

Restaura la instantánea en un InMemoryCache desechable, lo parchea, devuelve results + la cache re-extraída.

patch_cache lleva la instantánea porque un servidor stdio no tiene una caché en vivo para pasar al parcheador — solo JSON. Compara la cache devuelta con la tuya, o usa client.cache.restore().

Cada herramienta devuelve tanto un resumen legible por humanos como structuredContent legible por máquina, para que los clientes que no entienden la salida estructurada aún obtengan el JSON.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) o %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "apollo-cache-copilot": {
      "command": "npx",
      "args": ["-y", "-p", "@indianic/apollo-cache-copilot", "apollo-copilot", "mcp"]
    }
  }
}

Desde un checkout local — compila primero (npm run build), luego apunta al bin con una ruta absoluta:

{
  "mcpServers": {
    "apollo-cache-copilot": {
      "command": "node",
      "args": ["/absolute/path/to/apollo-cache-copilot/bin/apollo-copilot.js", "mcp"]
    }
  }
}

Reinicia Claude Desktop. Las tres herramientas aparecen en el menú de herramientas.

Cursor

.cursor/mcp.json en el proyecto (o ~/.cursor/mcp.json para todos los proyectos):

{
  "mcpServers": {
    "apollo-cache-copilot": {
      "command": "npx",
      "args": ["-y", "-p", "@indianic/apollo-cache-copilot", "apollo-copilot", "mcp"]
    }
  }
}

Checkout local:

{
  "mcpServers": {
    "apollo-cache-copilot": {
      "command": "node",
      "args": ["${workspaceFolder}/bin/apollo-copilot.js", "mcp"]
    }
  }
}

Luego Cursor → Configuración → MCP → confirma que el servidor está en verde.

Y luego solo pregunta

"Aquí está mi instantánea de caché — ¿por qué el avatar está en blanco en la pantalla de perfil?"

El agente llama a diagnose_cache_graph, obtiene User:1.avatar → Avatar:99 más el PRUNE_DANGLING_REFS propuesto, y lo correlaciona con la mutación que escribió una referencia sin el cuerpo de la entidad.

Desarrollo

npm install
npm run build      # tsc -> dist/  (run first: typecheck and tests import dist)
npm run typecheck  # tsc --noEmit -p tsconfig.test.json (includes tests)
npm test           # vitest run

tsconfig.json es la compilación y excluye __tests__ / __mocks__ para que el paquete publicado sea solo las herramientas. tsconfig.test.json verifica tipos de todo y no emite nada.

Métricas de éxito

#

Métrica

Objetivo

1

Recuerdo de detección en el conjunto de fixtures

100% — cada defecto sembrado encontrado

2

Falsos positivos en una instantánea saludable

0

3

Tiempo de ejecución del analizador en un extract() de 10MB

< 1s

4

Hallazgos con una ruta de caché exacta

100%

5

Tiempo del desarrollador desde el síntoma hasta la causa raíz nombrada

< 5 min (vs. horas)

6

Tokens enviados al modelo por diagnóstico

< 10k — hallazgos y subgrafo, nunca toda la caché

Licencia

ISC — ver LICENSE.

Available Tools

3 tools
diagnose_cache_graphDiagnose cache graphA
Read-only

Run the full inspect -> reason -> plan graph over a serialized cache. Returns findings, the proposed patch operations (feed them to patch_cache), and per-step narration. Plans only; never mutates.

ParametersJSON Schema
NameRequiredDescriptionDefault
cacheYesThe full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. "ROOT_QUERY", "User:1"); values are that entity's stored fields, which may contain `{ "__ref": "<cache id>" }` pointers to other entries in this same object.

Output Schema

ParametersJSON Schema
NameRequiredDescription
findingsYesEvery defect the inspector found in `cache`.
narrationYes
proposedPatchesYesMechanically-derived fixes for the fixable findings, ready to pass to patch_cache as-is.

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true, and the description reinforces this with 'Plans only; never mutates.' It adds useful behavioral context about what the tool does not do and how its output should be consumed, going beyond the structured annotation without contradicting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences deliver the pipeline, the return value, the downstream consumer, and the side-effect guarantee. Every phrase earns its place and the most important behavioral constraint is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with a fully documented schema and an output schema, the description is complete: it names the inputs, outputs, downstream action, and non-mutating behavior. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides 100% coverage, including a detailed description of the cache object and its structure. The tool description does not need to restate parameter details; the schema carries the semantic weight, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Run the full inspect -> reason -> plan graph over a serialized cache') and clearly differentiates itself from the sibling tools by describing its broader pipeline. It also states what it returns, making its role unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when this tool fits: it produces patch operations that should be fed to patch_cache, and it is a planning-only step. It does not explicitly state when to prefer it over inspect_dangling_refs, but the pipeline framing and output-to-patch_cache relationship make the usage context clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

inspect_dangling_refsInspect dangling refsA
Read-only

Audit a serialized Apollo InMemoryCache (cache.extract() output) for dangling __refs, unreachable entities, and objects Apollo could not normalize. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
cacheYesThe full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. "ROOT_QUERY", "User:1"); values are that entity's stored fields, which may contain `{ "__ref": "<cache id>" }` pointers to other entries in this same object.
rootIdsNoCache IDs to treat as reachability roots for the UNREACHABLE_ENTITY check, e.g. ["ROOT_QUERY"]. Omit to use every one of ROOT_QUERY / ROOT_MUTATION / ROOT_SUBSCRIPTION that is present in `cache`. Has no effect on ORPHANED_REF or normalization-gap findings.
includeUnreachableNoInclude UNREACHABLE_ENTITY findings for entities no root can reach (candidates `cache.gc()` would collect). Set false to skip reachability analysis and only check refs/normalization.
includeNormalizationGapsNoInclude MISSING_TYPENAME / MISSING_ID findings for inline (non-entity) objects that Apollo could not normalize because they lack a `__typename` or an `id`/`_id` field.

Output Schema

ParametersJSON Schema
NameRequiredDescription
statsYesAggregate counts over the whole cache, independent of the findings list.
findingsYesEvery defect found, in walk order.

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint, and the description repeats 'Read-only.' It adds the scope of audit findings but no additional behavioral context such as error behavior, performance implications, or what the tool does not inspect. With the safety profile already covered by annotations, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences totaling 19 words. It front-loads the verb, resource, and primary finding types, and 'Read-only' is a harmless, minimal redundancy with the annotation. Every word contributes to understanding what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 4 parameters, 2 siblings, and subtle optional-parameter interactions, but the input schema is exceptionally detailed and an output schema exists, so the short description is sufficient for invocation. The main completeness gap is the lack of an explicit decision rule versus diagnose_cache_graph, preventing a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with detailed parameter documentation for cache, rootIds, includeUnreachable, and includeNormalizationGaps, including defaults and effects on findings. The description itself adds no parameter-level detail beyond the cache.extract() context, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with the specific verb 'Audit' and names the exact resource: a serialized Apollo InMemoryCache from cache.extract(). It then enumerates the three distinct finding categories (dangling __refs, unreachable entities, normalization gaps), which makes the tool's scope precise and differentiates it from the write-oriented patch_cache and the broader-sounding diagnose_cache_graph.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: use this when you have cache.extract() output and need to audit for ref/reachability/normalization issues. However, there is no explicit when-to-use versus alternatives, no exclusions, and no routing to sibling tools such as diagnose_cache_graph. The context is clear but the guidance is not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

patch_cachePatch cacheA
Idempotent

Apply declarative repairs (modify / evict, optional gc) to a serialized cache and return the patched store. Set dryRun to validate the operations without changing anything.

ParametersJSON Schema
NameRequiredDescriptionDefault
gcNoRun `cache.gc()` once after all operations land, to collect anything the patches orphaned.
cacheYesThe full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. "ROOT_QUERY", "User:1"); values are that entity's stored fields, which may contain `{ "__ref": "<cache id>" }` pointers to other entries in this same object.
dryRunNoValidate `operations` and report what would happen without mutating the cache.
operationsYesOne or more modify/evict operations to apply, in order.

Output Schema

ParametersJSON Schema
NameRequiredDescription
cacheYesThe store after the operations landed. Unchanged when `dryRun` is true.
dryRunYesEchoes the request's dryRun — true means the cache was not actually touched.
resultsYesOne result per input operation, in the same order.
collectedYesCache keys removed by the trailing `gc()`, when it ran.

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=false and idempotentHint=true, and the description adds meaningful behavioral context beyond those flags: it explicitly states that dryRun validates without mutating the cache, that the modified store is returned, and that gc is optional. This goes beyond what the annotations alone convey, while not contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler. The core action is front-loaded, and the dryRun safety note earns its place as a critical usage caveat. It is appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the very rich input and output schemas, the description only needs to establish the operation intent, the mutating nature, and the dryRun flow, which it does. The main missing element is explicit guidance on when to choose this tool over the siblings, but the schema and annotations cover most invocation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already thoroughly documents each parameter and nested operation shape. The description mentions modify/evict and dryRun, but it does not add parameter-level meaning beyond what the schema provides. The baseline of 3 applies because the schema carries the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool applies declarative repairs (modify/evict, optional gc) to a serialized cache and returns the patched store. The specific verb 'apply' plus the resource 'serialized cache' and operation types distinguish it from the sibling tools inspect_dangling_refs and diagnose_cache_graph, which are non-mutating inspection tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for mutating a serialized cache and mentions dryRun for validation, but it gives no explicit guidance on when to use patch_cache versus the sibling tools. No exclusion criteria or alternative routing is provided, so an agent must infer the appropriate context from the tool name and sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.2
    • Changeddiagnose_cache_graph8 fields changed
      • addedInput schema / properties / cache / additionalProperties / description
        Added value: +"One normalized store entry: the raw field/value map Apollo keeps under a single cache key."
      • addedInput schema / properties / cache / description
        Added value: +"The full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. \"ROOT_QUERY\", \"User:1\"); values are that entity's stored fields, which may contain `{ \"__ref\": \"<cache id>\" }` pointers to other entries in this same object."
      • addedOutput schema / properties / findings / description
        Added value: +"Every defect the inspector found in `cache`."
      • addedOutput schema / properties / findings / items / properties / danglingRef / description
        Added value: +"The unresolved cache key the ref pointed at. Only present when kind is ORPHANED_REF."
      • addedOutput schema / properties / findings / items / properties / message / description
        Added value: +"Human-readable explanation of this finding."
      • addedOutput schema / properties / findings / items / properties / path / description
        Added value: +"Dotted path to the defect from its cache key, e.g. \"User:2.posts.1\"."
      • addedOutput schema / properties / proposedPatches / description
        Added value: +"Mechanically-derived fixes for the fixable findings, ready to pass to patch_cache as-is."
      • changedOutput schema / properties / proposedPatches / items / oneOf
        Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fields": {
-        "additionalProperties": {
-          "oneOf": [
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "DELETE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "INVALIDATE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "SET",
-                  "type": "string"
-                },
-                "value": {}
-              },
-              "required": [
-                "action",
-                "value"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "PRUNE_DANGLING_REFS",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            }
-          ]
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "id": {
-        "default": "ROOT_QUERY",
-        "type": "string"
-      },
-      "optimistic": {
-        "default": false,
-        "type": "boolean"
-      },
-      "type": {
-        "const": "modify",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id",
-      "fields",
-      "optimistic",
-      "broadcast"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "args": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fieldName": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "type": {
-        "const": "evict",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id",
-      "broadcast"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this change. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fields": {
+        "additionalProperties": {
+          "oneOf": [
+            {
+              "additionalProperties": false,
+              "description": "Remove this field from the entity entirely.",
+              "properties": {
+                "action": {
+                  "const": "DELETE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Mark this field stale so Apollo refetches it, without removing or changing its value.",
+              "properties": {
+                "action": {
+                  "const": "INVALIDATE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Overwrite this field with `value` (any JSON — a scalar, object, or `{ \"__ref\": \"<cache id>\" }`).",
+              "properties": {
+                "action": {
+                  "const": "SET",
+                  "type": "string"
+                },
+                "value": {}
+              },
+              "required": [
+                "action",
+                "value"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Drop any `__ref` pointer(s) this field holds that no longer resolve to an entity in the cache. Works on a single ref or a list of refs; refs that still resolve are left untouched.",
+              "properties": {
+                "action": {
+                  "const": "PRUNE_DANGLING_REFS",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        "description": "Map of field name -> FieldPatch describing how to change that one field.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "id": {
+        "default": "ROOT_QUERY",
+        "description": "Cache key of the entity to modify, e.g. \"User:2\". Defaults to \"ROOT_QUERY\" if omitted.",
+        "type": "string"
+      },
+      "optimistic": {
+        "default": false,
+        "description": "Apply against the optimistic layer instead of the base cache. Mirrors `cache.modify`'s option.",
+        "type": "boolean"
+      },
+      "type": {
+        "const": "modify",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id",
+      "fields",
+      "optimistic",
+      "broadcast"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "args": {
+        "additionalProperties": {},
+        "description": "Field arguments to match when evicting a specific parameterized field (used with `fieldName`).",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this eviction. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fieldName": {
+        "description": "Evict only this one field instead of the whole entity at `id`.",
+        "type": "string"
+      },
+      "id": {
+        "description": "Cache key of the entity to evict, e.g. \"Post:5\".",
+        "type": "string"
+      },
+      "type": {
+        "const": "evict",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id",
+      "broadcast"
+    ],
+    "type": "object"
+  }
+]
    • Changedinspect_dangling_refs14 fields changed
      • addedInput schema / properties / cache / additionalProperties / description
        Added value: +"One normalized store entry: the raw field/value map Apollo keeps under a single cache key."
      • addedInput schema / properties / cache / description
        Added value: +"The full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. \"ROOT_QUERY\", \"User:1\"); values are that entity's stored fields, which may contain `{ \"__ref\": \"<cache id>\" }` pointers to other entries in this same object."
      • addedInput schema / properties / includeNormalizationGaps / description
        Added value: +"Include MISSING_TYPENAME / MISSING_ID findings for inline (non-entity) objects that Apollo could not normalize because they lack a `__typename` or an `id`/`_id` field."
      • addedInput schema / properties / includeUnreachable / description
        Added value: +"Include UNREACHABLE_ENTITY findings for entities no root can reach (candidates `cache.gc()` would collect). Set false to skip reachability analysis and only check refs/normalization."
      • addedInput schema / properties / rootIds / description
        Added value: +"Cache IDs to treat as reachability roots for the UNREACHABLE_ENTITY check, e.g. [\"ROOT_QUERY\"]. Omit to use every one of ROOT_QUERY / ROOT_MUTATION / ROOT_SUBSCRIPTION that is present in `cache`. Has no effect on ORPHANED_REF or normalization-gap findings."
      • addedOutput schema / properties / findings / description
        Added value: +"Every defect found, in walk order."
      • addedOutput schema / properties / findings / items / properties / danglingRef / description
        Added value: +"The unresolved cache key the ref pointed at. Only present when kind is ORPHANED_REF."
      • addedOutput schema / properties / findings / items / properties / message / description
        Added value: +"Human-readable explanation of this finding."
      • addedOutput schema / properties / findings / items / properties / path / description
        Added value: +"Dotted path to the defect from its cache key, e.g. \"User:2.posts.1\"."
      • addedOutput schema / properties / stats / description
        Added value: +"Aggregate counts over the whole cache, independent of the findings list."
      • addedOutput schema / properties / stats / properties / danglingCount / description
        Added value: +"Of those refs, how many did not resolve."
      • addedOutput schema / properties / stats / properties / entityCount / description
        Added value: +"Total cache keys in the input."
      • addedOutput schema / properties / stats / properties / refCount / description
        Added value: +"Total `__ref` pointers encountered."
      • addedOutput schema / properties / stats / properties / unreachableCount / description
        Added value: +"Entities no root reaches."
    • Changedpatch_cache15 fields changed
      • addedInput schema / properties / cache / additionalProperties / description
        Added value: +"One normalized store entry: the raw field/value map Apollo keeps under a single cache key."
      • addedInput schema / properties / cache / description
        Added value: +"The full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. \"ROOT_QUERY\", \"User:1\"); values are that entity's stored fields, which may contain `{ \"__ref\": \"<cache id>\" }` pointers to other entries in this same object."
      • addedInput schema / properties / dryRun / description
        Added value: +"Validate `operations` and report what would happen without mutating the cache."
      • addedInput schema / properties / gc / description
        Added value: +"Run `cache.gc()` once after all operations land, to collect anything the patches orphaned."
      • addedInput schema / properties / operations / description
        Added value: +"One or more modify/evict operations to apply, in order."
      • changedInput schema / properties / operations / items / oneOf
        Previous value: -[
-  {
-    "properties": {
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fields": {
-        "additionalProperties": {
-          "oneOf": [
-            {
-              "properties": {
-                "action": {
-                  "const": "DELETE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "properties": {
-                "action": {
-                  "const": "INVALIDATE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "properties": {
-                "action": {
-                  "const": "SET",
-                  "type": "string"
-                },
-                "value": {}
-              },
-              "required": [
-                "action",
-                "value"
-              ],
-              "type": "object"
-            },
-            {
-              "properties": {
-                "action": {
-                  "const": "PRUNE_DANGLING_REFS",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            }
-          ]
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "id": {
-        "default": "ROOT_QUERY",
-        "type": "string"
-      },
-      "optimistic": {
-        "default": false,
-        "type": "boolean"
-      },
-      "type": {
-        "const": "modify",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "fields"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "args": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fieldName": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "type": {
-        "const": "evict",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this change. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fields": {
+        "additionalProperties": {
+          "oneOf": [
+            {
+              "description": "Remove this field from the entity entirely.",
+              "properties": {
+                "action": {
+                  "const": "DELETE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "description": "Mark this field stale so Apollo refetches it, without removing or changing its value.",
+              "properties": {
+                "action": {
+                  "const": "INVALIDATE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "description": "Overwrite this field with `value` (any JSON — a scalar, object, or `{ \"__ref\": \"<cache id>\" }`).",
+              "properties": {
+                "action": {
+                  "const": "SET",
+                  "type": "string"
+                },
+                "value": {}
+              },
+              "required": [
+                "action",
+                "value"
+              ],
+              "type": "object"
+            },
+            {
+              "description": "Drop any `__ref` pointer(s) this field holds that no longer resolve to an entity in the cache. Works on a single ref or a list of refs; refs that still resolve are left untouched.",
+              "properties": {
+                "action": {
+                  "const": "PRUNE_DANGLING_REFS",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        "description": "Map of field name -> FieldPatch describing how to change that one field.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "id": {
+        "default": "ROOT_QUERY",
+        "description": "Cache key of the entity to modify, e.g. \"User:2\". Defaults to \"ROOT_QUERY\" if omitted.",
+        "type": "string"
+      },
+      "optimistic": {
+        "default": false,
+        "description": "Apply against the optimistic layer instead of the base cache. Mirrors `cache.modify`'s option.",
+        "type": "boolean"
+      },
+      "type": {
+        "const": "modify",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "fields"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "args": {
+        "additionalProperties": {},
+        "description": "Field arguments to match when evicting a specific parameterized field (used with `fieldName`).",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this eviction. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fieldName": {
+        "description": "Evict only this one field instead of the whole entity at `id`.",
+        "type": "string"
+      },
+      "id": {
+        "description": "Cache key of the entity to evict, e.g. \"Post:5\".",
+        "type": "string"
+      },
+      "type": {
+        "const": "evict",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id"
+    ],
+    "type": "object"
+  }
+]
      • addedOutput schema / properties / cache / additionalProperties / description
        Added value: +"One normalized store entry: the raw field/value map Apollo keeps under a single cache key."
      • addedOutput schema / properties / cache / description
        Added value: +"The store after the operations landed. Unchanged when `dryRun` is true."
      • addedOutput schema / properties / collected / description
        Added value: +"Cache keys removed by the trailing `gc()`, when it ran."
      • addedOutput schema / properties / dryRun / description
        Added value: +"Echoes the request's dryRun — true means the cache was not actually touched."
      • addedOutput schema / properties / results / description
        Added value: +"One result per input operation, in the same order."
      • addedOutput schema / properties / results / items / properties / changed / description
        Added value: +"Whether `cache.modify` / `cache.evict` actually changed anything."
      • addedOutput schema / properties / results / items / properties / error / description
        Added value: +"Set when this one operation failed; the rest of the batch still ran."
      • addedOutput schema / properties / results / items / properties / operation / description
        Added value: +"The operation this result is reporting on, echoed back."
      • changedOutput schema / properties / results / items / properties / operation / oneOf
        Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fields": {
-        "additionalProperties": {
-          "oneOf": [
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "DELETE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "INVALIDATE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "SET",
-                  "type": "string"
-                },
-                "value": {}
-              },
-              "required": [
-                "action",
-                "value"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "PRUNE_DANGLING_REFS",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            }
-          ]
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "id": {
-        "default": "ROOT_QUERY",
-        "type": "string"
-      },
-      "optimistic": {
-        "default": false,
-        "type": "boolean"
-      },
-      "type": {
-        "const": "modify",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id",
-      "fields",
-      "optimistic",
-      "broadcast"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "args": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fieldName": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "type": {
-        "const": "evict",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id",
-      "broadcast"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this change. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fields": {
+        "additionalProperties": {
+          "oneOf": [
+            {
+              "additionalProperties": false,
+              "description": "Remove this field from the entity entirely.",
+              "properties": {
+                "action": {
+                  "const": "DELETE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Mark this field stale so Apollo refetches it, without removing or changing its value.",
+              "properties": {
+                "action": {
+                  "const": "INVALIDATE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Overwrite this field with `value` (any JSON — a scalar, object, or `{ \"__ref\": \"<cache id>\" }`).",
+              "properties": {
+                "action": {
+                  "const": "SET",
+                  "type": "string"
+                },
+                "value": {}
+              },
+              "required": [
+                "action",
+                "value"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Drop any `__ref` pointer(s) this field holds that no longer resolve to an entity in the cache. Works on a single ref or a list of refs; refs that still resolve are left untouched.",
+              "properties": {
+                "action": {
+                  "const": "PRUNE_DANGLING_REFS",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        "description": "Map of field name -> FieldPatch describing how to change that one field.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "id": {
+        "default": "ROOT_QUERY",
+        "description": "Cache key of the entity to modify, e.g. \"User:2\". Defaults to \"ROOT_QUERY\" if omitted.",
+        "type": "string"
+      },
+      "optimistic": {
+        "default": false,
+        "description": "Apply against the optimistic layer instead of the base cache. Mirrors `cache.modify`'s option.",
+        "type": "boolean"
+      },
+      "type": {
+        "const": "modify",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id",
+      "fields",
+      "optimistic",
+      "broadcast"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "args": {
+        "additionalProperties": {},
+        "description": "Field arguments to match when evicting a specific parameterized field (used with `fieldName`).",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this eviction. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fieldName": {
+        "description": "Evict only this one field instead of the whole entity at `id`.",
+        "type": "string"
+      },
+      "id": {
+        "description": "Cache key of the entity to evict, e.g. \"Post:5\".",
+        "type": "string"
+      },
+      "type": {
+        "const": "evict",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id",
+      "broadcast"
+    ],
+    "type": "object"
+  }
+]
  2. 3 tool updatesv1.0.0
    • First observeddiagnose_cache_graph
    • First observedinspect_dangling_refs
    • First observedpatch_cache
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation4/5

The three tools map to distinct workflow phases: focused read-only audit, planning/diagnosis, and mutation. inspect_dangling_refs and diagnose_cache_graph overlap in that both return findings, but the descriptions clearly differentiate the focused audit from the full inspect-reason-plan pipeline.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: inspect_dangling_refs, patch_cache, diagnose_cache_graph. The verbs and noun objects are clear and predictable.

Tool Count5/5

Three tools is a well-scoped size for a focused Apollo cache repair copilot. Each tool covers a meaningful stage of the workflow—diagnose, plan, patch—without redundancy or bloat.

Completeness5/5

The surface covers the full repair lifecycle: audit problems, generate a plan, and apply/validate repairs with dry-run and optional GC. There are no obvious dead ends for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers