Omni MCP Server

Omni MCP server exists for a simple reason — assistants are far more useful when they can act on Omni directly instead of describing what you should do. All-in-one MCP server: GitHub, Git, Slack, web fetch, memory, and filesystem. Agent Mode opt-in.

What you get

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.

• 🔒 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

What the assistant can call

Once Omni is connected, these are the calls the assistant has available:

• Group — Tool

Setting it up

@bitofacoder/omni-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 3 environment variables: GITHUB_PERSONAL_ACCESS_TOKEN, SLACK_BOT_TOKEN, OMNI_AGENT_MODE. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Omni's toolset — Group — is a fair guide to whether it matches your workflow. It is maintained by bitofacoder; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the omni mcp server does with a few real requests.