AIOS Co-Founder MCP
# aios-cofounder-mcp
Production-ready MCP server for a Business Co-Founder / Executive Assistant.
## Features
- FastMCP server over STDIO by default
- Lightweight SQLite storage for assistant state
- Google OAuth + Gmail, Calendar, Contacts tools
- Web search + fetch helpers
- Approval gating for sensitive actions
## Setup
1. Create a virtual environment and install dependencies:
```bash
uv sync
```
2. Configure environment variables:
```bash
cp .env.example .env
```
3. Run the MCP server (STDIO transport):
```bash
uv run aios-cofounder-mcp
```
## Notes
- Google OAuth requires valid `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET`.
- Set `OAUTH_REDIRECT_BASE_URL` to the public base URL for this server (e.g., an ngrok/cloudflared URL).
- Set `GOOGLE_OAUTH_SCOPES` to a space- or comma-separated list of scopes.
- The OAuth callback is served at `/oauth/google/callback` by this MCP server.
- For local dev, start a tunnel to port `8765` (default callback bind port) and set `OAUTH_REDIRECT_BASE_URL=https://<public-domain>`.
- By default the server uses SQLite at `./aios_cofounder_mcp.db`.
- Tools that modify external systems require approval before execution.
## Known limitations
- Free/busy uses the primary calendar only.
- OAuth callback listener is always started when `OAUTH_REDIRECT_BASE_URL` is set.
## TODO
- Consolidate OAuth error mapping for client display.
- Add pagination for repository list endpoints.
## Ops notes
- SQLite file and parent directory are created on first run.
- Keep `OAUTH_STATE_TTL_SECONDS` short in shared environments.
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.