Your notes, for your AI agent.
Let the agent you already use read, search and write your Neptunion notes: pages, databases, LaTeX papers, meeting transcripts. One step, on your own computer. You choose what it may do, and you see it work.
Claude Code
Have Neptunion open, with the space you want Claude to work in.
-
Add Neptunion's plugin.
In Claude Code, type these two lines. The plugin connects Claude to Neptunion and teaches it how your pages work.
/plugin marketplace add SynomyCloud/neptunion-agent /plugin install neptunion@neptunion
Or only the connection, from a terminal:
claude mcp add --transport http -s user neptunion http://127.0.0.1:51741/mcp -
Allow it, once.
Type /mcp, choose neptunion and Authenticate. Your browser opens a page from Neptunion itself: choose how far Claude reaches and what it may do, and press Allow.
-
Ask.
“Summarise every meeting that has no summary yet.” “Put last week's action items into a page called Week 44.” “Add a Due column to my Tasks database and fill it in.” “Write the introduction of my paper in LaTeX.”
For the meetings there is a command of its own:
/neptunion:summarize-meetings.
Codex
Have Neptunion open, with the space you want Codex to work in. In a terminal:
-
Add Neptunion.
codex mcp add neptunion --url http://127.0.0.1:51741/mcp
-
Allow it, once.
codex mcp login neptunion
Your browser opens a page from Neptunion itself: choose how far Codex reaches and what it may do, and press Allow.
-
Teach it how Neptunion works (optional).
Neptunion's skill tells Codex how your pages, databases and LaTeX projects work, so it changes them well:
codex plugin marketplace add SynomyCloud/neptunion-agent
Claude Desktop
Claude Desktop's own connectors reach servers on the internet, and Neptunion is on your computer, so it goes through a small bridge. You need Node.js.
-
Make a key for it in Neptunion.
In Neptunion: Settings → API, then New key for it… beside Claude Desktop. Choose the spaces it reaches and what it may do, and press Create key. Neptunion shows the lines for Claude's settings file, with the key already in them. Copy them.
-
Put them in Claude's settings file.
Quit Claude Desktop, open its settings file (in Claude Desktop: Settings → Developer → Edit Config shows it), put the lines in (beside any servers already in
mcpServers), save, and open Claude Desktop again. They look like this:{ "mcpServers": { "neptunion": { "command": "npx", "args": ["-y", "mcp-remote", "http://127.0.0.1:51741/mcp", "--header", "Authorization:${NEPTUNION_AUTH}"], "env": { "NEPTUNION_AUTH": "Bearer synomy_…" } } } }
Without a key, leave out --header and env: your browser then opens a page from Neptunion where you press Allow. Claude Desktop starts the bridge twice, for chat and for Code, so it asks twice and makes two keys; one key from Settings does for both.
Gemini CLI
Have Neptunion open, with the space you want Gemini to work in. In a terminal:
-
Add Neptunion's extension.
It connects Gemini to Neptunion and brings the skill that tells it how your pages work.
gemini extensions install https://github.com/SynomyCloud/neptunion-agent
-
Allow it, once.
The first time Gemini uses Neptunion, your browser opens a page from Neptunion itself: choose how far it reaches and what it may do, and press Allow.
Cursor
Have Neptunion open, with the space you want Cursor to work in.
-
Add Neptunion.
Add to CursorOr put it in
~/.cursor/mcp.jsonyourself:{ "mcpServers": { "neptunion": { "url": "http://127.0.0.1:51741/mcp" } } } -
Allow it, once.
In Settings → MCP, press Connect beside neptunion. Your browser opens a page from Neptunion itself: choose what Cursor may do, and press Allow.
-
Teach it how Neptunion works (optional).
Copy the skill folder
plugins/neptunion/skills/neptunion/from the agent kit into~/.agents/skills/, or let one line do it (step 3 under Others).
VS Code
For GitHub Copilot's agent mode. Have Neptunion open, with the space you want it to work in.
-
Add Neptunion.
Add to VS CodeOr from a terminal:
code --add-mcp '{"name":"neptunion","type":"http","url":"http://127.0.0.1:51741/mcp"}' -
Allow it, once.
When VS Code asks to sign in to neptunion, say yes. Your browser opens a page from Neptunion itself: choose what the agent may do, and press Allow.
-
Teach it how Neptunion works (optional).
Copy the skill folder
plugins/neptunion/skills/neptunion/from the agent kit into~/.agents/skills/.
Any other agent
Neptunion speaks the Model Context Protocol, so any agent that can add an MCP server can use it. Give it this address:
http://127.0.0.1:51741/mcp
-
If your agent can sign in to a server
OpenCode, Zed, Cline and Devin can. Add the address with no key, sign in when asked, and press Allow on the page Neptunion opens in your browser.
-
If it needs a key
In Neptunion, open Settings → API, press New key, choose what it may do, and copy the key. Give it to your agent as a header:
Authorization: Bearer synomy_…
Antigravity, for example, in
~/.gemini/config/mcp_config.json:{ "mcpServers": { "neptunion": { "serverUrl": "http://127.0.0.1:51741/mcp", "headers": { "Authorization": "Bearer synomy_…" } } } } -
Teach it how Neptunion works
Agents that read skills (Codex, Cursor, VS Code, OpenCode, Antigravity) find Neptunion's in
~/.agents/skills. One line puts it there, and adds Neptunion to Claude Code and Codex if you have them:curl -fsSL https://raw.githubusercontent.com/SynomyCloud/neptunion-agent/main/install.sh | sh
What your agent can do
- Find and read any page it may reach, search your notes, and follow what changes.
- Write: make pages, change words in them without disturbing the rest, add pictures, move pages around.
- Fill databases: add rows, set their values, add and rename columns.
- Write LaTeX and HTML projects: make one from a template and write its files. Neptunion compiles it while you have it open.
- Summarise your meetings: find every meeting without a summary, read its transcript, and write the summary into it, with each point linked to the moment it was said. Let them pile up and ask once.
- Undo its own mistakes: what it deletes goes to the trash, and every page keeps its history.
You see it work
While your agent works, it has a pointer in your window, like a friend editing the same page. It goes to what the agent reads, presses where it writes, and the words it changed light up for a moment. The pointer carries the agent's name and its own colours, so you always know it is an AI and not a person.
You stay in charge
Your notes never leave your computer for this: the agent talks to Neptunion on your own machine, at 127.0.0.1, and only while Neptunion runs. When it asks to connect, you choose how far it reaches: every space, only the spaces you tick, one page and what is inside it, or only meeting transcripts, and whether it may only read, also change, or also delete. Every agent you let in is listed in Settings → API under its own name, and removing it there stops it at once.
If something does not work
- The agent cannot reach Neptunion. Neptunion has to be running. If you chose another port in Settings → API, use that number instead of 51741 (the plugin and
install.shread it fromNEPTUNION_PORT). - It cannot find a space. An agent let into every space reaches each space Neptunion has opened on this computer, so open it once. One you let into chosen spaces keeps to those: tick another for it in Settings → API (Edit beside it).
- It may not do something. Remove it in Settings → API and connect it again with more access.
- For your own scripts, the full guide to Neptunion's API is served by the app itself at 127.0.0.1:51741 while it runs (Settings → API → Steps for every agent).