Fryll meets your AI
Your AI.
Your team.
Connected.
Bring Claude or Codex into your team’s conversations. Catch up, find answers, and share updates without leaving your assistant.
Share the release update in #engineering.
01 / Get connected
Pick your assistant.
Add Fryll, sign in, and choose what to share.
No API keys to create or copy.
You’ll need a Fryll account and at least one workspace. Create a workspace →
Connect Claude to Fryll
Add a custom connector.
In Claude Desktop or claude.ai, open Customize → Connectors → + Add → Add custom connector. Some versions put Connectors under Settings.
Name it Fryll, then paste this server URL and continue:
MCP server URLhttps://api.fryll.com/mcpChoose automatic sign-in.
If authentication options appear, select Sign in now and Register automatically under OAuth client. Leave client ID, client secret, and request headers empty.
Allow the connection in Fryll.
Sign in to Fryll. Choose your workspaces, posting permissions, and default workspace, then select Allow connection. See what to choose below.
Enable Fryll in your chat.
Return to Claude. Open + → Connectors in the chat and enable Fryll. If the connector still shows Connect, click it to finish signing in.
On a Team or Enterprise account, your organization’s owner or admin may need to add the connector first. Each person then connects their own Fryll account.
Claude’s connector guide ↗Using Claude Code in the terminal?
If Fryll is already available through your Claude account, use that connection. Otherwise, with Claude Code installed, run:
claude mcp add --transport http --scope user fryll https://api.fryll.com/mcpStart Claude Code, enter /mcp, choose Fryll, and follow the authentication prompt. Approve access in Fryll, then return to Claude Code.
Connect Codex to Fryll
Add an MCP server.
In the desktop app, open Settings → MCP servers → Add server (or Add custom, depending on your version).
Paste Fryll’s server URL.
Name it Fryll, choose Streamable HTTP, and paste this URL:
MCP server URLhttps://api.fryll.com/mcpLeave token and header fields empty. Save, then restart when prompted.
Sign in with Fryll.
Select Authenticate for Fryll. Your browser opens the Fryll sign-in and permissions page. Choose your workspaces and default, then select Allow connection.
Try it in a new chat.
Return to Codex and start a new chat. Ask it to list your Fryll workspaces. You can also use
/mcpto check the connection.
Prefer the Codex CLI?
With the Codex CLI installed, run:
codex mcp add fryll --url https://api.fryll.com/mcpFollow the browser sign-in. If it does not open automatically, run:
codex mcp login fryllThe CLI, desktop app, and IDE extension share MCP configuration on the same host. Restart or refresh the client after adding Fryll.
Connect another MCP assistant
Use a client that supports remote Streamable HTTP, OAuth, and automatic client registration (DCR). Setup labels vary by app.
Create a remote MCP connection.
Open your assistant’s MCP or connector settings. Add a server named Fryll and select Streamable HTTP. Paste this server URL:
MCP server URLhttps://api.fryll.com/mcpUse OAuth authentication.
Choose OAuth with automatic registration. Fryll’s sign-in page opens in your browser; no manually created app, API key, or client secret is needed.
Choose access and start a chat.
Approve your workspaces and default in Fryll. Return to your assistant, enable the connection, and ask it to list your Fryll workspaces.
A client that only supports local servers or fixed API keys needs a different setup. Check its remote MCP and OAuth support before connecting.
Read the Fryll MCP guide03 / Start a conversation
Put it to work.
Copy a prompt into your assistant.
Replace bracketed names with your own.
List my Fryll workspaces and tell me which is the default. Do not send any messages.
Summarize the latest messages in #[channel] in my [workspace] Fryll workspace. Highlight decisions and open questions.
Draft a short update about our work in this chat for #[channel] in my [workspace] Fryll workspace. Show me the draft and ask before sending it.
Use workspace and channel names in your prompts. Your assistant handles the IDs.
A few useful answers
Before you get started.
What can my assistant do in Fryll?
Why does Claude or Codex still ask for permission?
It connects, but cannot send a message.
A workspace or private channel is missing.
The assistant asks for a client ID or API key.
/mcp and that your client supports remote MCP with OAuth.Fryll is connected, but the assistant cannot see its tools.
Does this create an autonomous bot in my workspace?
How do I change access or disconnect?
Less copying. More context.