ctx

Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
100%
Calidad de los nombres
93%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,115Tokens (definiciones de herramientas)
~1.6 KBTamaño de respuesta típico
Impacto moderado en la atención (0.87% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "ctx": {
      "url": "https://ctx.vanshul.com/mcp"
    }
  }
}

Puntos de conexión remotos

https://ctx.vanshul.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (6)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🔴pack_repo(repo, ref, include, exclude, max_tokens)

Fetch a GitHub repository and return it as one agent-ready context blob: text files concatenated with clear "==== path ====" headers, binaries/lockfiles/build dirs stripped, with a token estimate. Use include/exclude globs to focus, and max_tokens to fit a budget.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "repo": {
      "type": "string",
      "description": "A GitHub repo as \"owner/repo\" or a github.com URL."
    },
    "ref": {
      "type": "string",
      "description": "Optional branch, tag or commit SHA (defaults to the default branch)."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "max_tokens": {
      "type": "number",
      "description": "Stop adding files once the estimate exceeds this many tokens."
    }
  },
  "required": [
    "repo"
  ]
}
🟢search_context(repo, query, ref, include, exclude, ...)

Search a GitHub repository and return only the passages that match a query — each with its file path, line number and a relevance score. Far more token-efficient than pack_repo when you need a specific detail (e.g. "where is auth handled?").

Esquema de entrada

{
  "type": "object",
  "properties": {
    "repo": {
      "type": "string",
      "description": "A GitHub repo as \"owner/repo\" or a github.com URL."
    },
    "query": {
      "type": "string",
      "description": "Space-separated search terms; matching is case-insensitive."
    },
    "ref": {
      "type": "string",
      "description": "Optional branch, tag or commit SHA (defaults to the default branch)."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "max_matches": {
      "type": "number",
      "description": "Max passages to return (1–50, default 5)."
    },
    "context_chars": {
      "type": "number",
      "description": "Per-passage character budget (80–4000, default 500)."
    }
  },
  "required": [
    "repo",
    "query"
  ]
}
🟢list_files(repo, ref, include, exclude)

List the text files ctx would include for a repository (after stripping binaries, lockfiles and build dirs), with their byte sizes. Cheap way for an agent to see the layout before packing.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "repo": {
      "type": "string",
      "description": "A GitHub repo as \"owner/repo\" or a github.com URL."
    },
    "ref": {
      "type": "string",
      "description": "Optional branch, tag or commit SHA (defaults to the default branch)."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    }
  },
  "required": [
    "repo"
  ]
}
🟢get_file(repo, path, ref)

Return the full text of a single file in a repository, by path. Use after list_files or search_context to drill in.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "repo": {
      "type": "string",
      "description": "A GitHub repo as \"owner/repo\" or a github.com URL."
    },
    "path": {
      "type": "string",
      "description": "File path within the repo."
    },
    "ref": {
      "type": "string",
      "description": "Optional branch, tag or commit SHA (defaults to the default branch)."
    }
  },
  "required": [
    "repo",
    "path"
  ]
}
⚪pack_docs(url, depth, max_pages, max_tokens)

Crawl a documentation site from a start URL and return it as one agent-ready context blob: each page extracted to clean Markdown, concatenated with its URL. Stays within the same site section; bounded by depth and page count. Use max_tokens to fit a budget.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The absolute http(s) URL to start crawling from (e.g. a docs index)."
    },
    "depth": {
      "type": "number",
      "description": "How many link hops to follow (0–3, default 1)."
    },
    "max_pages": {
      "type": "number",
      "description": "Max pages to fetch (1–30, default 10)."
    },
    "max_tokens": {
      "type": "number",
      "description": "Stop adding pages once the estimate exceeds this many tokens."
    }
  },
  "required": [
    "url"
  ]
}
🟢search_docs(url, query, depth, max_pages, max_matches, ...)

Crawl a documentation site and return only the passages that match a query — each with its page URL, line and a relevance score. Token-efficient way to answer a question from docs without packing the whole site.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The absolute http(s) URL to start crawling from."
    },
    "query": {
      "type": "string",
      "description": "Space-separated search terms; matching is case-insensitive."
    },
    "depth": {
      "type": "number",
      "description": "How many link hops to follow (0–3, default 1)."
    },
    "max_pages": {
      "type": "number",
      "description": "Max pages to fetch (1–30, default 10)."
    },
    "max_matches": {
      "type": "number",
      "description": "Max passages to return (1–50, default 5)."
    },
    "context_chars": {
      "type": "number",
      "description": "Per-passage character budget (80–4000, default 500)."
    }
  },
  "required": [
    "url",
    "query"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas