MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Your reading, cited wiki and agent-kept editions in Noeis. Read-only unless you grant more.
Skills that teach the AI this kind of work; they work alongside this one
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
A privacy-first app that strips AI watermarks from content you own.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Noeis. Follow https://mcp.popnx.com/i/atsokolas-noeis.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 16, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Noeis for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "noeis": { "command": "npx", "args": [ "-y", "@noeis/wiki-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Noeis tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"noeis": {
"command": "npx",
"args": [
"-y",
"@noeis/wiki-mcp"
]
}
}
}Use Noeis and tell me what you can do for me, then show me one thing✓ If Claude says it is using Noeis or shows a Noeis tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
NOEIS_TOKEN Noeis agent token. Optional when `noeis connect` has stored one.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Noeis yet
Noeis runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Noeis
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Noeis for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user noeis -- npx -y @noeis/wiki-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Noeis tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user noeis -- npx -y @noeis/wiki-mcpYou should see Noeis listed as connected
Use Noeis and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Noeis or shows a Noeis tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
NOEIS_TOKEN Noeis agent token. Optional when `noeis connect` has stored one.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Noeis for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "noeis": { "command": "npx", "args": [ "-y", "@noeis/wiki-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Noeis tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Noeis and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Noeis or shows a Noeis tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
NOEIS_TOKEN Noeis agent token. Optional when `noeis connect` has stored one.Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Noeis for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "noeis": { "type": "stdio", "command": "npx", "args": [ "-y", "@noeis/wiki-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Noeis tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Noeis and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Noeis or shows a Noeis tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
NOEIS_TOKEN Noeis agent token. Optional when `noeis connect` has stored one.Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user noeis -- npx -y @noeis/wiki-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"noeis": {
"command": "npx",
"args": [
"-y",
"@noeis/wiki-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"noeis": {
"command": "npx",
"args": [
"-y",
"@noeis/wiki-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"noeis": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@noeis/wiki-mcp"
]
}
}
}NOEIS_TOKEN secret envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @noeis/wiki-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 20, 2026
The registry name was verified with the GitHub account atsokolas, which owns the repo
Code last changed 2 days ago
No licence file found in the repo
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/atsokolas-noeis)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed 2 days ago, and the latest version (0.5.1) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Atlassian’s official server lets AI search and manage Jira work and Confluence pages. Connects to Atlassian’s cloud with OAuth sign-in.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| This one Noeis | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Installs on your computer |
| Needs a key | No | No | No | Yes | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 2/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| License | – | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
MCP server for driving a Noeis wiki from external agents.
Settings -> Connected agentsNOEIS_API_URL if you are not using the hosted APIAn edition is a paper you keep for your reader — *This Week in AI*, *Weekend Readings*. Noeis does not write it; it holds it to a shape and files it under a window, and the reader reads it at /editions and saves sources from it into their library.
The shape is the whole contribution. Every item carries a finding (what the source says) and a boundary (what would limit it). An item without a boundary is refused by name, so you can fix it and file again — that rule is the difference between an edition and a newsletter. A section nobody filled is printed rather than dropped.
An item can also carry what a reader weighs it by: a plain line, a why (a sentence on why you picked it for this reader), the passage it quotes (checked word for word when the reader saves the source, and never shown as a quotation until it holds), its sourceKind, a confidence, and up to three figures, each of which must appear in the finding, passage or note. An issue can carry a plain headline and followUps saying what became of the last issue's watch list.
create_edition file or replace an edition for a window
list_editions what is already on the stand — check before filing, so you continue a run rather than starting a second one get_edition one edition in full, including which sources the reader took
Filing twice for the same window replaces your own edition rather than printing a second copy of Tuesday, and sources the reader has already saved survive the rewrite — those are theirs, not yours.
For testing against unreleased tools, point the runtime at this directory instead of the published package. The server is a plain stdio process:
{
"servers": { "noeis-wiki-dev": { "transport": "stdio", "command": "node", "args": ["/absolute/path/to/note-taker-3/packages/wiki-mcp/bin/noeis-wiki-mcp"], "env": { "NOEIS_CONFIG_DIR": "/Users/you/.config/noeis" } } } }
NOEIS_API_URL is optional and defaults to the hosted API, so a checkout talks to the same Noeis the published package does.
Install the CLI and connect the runtime you use:
npm i -g @noeis/noeis-cli
noeis connect hermes --scope read
noeis connect openclaw --scope read
noeis connect codex --scope read
The CLI opens Noeis for human approval, verifies grant/workspace metadata, and writes runtime MCP config. The generated config calls noeis mcp; it reads the credential from the Noeis CLI config instead of copying it into every runtime. Reload the runtime and call connection_info there before claiming its tools are loaded. Use --scope read-write only after the human explicitly chooses the broader grant.
Public package status: @noeis/noeis-cli and @noeis/wiki-mcp are published on npm.
Noeis also supports task links:
https://www.noeis.io/a/run/at_...
These links package a specific task, target, runtime, and permission set. Opening the link lets the user dispatch the task into the normal Noeis handoff queue. If the requested runtime is not connected, Noeis shows the matching noeis connect command before dispatch.
noeis mcp
Both noeis mcp and noeis-wiki-mcp read the token and API URL from NOEIS_TOKEN/NOEIS_API_URL when set, and otherwise from config.json in NOEIS_CONFIG_DIR (default ~/.config/noeis) — the file noeis login writes. NOEIS_API_URL defaults to https://note-taker-3-unrg.onrender.com.
The MCP surface includes wiki tools plus Library/Think tools for saved articles, highlights, concepts, and questions. Agents can search highlights, fetch articles, create article highlights, file articles into folders and keep them on the Shelf, create or update Think questions, update concepts, pin highlights to concepts, and create or edit wiki pages.
Noeis also offers a hosted Streamable HTTP endpoint for clients that cannot launch a local stdio process:
https://note-taker-3-unrg.onrender.com/mcp
Use a dedicated connected-agent token as a Bearer credential. Create it in Noeis under Settings -> Connected agents, begin with the read scope, and give it a short expiry and daily quota. A token with agent-write can perform only the write operations already permitted by the Noeis API; human-only actions remain unavailable. MCP connection checks do not consume quota, while each tool action is counted by the underlying API exactly once.
The endpoint accepts standard JSON-RPC POST requests over Streamable HTTP. It has no cookie session and does not support OAuth yet. Check deployment readiness without a token at:
https://note-taker-3-unrg.onrender.com/mcp/health
For cron jobs, shell scripts, or custom runtimes that do not speak MCP, install the sibling CLI:
npm i -g @noeis/noeis-cli
noeis connect hermes --scope read noeis ingest https://example.com/research noeis pages list
The CLI uses the same Connected agents token and API routes as this MCP server.
Register the server once with claude mcp add. --scope user makes it available in every project; leave it off to add it to the current project only.
Through the CLI, which reads the token noeis login or noeis connect saved:
claude mcp add --scope user noeis -- noeis mcp
Or through the hosted endpoint, with no local install (use a read token):
claude mcp add --scope user --transport http noeis \
https://note-taker-3-unrg.onrender.com/mcp \ --header "Authorization: Bearer ntk_at_..."
Run claude mcp list to see it connected, then ask Claude something like "what have I read about sparse models?". It will call recall and can open any hit with read.
Add this to ~/.codex/config.toml:
[mcp_servers.noeis-wiki]
command = "noeis" args = ["mcp"]
Restart Codex and confirm the noeis-wiki MCP server is connected.
Add this server to your OpenCode MCP config:
{
"mcp": { "noeis-wiki": { "command": "noeis", "args": ["mcp"] } } }
Add a stdio MCP server named noeis-wiki:
{
"servers": { "noeis-wiki": { "transport": "stdio", "command": "noeis", "args": ["mcp"] } } }
For local development:
{
"NOEIS_API_URL": "http://localhost:5500" }
Both lists below are the complete tool surface, checked against toolDefinitions by test/server.test.js — a tool added without a line here fails the suite.
An agent is shown the core tools unless its runtime asks for more, because every listed tool costs context on each turn. Core is twelve tools: recall, read, connection_info, list_pages, get_page_markdown, create_page, create_article, create_highlight, create_notebook_entry, update_notebook_entry, list_edition_profiles and file_edition_items. Every other tool below stays callable and is listed when you ask for its toolset: library, think, wiki, editions, work or all.
noeis mcp --toolsets=wiki,library # local, or NOEIS_TOOLSETS=wiki,library
https:// /mcp?toolsets=wiki # hosted
Work tools are listed by themselves for a connection approved with --work.
Start with recall. It asks everything the reader keeps (saved articles and their highlights with margin notes, Think notes, concepts, held views, wiki pages and Editions) with the same retrieval the in-app partner uses, so a plain question like "what have I written about hiring" finds the reader's own notes. Each hit carries a passage, an id, a link and the tool that opens it, usually read. Read tools return normalized JSON:
connection_inforecallreadget_profilelist_edition_profileslist_editionsget_editionlist_pageslist_judgment_pagesget_pageget_page_markdownsearch_pagesget_schemaget_briefinglist_sourceslist_backlinkslist_activitylist_revisionslist_source_eventsget_ingest_runlist_proposalslist_autolinksget_lint_runlist_folderssearch_articlesget_articlelist_article_highlightssearch_highlightsget_highlightget_source_thought_contextget_research_candidatelist_questionsget_questionlist_conceptsget_conceptlist_concept_noteslist_notebook_entriesget_notebook_entrylist_notebook_foldersWrite tools require a token with the agent-write scope. Read-only tokens receive 403 from the Noeis API on these calls:
create_pageupdate_pagecreate_judgment_pageupdate_judgment_pagearchive_pagecreate_editionconfigure_editionfile_edition_itemsingest_sourcedraft_pageask_pagepromote_answerlint_wikiapply_autolinkadd_sourceremove_sourceupdate_schemaaccept_proposaldismiss_proposalmerge_proposalcreate_articlecreate_folderfile_articlekeep_articleplace_articledelete_articledelete_foldernest_folderset_folder_feedcreate_highlightupdate_highlightsave_source_thoughtdelete_highlightwrite_concept_noteupdate_concept_notedelete_concept_notecreate_notebook_entryupdate_notebook_entrydelete_notebook_entryadd_highlight_to_notebook_entrycreate_notebook_folderdelete_notebook_foldercreate_questionupdate_questionupdate_conceptpin_highlight_to_conceptWork is the reader's private work notebook, and it stays shut to every connection that was not approved with noeis connect … --work. With it, the connection's own read or read-write access applies to Work too, so the last four need read-write:
list_workget_work_notecreate_work_noteupdate_work_notecreate_work_folderupdate_work_folderEvery Work change names the revision it read, so an agent never saves over what the reader typed since. ChatGPT connections never see these tools.
delete_article, delete_highlight, delete_notebook_entry and delete_concept_note are the tools with no undo. Each says so in its description and each expects the reader to have been asked first. delete_folder and delete_notebook_folder are not among them: a Library folder must be empty before it will go, and a Notebook folder unfiles its notes rather than taking them with it.
Two packages, published in order, because the CLI depends on this one:
cd packages/wiki-mcp && npm publish --access public
cd ../cli && npm publish --access public
Bump both versions first, and bump the CLI's @noeis/wiki-mcp range to match the version being published. That range is the thing to watch: it sat at ^0.1.2 while this package moved to 0.3.0, and a caret on a 0.x version pins the minor — so the CLI could never install what had been written, and every agent connected through it kept the tools as they stood at 0.1.2.
Verify the artifact rather than the working tree, since files decides what actually ships:
npm pack --pack-destination /tmp
cd $(mktemp -d) && npm init -y && npm install /tmp/noeis-wiki-mcp- .tgz node -e "import('@noeis/wiki-mcp').then(m => console.log(m.toolDefinitions.length, 'tools'))"
wiki_schema: fetches the current Noeis wiki schema markdown and returns it as prompt context.