Obsidian iCloud MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | Your task is to read file from /Users/username/Library/Mobile Documents/iCloud |
| read_multiple_filesA | Read the contents of multiple files simultaneously. This is more efficient than reading files one by one when you need to analyze or compare multiple files. Each file's content is returned with its path as a reference. Failed reads for individual files won't stop the entire operation. Only works within allowed directories. |
| write_fileA | Your task is to write file to an appropriate path under /Users/username/Library/Mobile Documents/iCloud |
| edit_fileA | Edit a specific file under /Users/username/Library/Mobile Documents/iCloud |
| remove_fileD | – |
| remove_multiple_filesD | – |
| create_directoryA | Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. If the directory already exists, this operation will succeed silently. Perfect for setting up directory structures for projects or ensuring required paths exist. Only works within allowed directories. |
| list_directoryB | Your task is to list directory under /Users/username/Library/Mobile Documents/iCloud |
| remove_directoryD | – |
| remove_multiple_directoryD | – |
| move_fileA | Move or rename files and directories. Can move files between directories and rename them in a single operation. If the destination exists, the operation will fail. Works across different directories and can be used for simple renaming within the same directory. Both source and destination must be within allowed directories. |
| full_text_searchC | Tokenize the user's query and the search engine tool will return relevant contents. summarized those contents based on the user's query. |
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 12 tools
Most tools have distinct purposes, such as create_directory for directory creation, edit_file for interactive editing, and read_file for single-file reading. However, there is some overlap between remove_file and remove_multiple_files, and between remove_directory and remove_multiple_directory, which could cause minor confusion in tool selection.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as create_directory, list_directory, and read_file. This consistency makes it easy for agents to predict and understand tool functions across the set.
With 12 tools, the count is well-suited for a file management server, covering essential operations like create, read, edit, move, list, and delete for files and directories. This scope is comprehensive without being overwhelming, allowing for efficient agent workflows.
The tool set provides strong coverage for basic file operations, including CRUD for files and directories, search, and movement. A minor gap is the lack of a tool for copying files or directories, which might require workarounds, but core workflows are well-supported.