Maya: Version two point four of Cursor's official X plugin, shipped on September fourteenth, now requests the d m dot read and d m dot write permissions, which means the plugin can finally reach direct messages through X's hosted service. That opens up X Chat operations that weren't part of the connection before.

James: And the practical catch is that existing users have to sign in to X again before those permissions take effect. Once you do, the X Chat tools cover five operations: listing conversations, fetching events, sending messages, showing typing activity, and sending read receipts.

Maya: What I like is that this expands one existing connection rather than adding a second account. Everything runs as your own X account through OAuth. And notably, posting stays out of scope. The README says the plugin does not request tweet dot write, so an agent using this configuration cannot publish posts as you.

James: Right, so search, timelines, trends, bookmarks, lists, blocks, and mutes all remain, and now conversations get added on top. You add it from chat with slash add dash plugin x, and it requires Cursor three point one three or later.

Maya: Moving over to something more visual. On September tenth, Cursor added a Gamma plugin, version one point zero, that connects agents to Gamma's hosted service to generate presentations, documents, webpages, and social posts. A generation can start from a prompt, an outline, or a Gamma template.

James: You install it from Cursor Settings under Plugins, or use slash add dash plugin gamma from chat. It signs you in through Gamma using OAuth two point zero with dynamic client registration, so there's no token or client ID to copy. A Gamma account is required, and generated material consumes credits from that account.

Maya: One detail worth flagging is that generation runs asynchronously. The service returns a generation ID, and the agent checks that ID until the work completes, rather than holding one request open the whole time. After that, separate export tools produce PDF, PPTX, and PNG files.

James: And it isn't only creation. The plugin can browse existing Gamma material, listing Gammas, themes, and folders, and it can pull analytics like views and comments. So one installed plugin covers generation, export, browsing, and analytics.

Maya: Also from September tenth, there's an Excalidraw plugin, version one point zero, that lets an agent create hand-drawn diagram views from elements you describe in chat and export the current drawing as an dot excalidraw file. The nice part is that no account or authentication is required for the hosted service it configures.

James: That lowers the barrier a lot. It connects to Excalidraw's hosted service, and clients that support MCP Apps can show the result as an interactive diagram view right inside the conversation. There's also a checkpoint feature, so you can save a drawing's state during a session and restore it later without rebuilding every element.

Maya: One thing to be clear about, James: this configures the public Excalidraw service, not Excalidraw plus. Those workspaces use a separate authenticated address that isn't part of this plugin, so installing it does not connect your Excalidraw plus workspace.

James: Good distinction. You install it from Settings under Plugins or with slash add dash plugin excalidraw, and it requires Cursor three point one three. The drawing, export, and checkpoint tools all come from the hosted Excalidraw service itself.

Maya: Now for the data folks. Also on September tenth, Cursor added an official Google Cloud BigQuery plugin, version one point zero, connecting agents through Model Context Protocol. Its documented operations cover exploring BigQuery datasets and tables and running SQL queries.

James: Authentication uses BigQuery user OAuth, so you sign in with Google Cloud rather than configuring an API key or client ID. Importantly, your existing Google Cloud access controls still decide which projects, datasets, and tables the account can reach and which queries it can run.

Maya: Because the service is hosted by Google Cloud, the installed plugin is really a connection and authentication definition rather than a bundled database client. The workflow is inspect the datasets and tables exposed to you, then run SQL under your existing permissions.

James: You install it from Settings under Plugins, searching for Google Cloud BigQuery, or with slash add dash plugin google dash cloud dash bigquery. For teams already keeping analytical data in BigQuery, setup is just adding the plugin and completing the Google login.

Maya: And the last one lands on September fourteenth: a SharePoint plugin that connects Cursor agents to Microsoft SharePoint through Model Context Protocol. It's explicitly read-only. The changelog names the delegated Sites dot Read dot All permission, and the documentation says write operations are not part of the tool set.

James: So an agent can inspect team sites and documents the account already reaches, but it cannot modify or delete them. The documented operations cover searching for sites, browsing document libraries and folders, searching and reading files, and reading SharePoint lists and their items.

Maya: Cursor draws a clear line between this and its OneDrive integration too. OneDrive targets your personal drive, while SharePoint targets sites and their team document libraries.

James: You install it through Cursor's plugin interface and then sign in with Microsoft, and it requires Cursor three point one nine. Access is delegated through that account, so anything unavailable to your Microsoft sign-in stays unavailable to the agent.

Maya: That's the plugin roundup from Cursor HQ. We'll see you at the next commit.