# EndNote for Word
[繁體中文](README-zhTW.md)
EndNote for Word is an installable AI citation-management toolkit for Microsoft Word: a Claude Code, Claude Desktop, Codex, and ChatGPT Desktop skill/plugin plus MCP server that finds DOI-verified research papers, exports and imports RIS into EndNote libraries, and creates genuine EndNote Cite While You Write (CWYW) IEEE citations and bibliographies.
## What this tool does
- Guides AI Agents to find peer-reviewed papers, verify metadata and DOI, export EndNote-compatible RIS, and import it through EndNote Direct Export. With EndNote fully closed, a missing target library can be created from a verified empty library template, and a DOCX with no EndNote citations and no named library gets `<document stem>.enl` beside it.
- Replaces `{{CITE:id}}` markers in a DOCX with real CWYW citations, so every citation becomes an `ADDIN EN.CITE` field carrying an EndNote traveling library, and the bibliography becomes an `ADDIN EN.REFLIST` field.
- Never types citation text, never fabricates field codes in OOXML, and never passes off a plain-text reference list as a real bibliography.
- Reads your `.enl` library through a read-only snapshot so an agent can search for references and confirm every record number before Word is ever opened. RIS import is the sole library-writing action and EndNote itself performs it.
- Uses IEEE by default, requires a DOI for every cited reference, verifies each DOI through doi.org, and rejects doubled resolver prefixes.
- Supports both IEEE Default Format `[x]` and EndNote's Display as Author (Year), which produces forms such as `Author et al. [x]` for narrative prose.
- Preserves output-style-owned narrative punctuation. Forms such as `Hernandez, et al. [1]` are normal EndNote output and are not downgraded to typed authors or Default Format merely to remove a comma.
- Pre-checks the manifest against the library and against the installed output styles, because an unknown record number or an unknown style name makes EndNote open a modal dialog that blocks automation until the process is killed.
- Keeps Word hidden and starts EndNote with a hidden window when the bridge needs to launch it.
- Switches the document output style programmatically and rebuilds the bibliography, with no dialog.
- Validates the finished document structurally and reports counts, style, and the libraries recorded in the document.
- Exports and imports RIS, then reports before/after live-reference counts so the agent can re-query EndNote-assigned record numbers.
## Requirements
- Windows 10 or 11.
- Microsoft Word desktop with COM automation.
- Desktop **EndNote** for Windows with the **Cite While You Write** Word add-in installed and enabled. This is a hard prerequisite: without the CWYW add-in there is no supported way to produce native citation fields, and the tool refuses to fake them.
- Python 3 on `PATH`.
- PowerShell 7 as `pwsh.exe`, or Windows PowerShell 5.1 as `powershell.exe`.
- HTTPS access to `doi.org` for the mandatory pre-citation DOI check.
This project is developed and verified against **EndNote 21** with the 64-bit CWYW add-in (`EndNote.WordAddin.Connect`) and its global Word template `EndNote Cwyw.dotm`. The EndNote executable, the styles directory, and the CWYW template are discovered from the registry and from the installation directories at run time, newest version first, so no version number is hardcoded.
EndNote and Microsoft Office are proprietary products and are not distributed by this repository. The EndNote **web** or **online** plugin is not a substitute for the desktop CWYW add-in.
## Terminal compatibility
The bridge is a single PowerShell script written for both PowerShell 7 and Windows PowerShell 5.1. Four terminals are supported.
| Active terminal | Required action |
|---|---|
| PowerShell 7+ | Run the commands directly with `pwsh.exe`. |
| Windows PowerShell 5.1 | Supported. Run with `powershell.exe`, but prefer `pwsh.exe` when it is installed. Without `pwsh.exe`, the first call other than `probe`, `list-styles` or `validate` installs PowerShell 7 per user through winget (no administrator rights), and the result says so; read-only calls made before that announce it; set `ENDNOTE_WORD_AUTO_INSTALL_PWSH=0` to opt out. The MCP registration commands below launch the server with `powershell.exe` so it also starts before PowerShell 7 exists. |
| Bash on Windows, including Git Bash | Invoke Windows `pwsh.exe`, and fall back to `powershell.exe`. |
| CMD | Invoke `pwsh.exe` with the same arguments, and fall back to `powershell.exe`. |
From WSL Bash, invoke the Windows-side executable. Linux `pwsh` cannot automate Windows Word COM. If neither `pwsh.exe` nor `powershell.exe` is available, stop and install PowerShell rather than silently downgrading. See the [PowerShell installation guide](https://learn.microsoft.com/powershell/scripting/install/installing-powershell-on-windows).
The following command works from PowerShell 7, Windows PowerShell 5.1, Git Bash, and CMD:
```console
pwsh.exe -NoProfile -ExecutionPolicy Bypass -File scripts/endnote-word.ps1 -Action probe
```
## Install with an AI agent
If you want to use EndNote for Word in Claude Code, Claude Desktop, Codex, or ChatGPT Desktop, paste the following prompt. The agent will configure it for the current environment:
```text
Install or upgrade the EndNote for Word toolkit from https://github.com/felimet/endnote-for-word. Detect my available terminal and use PowerShell 7, Windows PowerShell 5.1, Bash on Windows including Git Bash, or CMD; prefer pwsh.exe when it exists and fall back to powershell.exe. From WSL Bash, invoke the Windows-side executable rather than Linux pwsh. If neither is available, stop and tell me to install PowerShell using https://learn.microsoft.com/powershell/scripting/install/installing-powershell-on-windows. Verify Microsoft Word desktop plus desktop EndNote with the Cite While You Write add-in, install the portable skill, register the local stdio MCP server, run the probe and the repository tests, preserve existing agent configuration, and report every changed file. Do not claim success unless the probe reports cwyw_macro_callable true and validation returns ok: true.
```
If you have no target library yet, fully close EndNote and provide an empty `.enl` library that the Agent may clone as a template, as shown in the [quick test prompt](#quick-test-prompt). Ask the Agent to register it with `configure_endnote_defaults` once; afterwards a DOCX without EndNote citations needs no library path, because its library is created as `<document stem>.enl` beside it. Otherwise, provide the DOCX and target `.enl` paths directly. Tell the Agent your preferred EndNote output style, for example `IEEE` or `APA 7th` (`APA 7`). If you omit it, IEEE is used. The Agent must confirm that the style is installed before editing Word and must not silently substitute another style.
Platform-specific skill locations and MCP configuration are documented in the [installation matrix](skills/endnote-for-word/references/installation-matrix.md).
## Add the skill and MCP to each agent
Replace `<REPO_ROOT>` with the absolute local checkout path. Preserve existing MCP entries when editing configuration files.
### Codex
Install the plugin from this repository's marketplace. The plugin carries the skill and the MCP server, starts the server from its installed folder, sets a 1860 s tool limit above the server's own 1800 s render watchdog, and forwards the `ENDNOTE_*` settings plus the Common Files variables the CWYW template lookup needs:
```console
codex plugin marketplace add felimet/endnote-for-word
codex plugin add endnote-for-word@endnote-for-word
```
To upgrade, run `codex plugin marketplace upgrade endnote-for-word` and then the `codex plugin add` command again. Restart Codex after installing or upgrading.
To register the parts by hand instead, copy `skills/endnote-for-word` to `%USERPROFILE%\.codex\skills\endnote-for-word` or `%USERPROFILE%\.agents\skills\endnote-for-word`, then register the server:
```console
codex mcp add endnote-for-word -- powershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "<REPO_ROOT>\scripts\run-mcp.ps1"
codex mcp get endnote-for-word
```
Use the plugin or the hand registration, not both: a server registered with `codex mcp add` under the same name takes precedence over the plugin's server.
### Claude Code
Install the plugin from this repository's marketplace:
```console
claude plugin marketplace add felimet/endnote-for-word
claude plugin install endnote-for-word@endnote-for-word
```
To upgrade, run `claude plugin marketplace update endnote-for-word` and `claude plugin update endnote-for-word@endnote-for-word`.
To register the parts by hand instead, copy `skills/endnote-for-word` to `%USERPROFILE%\.claude\skills\endnote-for-word`, then register the server:
```console
claude mcp add --scope user endnote-for-word -- powershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "<REPO_ROOT>\scripts\run-mcp.ps1"
claude mcp get endnote-for-word
```
Use the plugin or the hand registration, not both, or Claude Code loads two servers and two skills. Restart Claude Code after installing or upgrading.
### Claude Desktop
Upload `dist/endnote-for-word.skill` from **Customize > Skills**. Then merge this server into `%APPDATA%\Claude\claude_desktop_config.json` and restart Claude Desktop:
```json
{
"mcpServers": {
"endnote-for-word": {
"command": "powershell.exe",
"args": ["-NoLogo", "-NoProfile", "-NonInteractive", "-ExecutionPolicy", "Bypass", "-File", "<REPO_ROOT>\\scripts\\run-mcp.ps1"]
}
}
}
```
See Anthropic's [skill upload instructions](https://support.claude.com/en/articles/12512180-use-skills-in-claude) and [local MCP setup guide](https://modelcontextprotocol.io/docs/develop/connect-local-servers).
### ChatGPT Desktop
If **Plugins** is available for the account or workspace, install or enable the packaged capability through the supported [ChatGPT plugin workflow](https://help.openai.com/en/articles/20001256). ChatGPT Desktop does not automatically discover this local repository. OpenAI's current full-MCP documentation applies to ChatGPT web; do not assume the desktop app has the same developer-mode surface unless it is visible for the account.
ChatGPT cannot connect directly to the bundled local stdio MCP command. It requires a remote MCP endpoint or a [Secure MCP Tunnel](https://help.openai.com/en/articles/12584461-developer-mode-and-full-mcp-connectors-in-chatgpt-beta), with Developer mode or Apps enabled as allowed by the account or workspace. Because EndNote and Word automation must execute on the interactive Windows desktop, the endpoint or tunnel must route execution to that Windows host. This repository currently ships only the local stdio server.
## Workflow
1. **Probe.** Confirm Word COM, the EndNote executable, the CWYW add-in registration, the loaded CWYW template, and that a CWYW macro is callable. The macro check runs on a throwaway empty document so it cannot touch your files.
2. **Choose a style.** List the installed `.ens` output styles and pick an exact name. A style name that does not resolve to an installed file makes EndNote open a modal dialog and hangs the run.
3. **Find the references.** Search the `.enl` library read-only and collect the record numbers, first-author surnames, years, and bare DOIs.
4. **Write the manifest.** One entry per citation, each with a unique marker and an explicit display decision. Use `author-year` only when the citation is a grammatical part of the sentence; use `default` for claim support and merged citations.
5. **Pre-check.** Verify every record exists, is live, matches surname, year, and DOI, stores a bare DOI, and resolves successfully through doi.org.
6. **Render silently.** The bridge keeps Word hidden, starts EndNote hidden when needed, creates native citation fields, applies `ENAuthorYearFormat` only where requested, and saves atomically.
7. **Validate.** Re-open the result read-only and run every gate below.
Prepare markers in your DOCX first, for example:
```text
Automated lameness scoring is now standard {{CITE:thomsen2023}}.
Two independent trials agree {{CITE:merged}}.
```
## Manifest contract
See [`examples/example-manifest.json`](examples/example-manifest.json) for a complete file. Its `library.path` is a placeholder, so point it at your own `.enl` library before running it, otherwise the manifest fails the `library.path` existence check.
```jsonc
{
"schema_version": 1,
"library": { "path": "C:\\EndNoteLibraries\\ExampleLibrary.enl" },
"style": "IEEE",
"citations": [
{
"id": "thomsen2023",
"marker": "{{CITE:thomsen2023}}",
"targets": [ { "rec_number": 1, "author": "Thomsen", "year": 2023, "doi": "10.0000/fixture.0001" } ],
"display": "default",
"pages": "45-46"
}
],
"bibliography": { "expected": true }
}
```
| Rule | Requirement |
|---|---|
| `schema_version` | Must be `1`. |
| `citations` | Non-empty array. Unknown top-level and per-citation keys are rejected. |
| `id` | Matches `^[A-Za-z][A-Za-z0-9_-]*$` and is globally unique. |
| `marker` | Globally unique, and must occur exactly once in the document. |
| `targets` | Non-empty. Each target has an integer `rec_number` greater than zero, a non-empty `author` surname, an integer `year`, and a bare `doi`. |
| `display` | `default` for `[x]`, or `author-year` for `Author et al. [x]` under IEEE. `author-year` requires one target. |
| `pages` | Optional. Matches `^[0-9]+(\s*-\s*[0-9]+)?$`. Allowed only when `targets` has exactly one entry. |
| `suffix` | Optional free text such as `", p. 99"`. Allowed only when `targets` has exactly one entry. |
| `library.path` | Must exist and have a sibling `<name>.Data` directory. |
| `style` | Optional non-empty installed `.ens` style. Omit it to use the configured default, `IEEE`. |
Each citation becomes one temporary citation, so a merged entry with several targets produces one field, not several:
```text
{Thomsen, 2023 #1}
{Thomsen, 2023 #1@45-46}
{Magrin, 2023 #2; Bernhard, 2020 #3}
```
`pages` and `suffix` apply to the last target only, which is why they are restricted to single-target citations.
### IEEE DOI output style
The EndNote Bibliography Templates must place the literal `doi: https://doi.org/` immediately before the `DOI` field. Store only the bare DOI in EndNote. Journal Article, Conference Paper, and Web Page templates are specified in [styles-and-formatting.md](skills/endnote-for-word/references/styles-and-formatting.md). EndNote built-in styles must be opened and saved with **Save As** into the personal Styles folder; do not overwrite the installed style.
The manifest precheck refuses records whose EndNote DOI field already contains `doi:` or `https://doi.org/`. RIS export accepts those forms as input but writes one canonical bare `DO` value. Document validation then proves the visible bibliography contains exactly `doi: https://doi.org/<DOI>` for every cited target.
## Validation gates
`validate` fails the run with `ok: false` and exit code `3` when any gate fails.
1. No `{{CITE:` marker text remains anywhere in the document.
2. No residual temporary citation text remains, matched with `\{[^{}]*#\d+[^{}]*\}` over the document text.
3. The native citation field count equals the manifest citation count. Counting rule: fields whose code starts with `ADDIN EN.CITE`, minus fields whose code starts with `ADDIN EN.CITE.DATA`, because a large traveling library payload is moved into a nested data field.
4. When `bibliography.expected` is true, exactly one `ADDIN EN.REFLIST` field exists and its result text is not empty.
5. Every DOI is visibly printed as `doi: https://doi.org/<DOI>`, with no doubled resolver prefix.
6. Every manifest record number appears as `<rec-number>N</rec-number>` in some citation field's traveling library XML, and the matching author surname appears in the same field.
7. Every `author-year` native field result visibly contains its author surname.
8. The document text contains no `Error!`, `Reference source not found`, `{Citation}`, or `{Bibliography}` placeholder strings.
9. The `EN.Layout` document variable exists and its style matches the manifest style, compared case-insensitively.
10. The `EN.Libraries` document variable exists and lists every manifest record number inside `<record-ids>`.
## Version 1 limitations
| Limitation | Reason |
|---|---|
| No citation prefixes | The backslash prefix syntax, for example `{see \Thomsen, 2023 #1}`, opens a modal EndNote dialog that blocks automation. The manifest rejects `prefix` outright. |
| No excluded authors or years | `{\Thomsen, 2023 #1}` and the `ENExcludeAuthor` family are dialog-driven and hang the run. Use `suffix` text instead when the style permits it. |
| Library database safety | Searches read a temporary snapshot. The tool never edits `sdb.eni`; explicit RIS import is delegated to EndNote Direct Export. |
| Adding references is automated | `import_reference_file` opens the exact target library, sends RIS to EndNote, reports the count delta, and requires a fresh DOI search for assigned record numbers. A new target may be cloned only from a zero-record library while EndNote is fully closed. |
| Bibliography position is the CWYW default | EndNote places the reference list where Cite While You Write puts it, normally at the end of the document. Move it in EndNote or in Word if you need it elsewhere; this tool does not relocate it. |
| Instant formatting is not toggled | The CWYW toggle macro has no read-back, so calling it blindly would flip an unknown state. Change it in the EndNote ribbon if you need to. |
| Converting citations to plain text is manual | The CWYW macro behind it, `ENRemoveFieldCodes`, raises a modal confirmation dialog and never returns under automation, so there is no `remove-field-codes` action and no MCP tool for it. Do it yourself from the Word ribbon with **EndNote > Convert Citations and Bibliography > Convert to Plain Text**, which produces a new copy and leaves the original field codes intact. The result is one-way: EndNote can no longer update the citations in the converted copy. |
## Verify the installation
```console
pwsh.exe -NoProfile -ExecutionPolicy Bypass -File scripts/endnote-word.ps1 -Action probe
pwsh.exe -NoProfile -ExecutionPolicy Bypass -File scripts/endnote-word.ps1 -Action list-styles -Style IEEE
pwsh.exe -NoProfile -ExecutionPolicy Bypass -File tests/run-tests.ps1
```
The bridge preserves source files, writes through a temporary sibling DOCX, and refuses to replace an existing output unless `-Overwrite` is explicit. Cleanup is unified and verified: each run removes only tool-owned `.<name>.<guid>.work.docx` and `.<name>.<guid>.tmp.docx` siblings, confirms they no longer exist, and safely sweeps matching abandoned artifacts older than 24 hours. Repository tests isolate their temporary files in a uniquely named directory, remove Python caches, and fail if cleanup verification fails. Live integration tests are opt-in and need a real library path.
## Quick test prompt
This test creates a new target from an empty EndNote library while EndNote is fully closed. Replace the research topic, target path, template path, and DOCX path:
```text
Fully close EndNote before asking the Agent to create the missing target library.
Use the available scholarly-search or web tools to find one highly relevant peer-reviewed journal paper about "<research topic>". Do not invent metadata from memory; confirm the title, authors, journal, and year against the publisher page or a trusted scholarly index. The paper must have a DOI. Normalize it to a bare DOI and verify that https://doi.org/<DOI> resolves. Export the complete metadata as EndNote-compatible RIS, then call import_reference_file with library_path "<new target .enl>", ris_path "<RIS path>", and empty_library_template_path "<closed empty .enl>". Search the new library by DOI and use only the returned rec_number. In "<DOCX path>", replace any existing plain-text narrative author plus typed number, such as `Li et al. [1]`, with one {{CITE:test}} marker. Insert a native EndNote citation using IEEE and save a new suffixed output file. Use Display As: Author (Year) when the marker is the grammatical author subject; otherwise use Default Format. Keep Word and EndNote silent. Finally, validate the citation and bibliography fields and doi: https://doi.org/<DOI>, then report the result.
```
## Repository layout
| Path | Purpose |
|---|---|
| `skills/endnote-for-word/` | Cross-agent skill, references, and launcher |
| `scripts/` | Word and EndNote automation bridge, library reader, MCP server, and packager |
| `config/defaults.json` | Default output style, registered empty library template, temporary citation delimiters, and validation gates |
| `examples/` | Reference manifest |
| `tests/` | Static, MCP protocol, offline structure, library, and live integration checks |
| `evals/` | Evaluation cases |
## Packaging
```console
python scripts/package_plugin.py
```
The command creates `dist/endnote-for-word-plugin.zip`, the standalone skill package `dist/endnote-for-word.skill`, and a SHA-256 file for each. Release notes are in [CHANGELOG.md](CHANGELOG.md).
## Issues and discussion
If you have any questions or problems, please open a GitHub Issue to report them and join the discussion.
## License
[MIT](LICENSE)