MintMCP Docs
Search and read the official MintMCP documentation, the enterprise MCP gateway.
使うべきか
品質と安全性
検出事項（1）
- LOWTool 'fetch' suggests web access but openWorldHint=falsefetch 内
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"docs": {
"url": "https://www.mintmcp.com/docs/mcp"
}
}
}リモートエンドポイント
https://www.mintmcp.com/docs/mcpstreamable-httpできること
ツール一覧
ツール（4）
🟢search(query)
Search the full MintMCP documentation and get back matching pages with their ids, titles, and URLs. Use this first for any MintMCP question: setup, capabilities, security, or a specific connector (Snowflake, Slack, GitHub) or feature (SCIM, SIEM export, prompt security, Coworker Agents). Then pass a result id to the fetch tool to read the page. Coverage spans architecture, enterprise controls, and per-connector setup guides.
入力スキーマ
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "What to look for, in natural language or keywords. Examples: \"connect Snowflake\", \"SCIM provisioning\", \"block risky agent commands\", \"set up SSO with Okta\", \"Coworker Agent Slack\"."
}
},
"required": [
"query"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}出力スキーマ
{
"type": "object",
"properties": {
"results": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"title": {
"type": "string"
},
"url": {
"type": "string"
}
},
"required": [
"id",
"title",
"url"
],
"additionalProperties": false
}
}
},
"required": [
"results"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢fetch(id)
Fetch the full markdown content of a MintMCP documentation page by its id. Use it after search (or list_docs) to read a page in full before answering, for example the Snowflake connector setup, the SCIM provisioning guide, or the tool governance reference. If you have a public docs URL or a slug instead of a search-result id, use get_page.
入力スキーマ
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "The document id returned by search or list_docs."
}
},
"required": [
"id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}出力スキーマ
{
"type": "object",
"properties": {
"id": {
"type": "string"
},
"title": {
"type": "string"
},
"text": {
"type": "string"
},
"url": {
"type": "string"
},
"metadata": {
"type": "object",
"additionalProperties": {}
}
},
"required": [
"id",
"title",
"text",
"url"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list_docs(category)
List the MintMCP documentation table of contents, grouped by category (Getting Started, Architecture, connectors, Enterprise, Agent Monitor, and more). Each entry has a page id you can pass to fetch. Use it to see what the docs cover or to browse a category before reading a page. Pass an optional category to list just that group.
入力スキーマ
{
"type": "object",
"properties": {
"category": {
"type": "string",
"description": "Optional category name to filter by, e.g. \"Enterprise\" or \"Agent Monitor\"."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}出力スキーマ
{
"type": "object",
"properties": {
"categories": {
"type": "array",
"items": {
"type": "object",
"properties": {
"category": {
"type": "string"
},
"docs": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"title": {
"type": "string"
}
},
"required": [
"id",
"title"
],
"additionalProperties": false
}
}
},
"required": [
"category",
"docs"
],
"additionalProperties": false
}
}
},
"required": [
"categories"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_page(url)
Fetch a MintMCP documentation page from a public docs URL or a slug, for example "https://www.mintmcp.com/docs/security/tool-governance" or just "security/tool-governance". Use it when a user pastes a docs link or names a page directly. It returns the same full markdown content as fetch.
入力スキーマ
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "A docs page URL or slug, e.g. \"https://www.mintmcp.com/docs/enterprise/sso\" or \"enterprise/sso\"."
}
},
"required": [
"url"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}出力スキーマ
{
"type": "object",
"properties": {
"id": {
"type": "string"
},
"title": {
"type": "string"
},
"text": {
"type": "string"
},
"url": {
"type": "string"
},
"metadata": {
"type": "object",
"additionalProperties": {}
}
},
"required": [
"id",
"title",
"text",
"url"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}コミュニティ
エビデンス