Skip to main content
Plugsurfing’s Mintlify documentation includes a public MCP server at:
  • https://plugsurfing.mintlify.site/mcp
Use it with an MCP-compatible AI client when you want the assistant to search and read the published Drive API documentation while helping with an integration. For the wider AI-assisted integration workflow, start with the AI Integration Playbook.

​
What MCP provides today

The current Mintlify MCP server is scoped to the public Plugsurfing Developer documentation. It can help an AI client to:
  • search the published guides and API-reference pages
  • read the documentation and OpenAPI contract
  • find relevant endpoint, request, response, and authentication details
  • report feedback about an incorrect or incomplete documentation page
This gives an AI assistant current documentation context without copying pages or the OpenAPI file into a prompt manually.

​
Current scope

The MCP server currently provides read-only access to the published documentation and OpenAPI contract. It cannot call Drive API endpoints or access customer environments.

​
Use MCP with the guides and OpenAPI contract

Use each source for a different purpose:
  • use the Drive API guides to understand flows, setup steps, and operational caveats
  • use the https://plugsurfing.mintlify.site/reference/openapi.json for the exact API schema
  • use https://plugsurfing.mintlify.site/mcp when you want an AI client to search and read that published information
The MCP server reflects the published documentation. The OpenAPI contract remains the source of truth for endpoint schemas.

​
Connect an AI client

Add this URL to an MCP-compatible client, such as Claude, Cursor, or VS Code:
Then ask the client a focused question, for example:
The client can search the documentation and inspect the OpenAPI contract. It cannot make the Drive API calls for you.

​
API tools may be added later

Mintlify can expose selected OpenAPI endpoints as MCP tools when they are explicitly configured. Drive API endpoints are not exposed this way today. If this is added in the future, only endpoints that have been reviewed for security and safe AI use should be enabled. This page will then be updated with the available tools and their authentication requirements.