Back to Directory/Developer Tools

io.github.bitofacoder/omni-mcp-server

All-in-one MCP server: GitHub, Git, Slack, web fetch, memory, and filesystem. Agent Mode opt-in.

Developer ToolsTypeScriptv1.1.1

Omni MCP Server ๐Ÿš€

One MCP server instead of six. GitHub, local Git, Slack, web fetching, persistent memory, and filesystem tools โ€” 15 tools in a single config entry, with dangerous capabilities off by default.

npm version npm downloads License: MIT Model Context Protocol

Omni MCP Server setup wizard configuring Claude Desktop and listing all 15 bundled tools, with Agent Mode off by default

Why Omni?

Setting up MCP usually means installing and configuring a separate server for every capability โ€” one for GitHub, one for filesystem, one for memory, one for fetch. Each has its own config block, its own runtime, its own startup cost.

Omni bundles the everyday developer tools into one server, one config entry, one npx command:

You'd normally installโ€ฆWith Omni
server-githubโœ… built in
server-filesystemโœ… built in
server-memoryโœ… built in
server-fetchโœ… built in
a git serverโœ… built in
a Slack serverโœ… built in
  • ๐Ÿ”’ Safe by default โ€” shell execution and file writes are disabled unless you explicitly opt in to Agent Mode.
  • ๐Ÿ  Local & private โ€” runs on your machine over stdio. You bring your own tokens; nothing is proxied through a third party.
  • ๐Ÿชถ Zero install โ€” runs straight from npm via npx.

๐Ÿš€ Quick Start

Interactive setup (Claude Desktop)

npx -y @bitofacoder/omni-mcp-server@latest setup

The wizard asks for your optional tokens (GitHub, Slack), asks whether to enable Agent Mode, and updates your Claude Desktop config for you. Restart Claude Desktop and you're done.

Claude Code

claude mcp add omni -e GITHUB_PERSONAL_ACCESS_TOKEN=your_gh_token -- npx -y @bitofacoder/omni-mcp-server@latest

Manual config (Claude Desktop, Cursor, Windsurf, Codex CLIโ€ฆ)

Add this to your client's MCP config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "omni": {
      "command": "npx",
      "args": ["-y", "@bitofacoder/omni-mcp-server@latest"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_gh_token",
        "SLACK_BOT_TOKEN": "your_slack_token"
      }
    }
  }
}

All env vars are optional โ€” tools that need a missing token simply tell you so.

๐Ÿ› ๏ธ Tools (15)

GroupToolWhat it does
๐Ÿ™ GitHubgithub_search_reposSearch GitHub repositories
github_get_issueGet details of a specific issue
๐ŸŒณ Local Gitgit_statusWorking tree + staging area status
git_diffView local code changes
git_logView commit history
git_commitCommit staged changes with a message
๐Ÿ’ป Systemsystem_read_fileRead a local file
system_list_dirList a directory
system_write_fileโš ๏ธ Write a file (Agent Mode only)
system_execute_commandโš ๏ธ Run a shell command (Agent Mode only)
๐ŸŒ Webweb_fetchFetch any public URL as clean Markdown โ€” no API key needed
๐Ÿง  Memorymemory_storeSave a note/preference across chats
memory_retrieveRetrieve a saved memory
memory_listList everything remembered
๐Ÿ’ฌ Slackslack_send_messageSend a message to a Slack channel

๐Ÿ”’ Agent Mode (opt-in)

system_execute_command and system_write_file let the AI act on your machine โ€” run tests, install packages, edit files. Because that's real power, they are disabled by default and don't even appear in the tool list until you enable them:

"env": {
  "OMNI_AGENT_MODE": "true"
}

Everything else (reading files, git status, web fetch, memory) is read-only or sandboxed to its own data file.

๐Ÿค Contributing

PRs welcome โ€” especially new integrations (Linear, Notion, Jira, Discord) and Agent Mode hardening (allowlists, working-dir scoping). Open an issue first for bigger changes.

If Omni saved you some config wrangling, a โญ helps other people find it.

๐Ÿ“„ License

MIT โ€” see LICENSE.

Installation

Source-derived launch command. Check the maintainerโ€™s required arguments and credentials before running:

bash
npx -y @bitofacoder/omni-mcp-server

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-bitofacoder-omni-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@bitofacoder/omni-mcp-server"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the clientโ€™s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@bitofacoder/omni-mcp-servernpm

Compatible MCP Clients

io.github.bitofacoder/omni-mcp-server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More