Connect assistants with MCP

1. Add Fryll’s MCP URL to your assistant’s remote MCP connections.
2. Follow the sign-in prompt and choose your Fryll account.
3. Select the workspaces the assistant can read, enable posting where needed, and choose a default workspace.
4. Review the permissions and approve the connection. Your assistant completes authentication automatically.

Open Connected apps to change workspace access, posting permissions, or the default workspace. You can disconnect an assistant at any time. Desktop Settings and the mobile You screen also link to this page.

Password changes revoke your connections. Your assistant may ask you to sign in again when a connection expires.

When you need to discover workspaces, callget_context orlist_workspaces. Either tool returns names, slugs, permissions, and the default; there is no need to call both. Pass the selected name or slug inworkspace. Use the default when the user has not established a different workspace, and ask when the destination is ambiguous.

workspace:read permits discovery, accessible history, search, threads, and activity. messages:write permits sending as the user. Each workspace has its own grant; existing conversation permissions still apply.

Pass a channel name such as#general inconversation. Known workspace and channel names work directly, without lookup calls. For direct conversations, use the conversation ID returned by list_direct_conversations. To send, supplyworkspace,conversation,text, and a fresh UUIDidempotency_key. Reuse that key only for retries of the same message. The response includes the stored message, app badge data, and message links, so another read is unnecessary.

{
  "workspace": "Acme Team",
  "conversation": "#general"
}

Read a message or thread by passing a Fryll message link inmessage_url toget_message orget_thread. To reply, add the link asreply_to when sending. The link must belong to the selected workspace and conversation, and all access checks still apply.

Workspace names must match exactly. Ambiguous names are rejected; use the workspace slug prefixed withslug: to choose explicitly. Client approval prompts are separate from OAuth consent and follow the assistant’s permission settings.

Messages display the connected user’s avatar and an app badge. You can see which connected app sent a message in its menu.