@boopkit/cap-oauth-server 0.1.3 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/scaffold/reference/oauth-server.ref.md +4 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boopkit/cap-oauth-server",
3
- "version": "0.1.3",
3
+ "version": "0.1.4",
4
4
  "description": "Make a boop app an OAuth 2.1 authorization server and resource server, so an MCP client can act on behalf of one of its users",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
package/scaffold/reference/oauth-server.ref.md CHANGED
@@ -6,9 +6,10 @@ This app is an OAuth 2.1 **authorization server** (it issues tokens on a user's
6
6
  and a **resource server** (it accepts those tokens on its own API).
7
7
  That is what lets Claude, Claude Code, ChatGPT or any MCP client act as one of your users.
8
8
 
9
- > Slices 1 and 2 have landed: the client registry, the discovery documents, the consent screen,
10
- > `POST /oauth/token`, and a resource-server guard good enough to protect a route.
11
- > Revocation, the connected-clients screen and the device flow are not here yet;
9
+ > What is here: the client registry, the discovery documents, the consent screen,
10
+ > `POST /oauth/token`, a resource-server guard good enough to protect a route,
11
+ > the connected-clients screen at `/connections`, and revocation, both from that screen and
12
+ > from the client through `POST /oauth/revoke`. The device flow is not here yet;
12
13
  > this page describes what is actually here and says plainly what is not.
13
14
 
14
15
  ## Related