aum-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | No | Google OAuth client ID (required for Gmail, Calendar, Contacts tools) | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret (required for Gmail, Calendar, Contacts tools) | |
| GOOGLE_REFRESH_TOKEN | No | Google OAuth refresh token (required for Gmail, Calendar, Contacts tools, obtained by running scripts/google-auth.mjs) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| note_setB | Save a note with a key. Overwrites existing notes with the same key. |
| note_getC | Retrieve a note by key. |
| note_listA | List all saved note keys. |
| note_deleteC | Delete a note by key. |
| word_readA | Extract all text content from a Microsoft Word (.docx) file. |
| word_createB | Create a Microsoft Word (.docx) file from structured content (headings, paragraphs, bullets). |
| ppt_readA | Extract all text content from a Microsoft PowerPoint (.pptx) file, slide by slide. |
| ppt_createA | Create a Microsoft PowerPoint (.pptx) file from a list of slides, each with a title and optional bullet points. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools are cleanly divided into two distinct domains: notes (set/get/list/delete) and Office documents (Word read/create, PowerPoint read/create). Within each domain, actions are clearly differentiated, with no overlapping purposes.
All tools follow a consistent pattern: resource prefix (note_, word_, ppt_) followed by a verb in snake_case. This makes the tool set predictable and easy to navigate for both humans and agents.
With 8 tools spanning two focused areas, the count is well-scoped. Each tool serves a clear, necessary function without redundancy, and the server avoids being overly large or sparse.
Notes have full CRUD coverage. For Word and PowerPoint, read and create are covered, but there are no tools for updating existing documents or deleting them. This is a minor gap, but the core workflows (viewing and creating documents) are supported.