omni-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMNI_AGENT_MODE | No | Set to 'true' to enable potentially dangerous tools like system_execute_command and system_write_file | |
| SLACK_BOT_TOKEN | No | Slack bot token for Slack tools | |
| GITHUB_PERSONAL_ACCESS_TOKEN | No | GitHub personal access token for GitHub tools |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_search_reposB | Search for GitHub repositories |
| github_get_issueA | Get details of a specific GitHub issue |
| slack_send_messageA | Send a message to a Slack channel |
| system_read_fileB | Read a local file from the system |
| system_list_dirB | List contents of a local directory |
| web_fetchA | Fetch a public web page and read its content as clean Markdown |
| memory_storeA | Save a note, preference, or piece of context to persistent memory so it can be recalled in future conversations. |
| memory_retrieveB | Retrieve a previously saved memory by its key. |
| memory_listA | List all the memory keys currently saved in persistent storage. |
| git_statusA | Run git status to see the state of the working directory and staging area. |
| git_diffB | Run git diff to see exact line-by-line code changes. Shows unstaged changes by default. |
| git_logB | Run git log to see recent commit history. |
| git_commitA | Commit currently staged changes with a specific message. |
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 13 tools
Each tool has a unique domain prefix (github_, slack_, system_, web_, memory_, git_) and a distinct action, making it clear which tool to use for a given task. There is no overlap in functionality between tools from different domains.
Most tools follow a <domain>_<verb> or <domain>_<verb>_<object> pattern (e.g., github_search_repos, slack_send_message), but git tools use nouns (git_status, git_diff, git_log) instead of verbs, breaking the consistency. Memory tools also use verbs without objects (memory_store) rather than verb_noun.
With 13 tools covering 6 different domains, the count is reasonable for an omnibus server. It provides a focused set of utilities without overwhelming the user, though some domains could benefit from a few more tools.
Each domain has significant gaps: GitHub only offers search and get issue (no create/update/delete), Slack only send message (no read/list), system only read and list dir (no write/delete), and git lacks add, push, pull, and branch operations. This can cause agent failures when users request common operations.