Tailor

Tailor Platform for AI assistants: search, list and read the platform documentation.

¿Debería usar esto?

Calidad y seguridad

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

Hallazgos (1)

  • LOWTool 'fetch_knowledge' suggests web access but openWorldHint=falseen fetch_knowledge

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

Costo de contexto

~577Tokens (definiciones de herramientas)
~1.1 KBTamaño de respuesta típico
Impacto mínimo en la atención (0.45% 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": {
    "mcp": {
      "url": "https://mcp.tailor.tech/"
    }
  }
}

Puntos de conexión remotos

https://mcp.tailor.tech/streamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (3)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢fetch_knowledge(id, section)

Return the Markdown source of one documentation page, addressed by an id from search_knowledge or list_knowledge. The first line is the page's URL, for citation. Long pages come back as a heading outline instead; pass section to read one part of them.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "page identifier exactly as returned by search_knowledge or list_knowledge, for example docs:sdk/quickstart.md"
    },
    "section": {
      "type": "string",
      "description": "return only this section of the page, matched case-insensitively against its level-two headings"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}
🟢list_knowledge(source, section)

List the documentation table of contents: the id, title, source, section and summary of every page. Use this to see what exists when a search does not find the right words; prefer search_knowledge when you know what you are looking for. Narrow the listing with source or section, since the full listing is large and is cut at 500 entries.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "restrict the listing to one knowledge source; omit to list every source"
    },
    "section": {
      "type": "string",
      "description": "restrict the listing to one table-of-contents section, matched case-insensitively"
    }
  },
  "additionalProperties": false
}
🟢search_knowledge(query, source, limit)

Search the body text of Tailor Platform's public documentation and return matching pages with an excerpt. Start here for most questions, then pass an id to fetch_knowledge to read a page in full. Matching is literal and case-insensitive, so prefer the exact terms that would appear in the docs. This covers published documentation only; it cannot see a user's own application data.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "words to look for in the documentation body, matched case-insensitively as a substring"
    },
    "source": {
      "type": "string",
      "description": "restrict the search to one knowledge source; omit to search every source"
    },
    "limit": {
      "type": "integer",
      "description": "maximum number of pages to return; defaults to 10, capped at 50"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada3 herramientas