Add AI-native MCP server and agent skills#42
Closed
ksaidi-terpomo wants to merge 1 commit into
Closed
Conversation
d747643 to
14595d8
Compare
14595d8 to
2048ecf
Compare
Collaborator
Author
|
not applicable |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
mcpserverGradle application module that exposes Pmitz operations as MCP STDIO tools.PmitzBackendinterface.../pmitz-samplesas the recommended realistic sample environment for trying the MCP server with the public-library demo.Positioning
This MCP server is not the normal runtime integration path for applications. Production applications should continue to call Pmitz through the Java APIs, remote client, or remote HTTP API.
The MCP server is for developer, testing, support, and operations workflows where an AI assistant needs to inspect, configure, or exercise Pmitz. The docs and both Codex/Claude skills carry this positioning.
Runtime path:
MCP path:
Why
This gives AI clients a stable tool interface for Pmitz instead of requiring them to call Java APIs or hand-roll HTTP requests. The sample docs connect that interface to the existing public-library sample stack.
Sample workflow
Start the sibling sample stack:
cd ../pmitz-samples ./start-sample-public-library startThen point the MCP server at the sample Pmitz server:
The sample product uses
public-library, featurereserve, and limitmaxborrowed.Validation
./gradlew :mcpserver:test --tests io.terpomo.pmitz.mcpserver.tools.PmitzMcpLocalE2ETestsremoteserveron H2, covering upload, usage, limits, subscriptions, entitlement, and removal tool calls../gradlew :mcpserver:testafter updating/removing internal work-log references../gradlew build