MintMCP Docs
Server Details
Search and read the official MintMCP documentation, the enterprise MCP gateway.
- Status
- Healthy
- Uptime
- 100.0% over 57 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 4 tools
The tools are mostly distinct: search and list_docs clearly differ (query vs. browse), and get_page vs. fetch are differentiated by input type (slug/URL vs. search-result id). However, fetch and get_page both return the same full markdown content, so there is a small risk of misselection if the agent ignores input details.
Three tools follow a clear verb_noun pattern: get_page, list_docs, and fetch is a bare verb while search is also a bare verb. The naming is recognizable and not confusing, but the mix of bare verbs and verb_noun forms prevents a perfect score.
Four tools is well-scoped for a documentation retrieval server. Each tool has a distinct retrieval strategy (search, browse, URL fetch, ID fetch) and no redundant or unnecessary tools are present.
The tool set covers the full documentation access flow: discover via search, browse via list_docs, and retrieve content via fetch or get_page. There are no obvious dead ends for common user questions or URL-based requests.
Available Tools
4 toolsfetchFetch a Mintive docs pageRead-onlyIdempotentInspect
Fetch the full markdown content of a Mintive 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.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The document id returned by search or list_docs. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| url | Yes | |
| text | Yes | |
| title | Yes | |
| metadata | No |
get_pageGet a Mintive docs pageRead-onlyIdempotentInspect
Fetch a Mintive 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.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | A docs page URL or slug, e.g. "https://www.mintmcp.com/docs/enterprise/sso" or "enterprise/sso". |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| url | Yes | |
| text | Yes | |
| title | Yes | |
| metadata | No |
list_docsList Mintive docsRead-onlyIdempotentInspect
List the Mintive 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.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Optional category name to filter by, e.g. "Enterprise" or "Agent Monitor". |
Output Schema
| Name | Required | Description |
|---|---|---|
| categories | Yes |
searchSearch Mintive docsRead-onlyIdempotentInspect
Search the full Mintive documentation and get back matching pages with their ids, titles, and URLs. Use this first for any Mintive 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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | 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". |
Output Schema
| Name | Required | Description |
|---|---|---|
| results | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
4 tool updates
- First observed
fetch - First observed
get_page - First observed
list_docs - First observed
search
Related MCP Connectors
Search and read the Metabind documentation: MCP Apps, BindJS, the SDKs, the CLI, and the APIs.
Search and read the Free Battery Factory docs (LiteShip, batpak) as live MCP tools.
Search and read the current MemorySync documentation while writing integration code.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceSearch and read Kakao Developers REST API documentation through the MCP protocol.-
- FlicenseAqualityDmaintenanceEnables users to search and fetch Google's Gemini API documentation directly within an MCP-compliant environment. It provides structured access to guides and references for features like function calling, embeddings, and text generation.2-
- AlicenseAqualityDmaintenanceSearch and fetch MCP protocol documentation using BM25 search with weighted scoring and stemming.242 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for documentation search that automatically indexes web documentation sites and provides semantic, full-text, or hybrid search capabilities.7 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.