MCP server

Installation

The pdrive MCP server supports OAuth with dynamic client registration. Your editor handles the authentication flow automatically. No API keys needed.

Claude Code

Add to your .claude/settings.json or project .mcp.json:

{
  "mcpServers": {
    "pdrive": {
      "type": "url",
      "url": "https://pdrive.io/mcp"
    }
  }
}

When you first connect, your editor will open a browser window to authorize access to your pdrive account.

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "pdrive": {
      "type": "url",
      "url": "https://pdrive.io/mcp"
    }
  }
}

Windsurf

Add to your Windsurf MCP configuration (~/.windsurf/mcp.json):

{
  "mcpServers": {
    "pdrive": {
      "type": "url",
      "url": "https://pdrive.io/mcp"
    }
  }
}

API key authentication

If your editor does not support OAuth, you can authenticate with an API key instead. Create one at Settings > API keys and pass it as a Bearer token:

{
  "mcpServers": {
    "pdrive": {
      "type": "url",
      "url": "https://pdrive.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Tools

The MCP server exposes these tools:

list_accounts

List all accounts you have access to.

list_projects

List projects in an account. Requires account.

list_documents

List documents in a project. Requires account and project.

get_document

Get a document's metadata and latest version content. Requires account, project, and filename.

create_project

Create a new project in an account. Requires account and name. Needs write scope.

publish_document

Publish a markdown document to a project. Requires account, project, filename, and content. If a document with that filename already exists, a new version is created. Needs write scope.

Example tool call:

{
  "tool": "publish_document",
  "arguments": {
    "account": "acme",
    "project": "docs",
    "filename": "architecture.md",
    "content": "# Architecture\n\nOverview of the system design."
  }
}

Resources

The MCP server exposes document content as resources. Each document is available at:

pdrive://documents/{document_id}

Your editor can read these resources to access document content directly.

Prompts

The MCP server includes prompts for common workflows:

• publish_document: guides you through publishing a new document or updating an existing one
• review_document: fetches a document and helps review its content