Developer
AimHuge MCP
The Model Context Protocol server at /api/mcp lets Claude (and any MCP-compatible client) read and mutate AimHuge data on your behalf. OAuth 2.1 + PKCE + Dynamic Client Registration — add the URL to Claude and it walks you through Google signin automatically.
Claude.ai / Claude Desktop
- Open Settings → Connectors → Add custom connector.
- Paste
https://aimhuge.com/api/mcp. - Claude hits the endpoint, gets a 401 with discovery metadata, and auto-runs DCR.
- A browser window opens — sign in with Google and click Authorize.
- Claude exchanges the auth code for a token and your tools show up.
Claude Code (CLI)
claude mcp add --transport http aimhuge https://aimhuge.com/api/mcp
The first tool call triggers the OAuth flow in your browser. Tokens are stored per-project.
Available tools
Core
whoami— sanity-check that your bearer is wired.list_decks,get_deck,create_deck— deck CRUD.
Workspace meta
list_accounts— list your connected Google accounts.connect_account_url— get a URL to connect a new account.
Gmail
search_email,read_email,triage_inbox— read side.draft_email,update_draft,list_drafts,delete_draft— draft management.send_draft— send an existing draft (fires tripwire notification).
Calendar
list_calendars,list_calendar_events,get_event.respond_to_event— accept/decline/tentative.create_event_draft— creates a[DRAFT]-prefixed event without emailing attendees.send_event_invite— strips the prefix and mails attendees (tripwire).
Drive / Docs / Sheets
search_drive,read_drive_file.create_doc,append_to_doc.read_sheet_range,append_sheet_row.
Connected accounts
Loading…
Recent sends (tripwire)
Every irreversible send (email, calendar invite) writes a row here and fires a notification email to you. If you see something you didn't authorize, rotate your tokens immediately.
Personal access tokens
For headless clients (CLI configs, MCP inspector, ad-hoc scripts) you can mint a long-lived bearer token without going through the OAuth flow. Gated to allowlisted Google accounts.
Loading…