chore(release): prep 0.1.2 — version bump, publish fix, README

[ElliotPadfield]

Release prep for 0.1.2, on top of #5 (already merged to main).

Why this needs to be its own PR

#5 was merged between my last two pushes, so this release-prep commit landed on the stale feature branch. Reopening it cleanly against main.

Summary

• Bump to 0.1.2 — patch for the MCP content-type fix and OpenAlex search backend swap that landed in fix: MCP-valid content type + swap /v2/search backend to OpenAlex (#4) #5. Also updates the server's internal version string in src/index.ts:124 so it stops drifting from package.json.
• Fix .github/workflows/npm-publish.yml — the build job runs npm test, but there is no test script, so the workflow would fail with npm error Missing script: "test" on release: created and block the publish-npm step. Replace with npm run build (real CI value — verifies the TypeScript compiles before publishing) plus npm test --if-present so a future test script plugs in without a workflow edit.
• README cleanup — reframe the "Setup" block as "Local development (contributors only)" so end users clearly land on the npx -y unpaywall-mcp config (this is the "modern-style, no npm install" path the MCP SDK already supports). Add a one-line note in the Quickstart confirming no clone / no install is needed. Update the unpaywall_search_titles output description to match the new shape delivered in fix: MCP-valid content type + swap /v2/search backend to OpenAlex (#4) #5 (results[].response, results[].score, results[].snippet, _source) and call out the OpenAlex-backed implementation.

Release plan after merge

1. Merge this PR.
2. Create a GitHub release tagged v0.1.2 — .github/workflows/npm-publish.yml triggers on release: created, builds, and runs npm publish.
3. npm view unpaywall-mcp version should then show 0.1.2.

Test plan

• npm run build succeeds at 0.1.2 (tsc clean).
• Stdio smoke test still passes 30/30 after the version bump (same test run as fix: MCP-valid content type + swap /v2/search backend to OpenAlex (#4) #5).
• Workflow YAML is syntactically valid (inspected).
• After merge + release, confirm the workflow run succeeds and npm view unpaywall-mcp version === 0.1.2.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@ElliotPadfield has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 24 minutes and 50 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 24 minutes and 50 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: de9cc039-3abf-44a0-9b53-543408946cae

📥 Commits

Reviewing files that changed from the base of the PR and between 72b0009 and 2810b73.

📒 Files selected for processing (4)

• .github/workflows/npm-publish.yml
• README.md
• package.json
• src/index.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/0.1.2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}