What is MCP?
BrowserOS Connected Apps use the Model Context Protocol (MCP), an open standard for connecting AI assistants to external systems. Think of it as a single, consistent way to plug your apps into the assistant.Built-in Apps
- Gmail — Send, read, and search emails
- Google Calendar — Create events, check your schedule
- Google Docs — Create and edit documents
- Google Sheets — Create and edit spreadsheets
- Google Drive — Upload, download, and manage files
- Slack — Post messages, manage channels
- Notion — Create pages, manage databases
- LinkedIn — Post updates, manage connections
Connect a Built-in App
- Go to Settings → Connected Apps
- Click Add built-in app and select the app
- Sign in and authorize BrowserOS

Use Connected Apps
Just ask the assistant what you want — it will automatically use the right connected apps.
Example Prompts
Calendar
Calendar
- What’s on my calendar today?
- Schedule a meeting with Sarah tomorrow at 2pm
- When is my next meeting with the marketing team?
- Block off Friday afternoon for focus time
Email
- Show me unread emails from my manager
- Draft a reply to the last email from John thanking him for the update
- Find emails about the Q4 budget from last week
- Send an email to the team with the meeting notes
Slack
Slack
- Post a message to #general saying I’ll be out tomorrow
- What’s the latest message in #engineering?
- Send a DM to Sarah asking if she’s free for lunch
- Summarize what was discussed in #product today
Notion
Notion
- Add “Review Q4 report” to my Notion tasks database
- Create a new page in my Projects database for the website redesign
- What are my open tasks in Notion?
- Update the status of the “Launch campaign” task to complete
Cross-app workflows
Cross-app workflows
- Check my calendar for tomorrow, then draft an email to John summarizing what we’re meeting about
- Find all emails from last week about the budget and create a summary in Notion
- Look at my Slack DMs and add any action items to my Notion tasks
Add a Custom MCP Server
You can connect any MCP-compatible server that exposes an SSE endpoint.- Go to Settings → Connected Apps
- Click Add custom app
- Enter your server URL (e.g.,
http://localhost:8000/sse) and give it a name
Connect to OAuth-Protected Remote Servers
Some remote MCP servers (like Atlassian Jira, GitHub, etc.) require OAuth authentication. Use mcp-remote and supergateway to handle the OAuth flow locally:http://localhost:8000/sse as a custom MCP in BrowserOS.
Keep the terminal running while you use BrowserOS. The local server handles authentication and proxies requests to the remote MCP server.
Example: Atlassian Jira
Example: Atlassian Jira
http://localhost:8000/sse as a custom MCP.Example: GitHub
Example: GitHub
http://localhost:8001/sse as a custom MCP.Privacy & Security
Your data stays local
BrowserOS connects directly to your accounts. Credentials are stored locally on your machine.
You control access
Connect or disconnect apps anytime in Settings.
Secure OAuth
Built-in apps use OAuth flows — BrowserOS never sees your passwords.
