Assistants sign in, and three tools reach the whole API

Assistants sign in, and three tools reach the whole API

AI assistants connect by signing in instead of with a token, three general tools reach every REST API operation, and new organisations start with MCP off.

View as Markdown

REST API

MCP

  • New: claude.ai, ChatGPT and other AI assistants connect by signing in to plnnrly, so no token is needed. See Pick your client.
  • New: An assistant can delete once an administrator switches on Allow destructive actions, and only after you confirm the delete.
  • New: An assistant asks for your confirmation before it replaces a whole Drive document.
  • New: The MCP & API page has its own permissions, View MCP & API and Manage MCP & API. Roles that could open or change the page before keep that right.
  • Changed: Three general tools, search_api, api_read and api_write, replace the tool per feature. Together they reach every REST API operation except file uploads. See Tools.
  • Changed: New personal MCP tokens can no longer be created. Existing ones keep working.
  • Changed: MCP only works while the REST API is on. Organisations that had MCP on and the REST API off got the REST API switched on, so their assistants keep working.
  • Changed: New organisations start with MCP off. Existing organisations keep their setting.