MCP Tool Suite is the full set of actions an AI client can take inside 📝MythOS MCP — 41 tools spanning memo creation to daily journaling to template management, each carrying safety annotations so a client knows what's read-only versus destructive before it calls one. It exists because a knowledge library isn't useful to an AI that can only read it; the tools are what make MythOS MCP a collaborator rather than a search index. It's for anyone building or driving an AI client against a MythOS library.
Key Capabilities
- Memo CRUD — create, read, update, and delete memos, plus targeted section and line edits
- Search & discovery — full-text and semantic search, backlinks, related memos, library trends, delta sync
- Daily memos & tasks — read and edit daily journal entries, manage the task system
- Templates — list, read, create, update, and delete memo and daily templates
- Communities — list communities and search their approved posts
- Collaboration & library ops — invite or revoke collaborators, move memos between libraries, reindex embeddings
- Tags, media, and subscribers — manage tags, upload images, add or update newsletter subscribers
- Context —
get_contextloads your 📝Augmentation System; every write tool requires it first
Getting Started
Any MCP-connected client discovers the full tool list automatically once connected — see 📝MythOS MCP for how to connect.
FAQ
- How many tools are there? 41 as of this writing — the count grows as new capabilities ship.
- Which tools are safe to call without confirmation? Every tool carries read-only, destructive, and idempotent annotations per the MCP spec, so a well-behaved client can reason about risk before calling one.
- Do I need to call every tool myself? No — describe what you want in plain language; your AI client selects the right tool.
- Can an agent delete something by accident? Deletes are soft (memos move to trash, recoverable), and destructive tools carry an explicit annotation so clients can gate them behind confirmation.
Related
- 📝Internal Agent API — the same capabilities over plain REST, for non-MCP clients