Is there a Mintlify MCP server?

Yes. Mintlify runs a hosted admin MCP server at mcp.mintlify.com that AI tools connect to over an interactive OAuth login, and its documented tools edit pages, restructure navigation, update docs.json and open pull requests. Connecting Mintlify API directly through Jentic reaches a different surface: your agent gets all 9 REST operations from the spec, including the deployment trigger, agent jobs, the assistant, docs search and the analytics exports, which the admin MCP's documented tools do not cover. Connecting direct also keeps another server's tool definitions out of your agent's context, because Jentic returns operations on demand, and your own rules decide which of them the agent may call, where an admin MCP session inherits whatever permissions your Mintlify account already carries. Adding the next API is another import rather than another install and login.

What authentication does the Mintlify API use?

HTTP bearer tokens in the Authorization header. Mintlify documents three API key types, and two of them apply to the 9 operations here: the admin key (prefix `mint_`) authenticates the project, agent and analytics operations, and the assistant key (prefix `mint_dsc_`) authenticates the discovery assistant and search operations. The third, the Index key (prefix `mint_us_`), belongs to Mintlify's separate Index API on a different host and is not used by anything on this page. Your own Jentic One instance holds both keys and injects the right one per operation.

Do I need a paid Mintlify plan to call these operations?

Yes. Mintlify's REST API introduction states that 'The platform REST API requires a Pro or Enterprise plan', and all 9 operations on this page sit on that platform surface: deployments, agent jobs, the assistant, docs search and the analytics exports. A project on any other plan cannot call them, so confirm the organization's plan before you wire an agent to Mintlify. Plan tiers are listed at mintlify.com/pricing.

Can I deploy my docs from CI with the Mintlify API?

Yes. Call POST /v1/project/update/{projectId} after the docs commit lands; the response returns a status id. Poll GET /v1/project/update-status/{statusId} until it reports a successful build.

How do agent jobs differ from a normal deployment?

Agent jobs at POST /v2/agent/{projectId}/job ask Mintlify's documentation agent to draft or edit pages from natural-language instructions. The agent produces a draft you can refine via follow-up messages on /v2/agent/{projectId}/job/{id}/message. Deployments simply rebuild and publish the current source.

How do I query the docs assistant through Jentic?

Install Jentic One on your own machine, import Mintlify API from the Jentic API Directory, then have your agent search by intent for 'ask the docs assistant'. Jentic returns POST /discovery/v2/assistant/{domain}/message with its input schema and the assistant key already wired. Provide the published docs domain and the user question; the answer comes back grounded on the docs content.

How do I monitor docs feedback and assistant conversations?

GET /v1/analytics/{projectId}/feedback returns thumbs-up and thumbs-down ratings on docs pages, while GET /v1/analytics/{projectId}/assistant returns conversation history. Schedule the agent to pull both endpoints daily and report on quality trends.

Can I limit what my agent is allowed to do with the Mintlify API?

Yes. Because you run Jentic One yourself, your own rules decide which Mintlify operations and tokens the agent may use. Mintlify puts the project id and job id in the URL path, such as POST /v1/project/update/{projectId} and POST /v2/agent/{projectId}/job, so a rule can pin the agent to a single project. You pick the exact operations it can call, so a high-impact action like triggering a deployment is available only if you add it, while you keep read-only calls such as GET /v1/analytics/{projectId}/feedback separate.