Omni Mcp Server

io.github.bitofacoderPublished by GitHub account bitofacoderv1.1.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A single local MCP server bundling GitHub, local Git, Slack, web fetch, memory and filesystem tools, with shell execution and file writes off by default.

What you can do
Search GitHub repositories and read issue details, with an optional GitHub token for the GitHub tools (optional). Inspect local Git state: status, diff, log, and commit staged changes. Read local files and list directories; write files and run shell commands only when Agent Mode is enabled. Fetch a public URL as clean Markdown without an API key. Store, retrieve and list persistent memory notes across chats. Send a message to a Slack channel when a Slack bot token is configured.
When to use it
Useful when you want one config entry for everyday developer work — checking repos and issues, reviewing local changes, reading files, fetching web pages and keeping notes — instead of installing several separate servers. Agent Mode is for when you explicitly want the assistant to edit files or run commands on your machine.
Requirements
Runs locally over stdio via npx from the npm package, so Node.js is needed. Optional secrets: GITHUB_PERSONAL_ACCESS_TOKEN for the GitHub tools and SLACK_BOT_TOKEN for slack_send_message; tools needing a missing token report it. OMNI_AGENT_MODE set to 'true' enables shell execution and file writes. Network access is needed for GitHub, Slack and web fetch.
Before you install
Agent Mode (OMNI_AGENT_MODE=true) exposes system_write_file and system_execute_command, letting the assistant write files and run arbitrary shell commands on your machine; leave it off unless needed. git_commit and slack_send_message change data or send messages. GITHUB_PERSONAL_ACCESS_TOKEN and SLACK_BOT_TOKEN are secrets stored in the client config; scope them narrowly.

Installation

In SourceWeft

  1. Open Omni Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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)

bash
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

bash
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):

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:

json
"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.

Source: README.md at commit 5e6a756

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts