Drive
Tools that find, read, create and update the documents in your drive.
The Drive tools give an AI client access to the documents in plnnrly's drive — the long-form written work that lives on a customer, a project, the organisation, or a user's personal drive. A client can search for a document, read it as Markdown, draft a new one, and append to or rewrite an existing one.
Every call runs as the user who minted the MCP token, under exactly the same two layers of authorization the web interface applies: the drive-level permission for that owner (project_drive::access and friends), and then the per-document access rules — folder inheritance, general access, and any per-user grants.
Tools
| Tool | Purpose |
|---|---|
list-drive-documents-tool | Find a document by title, owner or folder. |
list-drive-folders-tool | Browse folders, to place a new document or narrow a search. |
get-drive-document-tool | Read one document's body and metadata. |
create-drive-document-tool | Create a new document. |
update-drive-document-tool | Rename a document, or append to and replace its body. |
Permissions at a glance
| Action | Permission |
|---|---|
| Read documents on a project | project_drive::access |
| Read documents on a customer | customer_drive::access |
| Read documents on the organisation drive | organization_drive::access |
| Read documents on a personal drive | user_drive::access |
| Create a document in any of those drives | the matching …_drive::create |
| Update a document | drive access and edit rights on that document |
Beyond the drive-level permission, each document resolves its own access: a document can be open to everyone with drive access, restricted to named people, or inherit either from the folder it sits in. Whoever creates a document keeps edit access to it, which means a document created through MCP stays editable by the user who created it.
Anything the caller may not see answers exactly as an id that does not exist would, so these tools cannot be used to discover which documents, projects or customers are there.
What these tools do not do
- There is no delete or archive tool. A document created by mistake has to be removed from the plnnrly interface. This is deliberate: it keeps a mis-firing client from removing a colleague's work.
- Document bodies are not searchable. There is no content index, so
searchmatches titles only. Narrow by customer, project or folder instead of guessing at wording. - Uploaded files are read-only. PDFs, images and Office documents appear in listings and return their metadata, but they have no editable body.
- Comments, attachments, tags and access settings are not exposed.
Common workflows
- "Find the onboarding document." —
list-drive-documents-toolwithsearch: "onboarding". - "Summarise the project brief." —
list-drive-documents-tool, thenget-drive-document-tool. - "Add today's meeting notes to the weekly log." —
get-drive-document-tool, thenupdate-drive-document-toolwithmode: "append". - "Draft a technical spec on the ACME project." —
create-drive-document-toolwithowner: "project". - "Tidy up this document." —
get-drive-document-tool, thenupdate-drive-document-toolwithmode: "replace"and theversionfrom the read.