Repository navigation
Orbitport mcp - #154
Open
DaniDeltaT wants to merge 4 commits into
Open
Orbitport mcp#154DaniDeltaT wants to merge 4 commits into
DaniDeltaT wants to merge 4 commits into
Conversation
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
1 participant
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.
Description
Adds a gateway native MCP endpoint for Orbitport KMS at POST /mcp.
exposes the existing KMS JSON RPC capabilities as MCP tools while preserving the current gateway security and execution model: bearer token auth, rate limiting, account hold/release, authoritative kms_tenant resolution, and KMS plugin routing all remain inside the gateway.
Added optional MCP support behind config ORBITPORT_MCP_ENABLED.
Added POST /mcp plus protected-resource metadata endpoints: /.well-known/oauth-protected-resource
/.well-known/oauth-protected-resource/mcp
Exposed existing KMS operations as MCP tools: crypto KMS tools like kms_create_key, kms_encrypt, kms_decrypt, kms_sign, kms_rotate_key
key-store tools like kms_keystore_put, kms_keystore_get, kms_keystore_list, kms_keystore_delete
Added MCP tools/list schemas with both inputSchema and outputSchema (assures agentic callers can properly formulate payloads being sent and create scripts that adhere to the expected output schema)
Reused existing KMS request/response shapes, so MCP tool arguments match the current JSON-RPC API.
Prevented callers from supplying tenant identity fields such as ClientId, client_id, KmsTenant, or kms_tenant.
Added MCP protocol compatibility handling for current and older client initialization formats (currently validated on openAI)
Added origin allowlist handling for browser-origin MCP requests.
Preserved opaque JSON precision for key-store MCP responses by using raw JSON serialization.
Updated README, context docs, dev guide, KMS README, and Swagger/OpenAPI docs.
Security Notes
MCP does not bypass the existing gateway path. Tool execution still requires a valid Orbitport bearer token, performs account hold/release, and uses the account resolved kms_tenant.
Only tools/call performs account hold and spends credits. Metadata/discovery calls such as initialize and tools/list are non sensitive and are not charged.
Changes
Checklist
Fixes #XX)