npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@noeis/cli

v0.1.1

Published

Command-line client for scripting a Noeis wiki.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

atsokolasatsokolas

Keywords

noeiswikicliagent

Readme

@noeis/cli

Command-line client for scripting a Noeis wiki without an MCP-speaking agent.

Install

Current internal build:

cd ~/Documents/GitHub/note-taker-3-1
npm i -g ./packages/cli

Public package status: @noeis/cli is not published on npm yet. After publish, this becomes npm i -g @noeis/cli.

Connect an agent

The normal setup path opens Noeis in your browser, asks you to approve the local agent, writes the CLI token, writes the runtime MCP config, and runs an access check:

noeis connect hermes
# or
noeis connect openclaw
# or
noeis connect codex

Supported runtime names: claude-code, codex, hermes, openclaw, and opencode.

The generated runtime MCP config calls noeis mcp. The raw token stays in one place: the Noeis CLI config, normally ~/.config/noeis/config.json. Generated MCP configs should not copy NOEIS_TOKEN.

For local/self-hosted API targets, pass both URLs:

noeis connect hermes --api-url http://localhost:5500 --app-url http://localhost:3000

If the browser cannot open automatically:

noeis connect hermes --no-browser

Agent launch links

Noeis can create browser links that feed a task to a connected runtime:

https://www.noeis.io/a/run/at_...

Open the link, review the task, then dispatch it to OpenClaw, Hermes, Codex, or another connected runtime. If the runtime is not connected yet, Noeis shows the exact connect command to run and preserves the task link.

Manual auth

You can still create a Connected agents token in Noeis Settings and paste it manually:

noeis login --token ntk_at_... --api-url http://localhost:5500

You can also skip stored config and use environment variables:

NOEIS_TOKEN=ntk_at_... NOEIS_API_URL=https://api.noeis.io noeis pages list

Manual environment variables are useful for scripts. Runtime MCP configs should prefer noeis mcp so secrets remain centralized.

Commands

noeis pages list
noeis mcp --help
noeis pages get <id> --json
noeis ingest https://example.com/research
noeis ingest ./source.txt --title "Source title"
noeis draft <pageId>
noeis ask <pageId> "What changed?"
noeis schema show
noeis schema edit
noeis log --since 1d

Write commands require a Connected agents token with agent-write.