Add disabled MCP read endpoint and PostgreSQL sessions #1600
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/mcp-server"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Partial implementation of the MCP plan. Includes the timeout assessment and pinned Bandit-compatible ExMCP foundations from #1598 and #1599. Adds RS256 Hydra token validation, PostgreSQL session ownership and atomic claims, protected resource metadata, and four bounded read tools. Disabled by default; no cluster changes.
Verification: 316 API tests passed, 230 PostgreSQL tests passed, and new Bash/jq token, tool, HTTP boundary, and session/protocol checks passed. Both protocol paths use the real HTTP plug; real-client sign-in is not yet tested.
Remaining: telemetry, logs, services, waits, commands/receipts, OAuth compatibility service and deployment. Shared OAuth discovery is owned by Flux ory-portal-bridge and advertises Pipelines registration. A compatibility decision is needed before replacing shared discovery with a Binjovi-specific endpoint. See docs/mcp-server.md. Recurring fork checks remain deferred.
WIP: Add disabled MCP read endpoint and PostgreSQL sessionsto Add disabled MCP read endpoint and PostgreSQL sessions