Skip to content

Commit 28a0198

Browse files
DennisAlundCopilot
andcommitted
docs: refine CHANGELOG wording for 0.7.0
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 720c6b4 commit 28a0198

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

CHANGELOG.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,19 +2,19 @@
22

33
## 0.7.0
44

5-
### MCP server moved into the Worker
5+
### MCP endpoint refactored into the Worker
66

7-
The standalone `@oddbit/shrtnr-mcp` npm package has been replaced by a built-in remote MCP endpoint at `/_/mcp`. Every shrtnr deployment now serves an MCP server over Streamable HTTP transport, authenticated with API keys.
7+
The MCP server is now a built-in remote endpoint at `/_/mcp`, served directly by the Cloudflare Worker. Every shrtnr deployment includes the MCP server out of the box, authenticated with the same API keys as the admin API.
88

99
- Added `/_/mcp` endpoint using Cloudflare's `agents` SDK with `createMcpHandler()`
10-
- MCP tools call the service layer directly instead of going through HTTP
10+
- MCP tools call the service layer directly for lower latency
1111
- Stateless per-request design: no Durable Objects required
12-
- Removed the `mcp/` package directory and its npm publish workflow
13-
- Updated `release-packages.yml` and `detect-releases.sh` to cover SDK only
12+
- Consolidated the `mcp/` directory into the main application
13+
- Simplified CI workflows to reflect the single-package structure
1414

1515
### Migration from `@oddbit/shrtnr-mcp`
1616

17-
Replace `npx @oddbit/shrtnr-mcp` with a remote connection to your shrtnr deployment. See the MCP section in `README.md` for client configuration examples.
17+
Replace `npx @oddbit/shrtnr-mcp` with a remote MCP connection to your shrtnr deployment. See the MCP section in `README.md` for client configuration examples.
1818

1919
## 0.6.3
2020

0 commit comments

Comments
 (0)