Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Files what you learn into a personal wiki and quizzes you before you forget it.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://my.eigma.app/api/mcpRun this in your terminal
claude mcp add --transport http eigma https://my.eigma.app/api/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"eigma": {
"url": "https://my.eigma.app/api/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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"eigma": {
"type": "http",
"url": "https://my.eigma.app/api/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.
ChatGPT connects only to servers on the internet:
https://my.eigma.app/api/mcpMenu names can differ slightly by plan and over time.
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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 6, 2026
The registry name was verified against the domain eigma.app (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
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.
Every tool description, input schema and shared extraction rule from the [Eigma](https://eigma.app) MCP connector, plus a runnable example server. The text a model reads, not the service behind it.
Eigma turns your conversations with an AI assistant into a personal wiki you actually remember.
An assistant can explain something well, and almost none of it survives you closing the tab. A week later you remember that you understood the thing, but not the thing itself, and what you do recall is often subtly wrong. Eigma saves the part worth keeping, files it under the right chapter, and asks you about it again before you forget.
Your knowledge as a map. Each page is a point of light, and its brightness shows how well you still remember it rather than how recently you opened it. Pages you have internalized stay bright; pages you are forgetting go dim.
Eigma connects over MCP, so it works inside the assistant you already use — ChatGPT, Claude, and coding agents like Claude Code and Codex. Your assistant does the thinking; Eigma keeps the result. The app is available in English, 中文 and Deutsch. → [eigma.app](https://eigma.app)
Setup takes about a minute, and you do it once per assistant.
Create your Eigma account first, at eigma.app. Partway through, you will be
asked to sign in, and your pages will go to whichever account you sign in with.
ChatGPT — its own address
https://my.eigma.app/api/mcp-chatgpt
Eigma and paste the address into the server URL fieldClaude, Claude Code and Codex — one shared address
https://my.eigma.app/api/mcp
Claude: Customize → Connectors → + → Add custom connector, paste the address, Add, then sign in.
⚠️ Then open a chat, click the + at the bottom left, choose Connectors, and switch Eigma on. Claude uses only the connectors that are switched on in that particular conversation. If Eigma looks connected but nothing happens, this is almost always why.
Claude Code:
claude mcp add --transport http --scope user eigma https://my.eigma.app/api/mcp
claude mcp login eigma
Codex:
codex mcp add eigma --url https://my.eigma.app/api/mcp
codex mcp login eigma
The login command opens a browser window so you can sign in and approve. Afterwards, run claude mcp list (or /mcp in a chat) to confirm the connection: worth doing, because a failed connection fails silently.
Then, in any chat: "organize this into Eigma". Your assistant turns the conversation into pages, files each page under the right chapter, attaches a few questions to it, and sends the result to your review inbox.
Screenshots and troubleshooting: [eigma.app/docs](https://eigma.app/docs).
Menu paths verified against the ChatGPT and Claude apps in September 2026.
Eight tools, five of them read-only. The read-only tools are what make your wiki usable as context inside the chat you are already in, rather than as something you have to open separately.
| Say something like | What happens |
|---|---|
| *"What do I have on transformers?"* | Matches across scripts, using CJK bigrams, German compound splitting and each page's aliases, so a page filed in English stays findable in the language you ask in |
| *"Use my notes on Kubernetes to answer this"* | Reads the page and answers from it |
| *"Check this page against real sources"* | Re-reads it, tests the claims, proposes a rewrite with inline footnotes and a References section |
| *"These two pages are about the same thing, merge them"* | Merges the two: the absorbed page's body is appended to the page you keep. Useful against the near-duplicates a growing wiki accumulates |
| *"Go through my Cloud chapter and tell me what is badly organised"* | Reads the chapter, then proposes all the moves and renames as a single changeset you can review in one pass |
| *"These questions are weak, write better ones"* | Adds, replaces or removes specific quiz questions |
| *"What should I review today?"* | Lists the pages you are closest to forgetting, rather than the ones you opened most recently |
| *"Translate my page on embeddings into German"* | Sends a translated copy to your inbox; the original page is untouched |
Everything that changes the wiki arrives as a reviewable changeset: a list of operations you approve or drop one by one. An assistant deciding that a change is a good idea is never enough to apply it.
This repository holds everything a model reads when it talks to Eigma: the tool descriptions and the input schemas. The connector itself is a hosted MCP server with OAuth, and that part is not here.
Take what is useful: vendor src/rules.ts and compose your own descriptions from it, copy the ingestSchema.ts pattern, or fork example/server.ts as a starting point.
npm install
npm test npm run example # boots the example server and prints its address
| `src/toolSpec.ts` | Descriptions for the six read tools (browse, search, read a page, resolve drafts, read memory state, translate), plus the outline and search helpers behind them. |
| `src/writeSpec.ts` | Descriptions for the two write tools, each in a full and a slim variant. These are the tools that change your wiki, so their wording matters most. |
| `src/rules.ts` | The 20 shared extraction rules that every tool description and the server instructions are composed from. Change a rule here and the change takes effect in every channel at once. |
| `src/ingestSchema.ts` | The save tool's input schema. |
| `src/changeOpsSchema.ts` | The edit tool's operation vocabulary, typed. |
| `src/skill.ts` | The connector's skill and its server instructions: when to act, what order to call tools in, how not to loop. |
| `src/renderSurface.ts` | A way to drive your own handler and get back the exact bytes tools/list puts on the wire. |
| `src/tools.ts` | The ordered tool registry: reads before writes, plus the per-host type that decides which variant of each description is used. |
| `src/textNormalize.ts` | The single text normalizer that every cross-language comparison in this repository uses. |
| `skill/eigma-filing/` | The generated Skill package, for hosts that load skills. Rebuild with npm run build:skill. |
| `example/server.ts` | A working MCP server over a Map. No database, no auth, ~330 lines; six of the eight tools wired end to end. |
MIT © Eigma. The Eigma name, logo and screenshots are not covered by the MIT grant.