okf-mcp 1.3.0 → 1.4.0
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.
- checksums.yaml +4 -4
- data/.okf/design/runtime-dependencies.md +26 -7
- data/.okf/log.md +28 -0
- data/.okf/structure/server-definition.md +6 -3
- data/.okf/testing/layers.md +8 -2
- data/CHANGELOG.md +13 -0
- data/lib/okf/mcp/server.rb +4 -2
- data/lib/okf/mcp/version.rb +1 -1
- metadata +4 -4
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 0352b152b315e30e0e1a9d44c73522fda54cd9471e7e270fe80ea6ed779b1130
|
|
4
|
+
data.tar.gz: f20df9a569978beef37ebd38365f743183db05ac2efdac8d0e09f7d2843e2088
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 51ff63a34ff69291a9f13823570280e3322c7b93d79a978244e547b7b55061eb4687e961cfc6fb07160a54a5e7853e82d5bb802c333326711753b9c96368526c
|
|
7
|
+
data.tar.gz: 284db006105634dc0cc99f40620f0c8fe41d10e6bedc4e2b8c81d59ec2a9faef0141c0ac4938410a7fbc4fb85b6067e0768cfeb86f750294bb0e4d19c1e53145
|
|
@@ -4,8 +4,8 @@ title: Exactly two runtime dependencies
|
|
|
4
4
|
description: "`mcp` and `okf`, nothing else — rack and webrick arrive through okf and must never be named here — with both floors held to one rule: the floor tracks what the suite proves."
|
|
5
5
|
tags: [dependencies, gemspec, constraint]
|
|
6
6
|
generated:
|
|
7
|
-
by:
|
|
8
|
-
at: 2026-
|
|
7
|
+
by: process:okf-maintain
|
|
8
|
+
at: 2026-11-20T22:05:23Z
|
|
9
9
|
resource: okf-mcp.gemspec
|
|
10
10
|
---
|
|
11
11
|
|
|
@@ -28,11 +28,30 @@ kernel holds its own: argue it, do not add it for convenience — and
|
|
|
28
28
|
|
|
29
29
|
One rule covers both, and it is the reason the pins are not round numbers.
|
|
30
30
|
|
|
31
|
-
**`mcp` is pinned pessimistically (`~>`)**, and the
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
compatibility
|
|
31
|
+
**`mcp` is pinned pessimistically (`~>`)**, and the floor is not a guess about
|
|
32
|
+
compatibility. It is the oldest version of the supported SDK series the
|
|
33
|
+
suite proves. The supported series now starts at 1.11.0 and stops before 1.12.0.
|
|
34
|
+
Patch releases resolve normally; opening a new SDK minor takes a
|
|
35
|
+
compatibility run.
|
|
36
|
+
The session-dispatch regression exercises the SDK calling both request entry
|
|
37
|
+
points; the transport suites prove stdio and Streamable HTTP still answer.
|
|
38
|
+
|
|
39
|
+
`rake test:sdk_floor` is what makes that sentence true rather than hopeful. It
|
|
40
|
+
runs the whole suite against the oldest SDK the pin admits, and CI runs it on
|
|
41
|
+
the floor Ruby. Every other job resolves the *newest* admissible SDK, so without
|
|
42
|
+
that leg the ceiling was proven on seven Rubies and the floor on none — and the
|
|
43
|
+
floor is the half the gemspec promises an adopter.
|
|
44
|
+
|
|
45
|
+
The gemspec drill used to cover the gap differently, by refusing any floor older
|
|
46
|
+
than the SDK the suite had resolved. That forced the floor up to whatever
|
|
47
|
+
bundler fetched, which makes the claim true by never admitting anything but the
|
|
48
|
+
newest release: an upstream publication nobody here asked for narrowed what an
|
|
49
|
+
adopter may install. It fired twice that way, and on both occasions the suite
|
|
50
|
+
passed against the very floor it was raising away from. **A rule that is kept by
|
|
51
|
+
shrinking what it has to cover is not being kept.** The drill now asks whether
|
|
52
|
+
the requirement *admits* the version CI ran, because a requirement that excludes
|
|
53
|
+
it would mean every assertion above it proved a resolution the gem refuses to
|
|
54
|
+
install with.
|
|
36
55
|
|
|
37
56
|
**The `okf` floor may lead the kernel checkout but never lag it.** It names the
|
|
38
57
|
kernel version that ships what this shell rides — `Search.prepare/with/across`,
|
data/.okf/log.md
CHANGED
|
@@ -1,5 +1,33 @@
|
|
|
1
1
|
# Update Log
|
|
2
2
|
|
|
3
|
+
## 2026-11-20
|
|
4
|
+
|
|
5
|
+
* Support MCP 1.11 dispatch on stdio and Streamable HTTP. The
|
|
6
|
+
[server definition](structure/server-definition.md) forwards SDK arguments
|
|
7
|
+
unchanged, and the [runtime dependency](design/runtime-dependencies.md)
|
|
8
|
+
accepts 1.11.x and holds new minors for a compatibility run. The
|
|
9
|
+
[test layers](testing/layers.md) separate the SDK-session regression from
|
|
10
|
+
the transport checks.
|
|
11
|
+
|
|
12
|
+
## 2026-09-02
|
|
13
|
+
|
|
14
|
+
* **The SDK floor is proven by a run instead of asserted by a ratchet** —
|
|
15
|
+
[runtime-dependencies](design/runtime-dependencies.md). The rule was already
|
|
16
|
+
written down correctly: the floor "is the oldest version the tests actually
|
|
17
|
+
pass on". Nothing ever ran them there. `gemspec_test` closed that gap by
|
|
18
|
+
refusing any floor older than the SDK bundler had just resolved, which is a
|
|
19
|
+
different rule and a weaker one — it made the claim true by never admitting
|
|
20
|
+
anything but the newest release, so an upstream publication narrowed what an
|
|
21
|
+
adopter may install. `rake test:sdk_floor` runs the suite against the oldest
|
|
22
|
+
admissible SDK and CI runs it on the floor Ruby, so the sentence in the
|
|
23
|
+
concept is now a thing that happens rather than a thing that is hoped.
|
|
24
|
+
|
|
25
|
+
* **The two floors are not the same claim, and looking alike is how they got
|
|
26
|
+
confused.** The kernel arrives from a checkout, so this code can start calling
|
|
27
|
+
a surface the day it is written and its floor must follow. The SDK arrives
|
|
28
|
+
from RubyGems, so nothing here calls an mcp surface it was not written
|
|
29
|
+
against. The kernel drill stays exactly as it was; only the SDK one changed.
|
|
30
|
+
|
|
3
31
|
## 2026-08-21
|
|
4
32
|
|
|
5
33
|
* **The freshness stamp watches every file the registry reads** —
|
|
@@ -4,8 +4,8 @@ title: The server definition
|
|
|
4
4
|
description: The MCP::Server subclass, the fourteen tool builders and the private helpers they share, one declared output shape per tool, and concepts as resources with a URI parser the SDK's matcher cannot supply.
|
|
5
5
|
tags: [mcp, server, tools, schemas, resources]
|
|
6
6
|
generated:
|
|
7
|
-
by:
|
|
8
|
-
at: 2026-
|
|
7
|
+
by: process:okf-maintain
|
|
8
|
+
at: 2026-11-20T22:05:23Z
|
|
9
9
|
resource: lib/okf/mcp/server.rb
|
|
10
10
|
---
|
|
11
11
|
|
|
@@ -29,7 +29,10 @@ registry and an engine. `Definition` subclasses the SDK's server and adds the
|
|
|
29
29
|
per-request wrap: `#in_request` memoizes fingerprints and `#retain_served`
|
|
30
30
|
prunes cache residency, so a frame's repeated reads cost one stat. `#handle`
|
|
31
31
|
and `#handle_json` are what the tests drive — real JSON-RPC frames, no
|
|
32
|
-
transport involved.
|
|
32
|
+
transport involved. Both entry points forward the SDK's dispatch arguments
|
|
33
|
+
unchanged, including the `auth_info` keyword the supported SDK passes.
|
|
34
|
+
[The test layers](../testing/layers.md) distinguish the dispatch regression
|
|
35
|
+
from the transport checks.
|
|
33
36
|
|
|
34
37
|
**The fourteen builders**, one per tool: `tags_tool`, `types_tool`,
|
|
35
38
|
`stats_tool`, `list_bundles_tool`, `dirs_tool`, `index_tool`, `search_tool`,
|
data/.okf/testing/layers.md
CHANGED
|
@@ -4,8 +4,8 @@ title: What each test layer proves
|
|
|
4
4
|
description: Integration-first over real JSON-RPC frames, with process-spawning confined to the two files that prove the process — plus the wire-reading rules the SSE tests cannot be written without.
|
|
5
5
|
tags: [testing, integration, http, sse]
|
|
6
6
|
generated:
|
|
7
|
-
by:
|
|
8
|
-
at: 2026-
|
|
7
|
+
by: process:okf-maintain
|
|
8
|
+
at: 2026-11-20T22:05:23Z
|
|
9
9
|
resource: test/integration
|
|
10
10
|
---
|
|
11
11
|
|
|
@@ -19,6 +19,12 @@ resource: test/integration
|
|
|
19
19
|
| the argv shell | flags and exit codes, in-process, spawning nothing | `cli_test.rb` |
|
|
20
20
|
| units | the pieces with contracts of their own | `test/unit/` |
|
|
21
21
|
|
|
22
|
+
`test/unit/server_test.rb` drives both dispatch entry points through a real
|
|
23
|
+
SDK session, so dropping an SDK-supplied keyword fails without spawning a
|
|
24
|
+
process. `test/unit/gemspec_test.rb` checks the dependency bounds and the
|
|
25
|
+
resolved version, while [the SDK-floor task](../design/runtime-dependencies.md)
|
|
26
|
+
runs this same suite at the oldest admitted version.
|
|
27
|
+
|
|
22
28
|
The three tool directories mirror the kernel's own — the three ways a bundle is
|
|
23
29
|
named: by directory, through the registry, and several at once.
|
|
24
30
|
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,19 @@ All notable changes to this project are documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [1.4.0] - 2026-11-20
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
|
|
12
|
+
- Preserve the SDK's request arguments through the server's cache wrapper. MCP
|
|
13
|
+
1.11 passes an `auth_info` keyword during dispatch; the old wrapper rejected
|
|
14
|
+
it before either stdio or Streamable HTTP could answer.
|
|
15
|
+
|
|
16
|
+
### Changed
|
|
17
|
+
|
|
18
|
+
- Require MCP 1.11.x. Patches can resolve normally; a new minor must be tested
|
|
19
|
+
before the requirement admits it.
|
|
20
|
+
|
|
8
21
|
## [1.3.0] - 2026-08-22
|
|
9
22
|
|
|
10
23
|
### Fixed
|
data/lib/okf/mcp/server.rb
CHANGED
|
@@ -159,11 +159,13 @@ module OKF
|
|
|
159
159
|
# honest bound and the registry re-read made the set movable. Anything
|
|
160
160
|
# the registry no longer names is dropped here, so a repointed entry
|
|
161
161
|
# stops retaining the bundle its slug used to mean.
|
|
162
|
-
|
|
162
|
+
# The SDK owns dispatch arguments, including auth_info from 1.11.
|
|
163
|
+
# Preserve them while wrapping the whole request.
|
|
164
|
+
def handle(...)
|
|
163
165
|
in_request { super }
|
|
164
166
|
end
|
|
165
167
|
|
|
166
|
-
def handle_json(
|
|
168
|
+
def handle_json(...)
|
|
167
169
|
in_request { super }
|
|
168
170
|
end
|
|
169
171
|
|
data/lib/okf/mcp/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: okf-mcp
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.
|
|
4
|
+
version: 1.4.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Rodrigo Serradura
|
|
@@ -15,14 +15,14 @@ dependencies:
|
|
|
15
15
|
requirements:
|
|
16
16
|
- - "~>"
|
|
17
17
|
- !ruby/object:Gem::Version
|
|
18
|
-
version:
|
|
18
|
+
version: 1.11.0
|
|
19
19
|
type: :runtime
|
|
20
20
|
prerelease: false
|
|
21
21
|
version_requirements: !ruby/object:Gem::Requirement
|
|
22
22
|
requirements:
|
|
23
23
|
- - "~>"
|
|
24
24
|
- !ruby/object:Gem::Version
|
|
25
|
-
version:
|
|
25
|
+
version: 1.11.0
|
|
26
26
|
- !ruby/object:Gem::Dependency
|
|
27
27
|
name: okf
|
|
28
28
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -119,7 +119,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
119
119
|
- !ruby/object:Gem::Version
|
|
120
120
|
version: '0'
|
|
121
121
|
requirements: []
|
|
122
|
-
rubygems_version: 4.0.
|
|
122
|
+
rubygems_version: 4.0.10
|
|
123
123
|
specification_version: 4
|
|
124
124
|
summary: 'A Model Context Protocol server for OKF: discover, orient in, search, and
|
|
125
125
|
read knowledge bundles from any MCP-capable agent.'
|