Tailor Platform for AI assistants: search, list and read the platform documentation.
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
page identifier exactly as returned by search_knowledge or list_knowledge, for example docs:sdk/quickstart.md
return only this section of the page, matched case-insensitively against its level-two headings
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.
| Argument | Type | Description |
|---|---|---|
| id* | string | page identifier exactly as returned by search_knowledge or list_knowledge, for example docs:sdk/quickstart.md |
| section | string | return only this section of the page, matched case-insensitively against its level-two headings |
{
"type": "object",
"required": [
"id"
],
"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"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| source | string | restrict the listing to one knowledge source; omit to list every source |
| section | string | restrict the listing to one table-of-contents section, matched case-insensitively |
{
"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 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.
| Argument | Type | Description |
|---|---|---|
| limit | integer | maximum number of pages to return; defaults to 10, capped at 50 |
| query* | string | words to look for in the documentation body, matched case-insensitively as a substring |
| source | string | restrict the search to one knowledge source; omit to search every source |
{
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"description": "maximum number of pages to return; defaults to 10, capped at 50"
},
"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"
}
},
"additionalProperties": false
}