AIOS Co-Founder MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Your Google OAuth client ID (required for Google OAuth) | |
| GOOGLE_OAUTH_SCOPES | Yes | A space- or comma-separated list of Google OAuth scopes | |
| GOOGLE_CLIENT_SECRET | Yes | Your Google OAuth client secret (required for Google OAuth) | |
| OAUTH_REDIRECT_BASE_URL | Yes | The public base URL for this server (e.g., an ngrok/cloudflared URL) used for OAuth callbacks |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_google_startA | Start Google OAuth flow and return an authorization URL. |
| auth_statusB | Return OAuth status for an approval_id or current connection status. |
| gmail_searchC | Search Gmail messages and return metadata. |
| gmail_get_messageC | Return full email content (plain text preferred). |
| gmail_get_threadB | Return all messages in a thread. |
| gmail_create_draftC | Create an email draft only. |
| gmail_apply_labelsC | Apply labels to one or more messages. |
| calendar_list_eventsC | List calendar events in a time range. |
| calendar_find_free_slotsC | Find available time slots in a range. |
| calendar_create_eventB | Create a calendar event (requires approval). |
| calendar_update_eventB | Update event details (requires approval). |
| calendar_cancel_eventC | Cancel an event (requires approval). |
| contacts_searchC | Search Google Contacts. |
| contacts_getC | Return full contact details. |
| contacts_create_or_updateC | Create or update a contact (requires approval). |
| web_searchC | Perform a web search and return top results. |
| web_fetchB | Fetch page content and extract readable text. |
| summarize_emailC | Summarize an email and store assistant memory. |
| meeting_briefD | Prepare a meeting brief. |
| compose_email_replyC | Generate an email reply draft (never sends). |
| approval_requestC | Create a pending approval record. |
| approval_resolveC | Approve or deny an action. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| inbox_triage | |
| meeting_prep | |
| email_followup | |
| weekly_review |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| connections_status | |
| assistant_companies | |
| assistant_contacts | |
| assistant_notes | |
| assistant_audit |
TDQS
Scored across 22 tools
Each tool has a clearly distinct purpose with no significant overlap. Tools are organized by domain (e.g., calendar, contacts, Gmail, web), and actions within each domain are specific and non-redundant. For example, calendar tools cover create, list, update, cancel, and find_free_slots without ambiguity.
Tool names follow a consistent snake_case pattern with a clear domain_action structure (e.g., calendar_create_event, gmail_search, web_fetch). All tools adhere to this convention, making them predictable and easy to understand across the entire set.
With 22 tools, the count is slightly high but reasonable given the broad scope covering calendar, contacts, Gmail, web, and AI-assisted tasks. Each tool serves a specific function, though some consolidation might be possible without losing utility, keeping it well-scoped for an assistant-focused server.
The toolset provides comprehensive coverage for an AI assistant domain, including CRUD operations for calendar and contacts, full email handling (search, get, draft, labels), web interactions (fetch and search), and AI utilities (summarize, meeting brief). No obvious gaps exist; agents can perform end-to-end workflows seamlessly.