Tailor

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
97%
Naming quality
100%
Poisoning risk
100%
Permission match
90%
Protocol compliance
100%

Findings (1)

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

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~577Tokens (tool definitions)
~1.1 KBTypical response size
Minimal attention impact (0.45% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.tailor.tech/"
    }
  }
}

Remote endpoints

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

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools