Omnigami AI MCP

Name: Omnigami AI MCP
Author: omnigami-ai

by omnigami-aiversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.omnigami-ai/mcp

Install

Overview

Description from the maker (original English)

Find omnigami skills: public catalogue search, install instructions and free-first recommendations.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "omnigami-ai": {
      "command": "npx",
      "args": [
        "-y",
        "@omnigami-ai/mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add omnigami-ai -- npx -y @omnigami-ai/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "omnigami-ai": {
      "command": "npx",
      "args": [
        "-y",
        "@omnigami-ai/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "omnigami-ai": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@omnigami-ai/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account omnigami-ai, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5668 servers in this category
Published to the registry more recently than 100% of the other 5668 servers in this category
Basic checks equal to or better than 100% of the other 5668 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Omnigami AI MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

omnigami MCP

Find an omnigami skill from your agent: search the public catalogue, get its install prompt, or describe the job for a free-first recommendation. Runs locally over stdio. It never buys, installs or generates a deliverable.

Release candidate 0.1.0, not yet on npm. The install lines below work once @omnigami-ai/mcp is published. MIT licensed (LICENSE).

Install — once published

Requires Node 20+ and npm. The package starts with:

npx -y @omnigami-ai/mcp

Claude Desktop: merge this into claude_desktop_config.json through Settings → Developer → Edit Config, then restart Desktop:

"mcpServers": { "omnigami": { "command": "npx", "args": ["-y", "@omnigami-ai/mcp"] } } }

Claude Code: add it to the current project's .mcp.json:

claude mcp add --scope project --transport stdio omnigami -- npx -y @omnigami-ai/mcp

claude mcp list

Cursor: merge the same mcpServers JSON into .cursor/mcp.json in the project, then enable the server in Cursor's MCP settings. For a global setup use ~/.cursor/mcp.json.

If a GUI cannot find npx, use its absolute path. On Windows use "command": "cmd" and "args": ["/c", "npx", "-y", "@omnigami-ai/mcp"]. Add --offline after the package name to disable catalogue requests.

The prototype was exercised in Claude Code and Inspector CLI. Desktop and Cursor configuration follows their official documentation; their GUIs have not been exercised. A skill's own agent support is separate: catalogue results distinguish Claude Code's tested status from other listed agents. Desktop guide, Claude Code configuration, Cursor configuration.

Tools

Tool	Inputs	Result
`search_skills`	`query`, optional `kind` (`film`, `shot`, `images`, `deck`) and boolean `free`	Up to eight matching skills, outputs, USD prices and pages
`get_skill`	`slug`	Inputs, requirements, install prompt, install command and agent platforms
`recommend`	`job`, optional `product_url`	One pick with reasons and a conditional alternative, a free tool, no match, or a clarification

For example, ask your agent: “Find a free launch-video skill for my working web app, wide for our website.” Describe the destination, shapes, input access, budget, theme and owned skills. A general launch defaults to free Product film. Paid picks explain the price and purchase/GitHub access requirements. No bundles are promoted. Two deliverables ask which comes first and name both choices.

Version one uses deterministic English routing. The host should inspect the user's authorized product material and pass a self-contained brief. The server does not inspect product URLs, verify screens or infer business facts. Complex implications and negations still need host judgment. A supplied recording has no verified match while the published catalogue lists no recording input.

Public data and privacy

The server reads fixed public paths on https://omnigami.ai: /llms.txt, each /skills/ /install.md, and the corresponding skill page. It uses the live list for prices and availability and refreshes details on demand. The cache lasts 15 minutes in memory. Requests have a four-second timeout and 1.5 MB limit, reject redirects and send no cookies. Failures fall back to the dated bundled snapshot with an explicit warning; detail failures are labelled separately.

Free-page prompts come from the site's Copy install prompt. Paid pages omit that button, so their public install.md Ask line is wrapped in the site's same prompt format; prompt_source identifies this fallback.

The bundle contains 36 public skills, checked on 2026-11-07. No keys, accounts, analytics or runtime disk cache. Jobs and product URLs are never sent to the site. product_url only fills the returned request. The runtime reads its own installed modules/data, never the user's product repo or credentials. Your host client controls its own model usage and conversation storage.

Develop locally — available now

From this source folder:

npm ci

npm run build npm test npm run check:snapshot npm run check:registry node dist/src/server.mjs --offline

The server waits for MCP messages on stdin. For an unpublished client setup, replace the npx entry with absolute Node and dist/src/server.mjs paths.

check:snapshot compares every bundled skill's price, availability, install command, prompt, inputs and outputs against live public pages. Inside the site workspace it also compiles the real site/src/data/skills.ts, finder helpers and availability helper. Use -- --site /path/to/site explicitly or -- --live for the independent public repository. Network/parse failure fails the check. npm run snapshot refreshes public data; review the diff and rebuild afterward.

CI tests Node 20, 22 and 24 and checks live snapshot freshness. For the clean tarball install plus Inspector CLI smoke test, use Node 24.22.1+:

npm run test:pack

The script uses a temporary clean export, packs and installs its tarball, lists the three tools and calls each once, then removes its temporary files. Inspector 2.14.0 is fetched as a development tool and is absent from the package. The runtime pins @modelcontextprotocol/sdk 1.32.2; the build copies modules and public data into dist without fetching anything.

Release and contact

Releases are published from version tags by the release.yml workflow, with npm provenance and no stored token. The MCP Registry entry is publishing/server.json.

Report bugs at GitHub Issues. For questions or a private report, email hello@omnigami.ai. Include your Node/client versions, the tool and a minimal example; omit private product data.

omnigami is a product of Auberon LLC and is not affiliated with Anthropic.

Omnigami AI MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

omnigami MCP

Install — once published

Tools

Public data and privacy

Develop locally — available now

Release and contact