Connected apps

Connect first-party services that give Vuti approved context and delivery options, or expose Vuti to compatible assistants through its remote MCP connector.

Open app settings

Google Drive, Calendar, and Gmail

Workspace owners and admins can connect Google Drive, Google Calendar, and Gmail independently from Settings → Apps.

• Google Drive uses a file picker. Only files deliberately selected into the workspace are available to Vuti; connecting Drive does not give Vuti free access to browse the account.
• Google Calendar is read-only. After connecting, an owner or admin explicitly selects which calendars Vuti may use when planning around launches, events, promotions, and deadlines. Vuti does not store event copies or read guest lists and attendee email addresses.
• Gmail is send-only. Vuti must show the complete recipients, subject, and body, then wait for a separate confirmation before sending. Vuti does not read the inbox.

Selected Drive files and calendars are shared workspace context. Disconnecting either service removes its Vuti selections. Disconnect any Google service at any time from the same settings page.

Connect your agent to Vuti

Open Settings → Apps and choose Set up Grok Bot, Claude, ChatGPT / Dot, Muse, or another agent. Setup includes the server URL, a read-only connection test, a workspace-specific first-draft prompt, and connection refresh. You can also open Vuti’s agent setup page.

Start with Grok Bot

1. In Vuti, select the workspace you want your agent to use, then open Settings → Apps → Set up Grok Bot.
2. Copy the connection request and paste it into Grok Bot. If asked to add a custom MCP server, use https://www.app.vuti.io/mcp, with Streamable HTTP and OAuth.
3. Complete Vuti sign-in privately. Keep Read context and prepare drafts selected. Leave generation and publishing permissions off for the first test.
4. Copy the connection test into Grok Bot. It should return your identity, selected workspace, brand voice, and connected platforms without changing anything.
5. Refresh connections in Vuti to inspect the authorization. Authorization alone does not establish that tool calls work; the connection test checks that separately.
6. Copy the first-draft prompt. It creates one text-only post in needs_review and returns a Vuti link. Open Review to inspect it before approving or scheduling.

Grok Bot documents support for MCP servers. Client compatibility still needs a successful sign-in and tool test for your account.

Other agents

• Claude: add the URL in custom connector settings, complete OAuth, and run the same connection test. Custom connector availability depends on your account.
• ChatGPT / Dot: use a supported Vuti app or plugin where available. Before public listing, custom MCP app testing may require ChatGPT Developer mode. Dot needs a supported, enabled plugin; a custom ChatGPT app alone does not establish Dot compatibility.
• Muse: consumer Muse custom-MCP access has not been verified. Its browser can be used to try Vuti after private sign-in. Muse Code separately supports remote MCP with OAuth. These are distinct connection paths.
• Other clients: remote Streamable HTTP MCP with OAuth is required. Clients without that support need a compatible bridge. No Vuti API key is required.

What connected assistants can do

New OAuth connections let you choose server-enforced permissions:

• Read context and prepare drafts is the recommended default. It allows reading workspace context, creating text drafts, editing unapproved drafts, and reusing saved assets.
• Read only allows inspecting context without draft changes.
• Generate plans and media separately permits AI generation using Vuti credits.
• Change approvals and publishing schedules separately permits the agent to approve and schedule content under your instructions. Enable it only when you intend the agent to have that authority.

Without publishing permission, a connection cannot approve, schedule, or change an already-approved, scheduled, or published post. You can still approve its drafts in Vuti. These permissions do not expand your workspace role or subscription entitlements. OAuth access follows your account’s accessible workspaces; the setup prompts explicitly select the current workspace for testing.

For LinkedIn document carousels, save a PDF, PPT, PPTX, DOC, or DOCX file in Assets first. A connected assistant can then call list_library_assets and pass the document's asset_id to create_post, creating the new carousel draft with the document already attached. The assistant can also use use_library_asset to attach a saved document to an existing LinkedIn draft.

Connected assistants do not bypass Vuti's product rules. Publishing remains tied to supported connected social accounts, workspace permissions, plan limits, credits, and approval controls.

Review and revoke access

Open Settings → Apps to review Google connections and external assistant OAuth grants. Revoking an external assistant invalidates its access and refresh tokens; reconnect it later if you want to authorize it again. Refreshable connections remain visible after their short-lived access token expires.

Connections authorized before permission selection was introduced show Legacy access and retain their original broad tool access. Revoke and reconnect to select narrower permissions. “Token issued” is an authorization timestamp, not a claim that the agent recently used Vuti.

Troubleshoot a connection

If sign-in does not open, add a custom remote MCP server with OAuth in your client. Reconnect after an expired or revoked session. Check Billing if tools report a plan or credit requirement. A successful OAuth connection does not unlock paid capabilities. If a draft creation times out, inspect existing posts before retrying so you do not create duplicates. For missing attachments, save the file in Assets first and ask the agent to reuse its library asset.

Vuti memory and an external assistant's own memory are separate. See Memory for the boundary.