Omni-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mount_folderA | Mount a local folder so its .txt and .md files become readable resources. The mount is persisted across server restarts. |
| add_new_sourceA | Mount a local folder so its .txt and .md files become readable resources. The mount is persisted across server restarts. (Alias for mount_folder.) |
| mount_urlA | Fetch a web page, convert its HTML to Markdown, and expose it as an MCP resource. The content is cached and persisted across server restarts. |
| mount_sqliteA | Mount a local SQLite database file. Its schema is automatically exposed as an MCP resource so the AI knows the table structures. Use query_sqlite to run SELECT queries against it. |
| query_sqliteA | Execute a read-only SQL query (SELECT only) against a mounted SQLite database and return the results as JSON. Maximum 100 rows returned. |
| unmount_folderA | Unmount a previously mounted folder so its files are no longer exposed as resources. |
| list_mountsA | List all currently mounted directories, URLs, and databases. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| test-resources/hello.txt | Local file: test-resources/hello.txt |
| test-resources/notes.md | Local file: test-resources/notes.md |
| test-resources/subdir/deep-note.md | Local file: test-resources/subdir/deep-note.md |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but there is notable overlap between 'add_new_source' and 'mount_folder', which are explicitly described as aliases for the same operation. This duplication could cause confusion or misselection by an agent, though other tools like 'mount_sqlite', 'mount_url', and 'query_sqlite' are clearly differentiated.
The naming follows a consistent verb_noun pattern throughout, such as 'mount_folder', 'list_mounts', and 'query_sqlite'. The only deviation is 'add_new_source', which breaks the pattern but is explained as an alias for 'mount_folder', maintaining overall readability and predictability.
With 7 tools, the count is well-scoped for a server focused on mounting and querying various data sources. Each tool serves a clear purpose in the workflow, from mounting folders, URLs, and databases to listing and unmounting, without feeling excessive or insufficient for the domain.
The tool set provides comprehensive coverage for mounting and accessing different resource types (folders, URLs, SQLite databases), with operations for listing and unmounting. A minor gap is the lack of a tool to unmount URLs or SQLite databases specifically, but agents can likely infer or work around this using existing tools.