feat(mcp): retarget csoai.org/mcp routes to csoai-gspc-mcp worker - #38
Merged
Conversation
Retarget csoai.org/mcp* and www.csoai.org/mcp* from sov-mcp-gateway (500 kind=no-token) to the public-friendly csoai-gspc-mcp worker. Changes: - workers/csoai-gspc-mcp: worker with routes for csoai.org/mcp* - .well-known/mcp.json: reference live MCP server - .well-known/mcp/server-card.json: Smithery/MCP discovery card The worker handles public initialize + tools/list without Authorization. Free verify stays loginless. No key required in Smithery. No SOV* branding. Deploy requires: cd workers/csoai-gspc-mcp && npx wrangler deploy GHA workflow needs CF_ACCOUNT_ID + CF_API_TOKEN secrets. Supersedes PR #29 (HOLD) which added the worker stub without routes. Co-authored-by: Nicholas Templeman <nicholas@csoai.org>
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.
Problem
POST https://csoai.org/mcpreturns 500kind=no-tokenfromsov-mcp-gateway.The good worker already exists and is LIVE at https://csoai-gspc-mcp.nicholastempleman.workers.dev/mcp (returns 200, no auth required).
Smithery cannot scan
csoai.org/mcpbecause the gateway demands auth that should not exist on public tools.Solution
Retarget
csoai.org/mcp*andwww.csoai.org/mcp*routes onto the public-friendlycsoai-gspc-mcpworker by declaring routes inwrangler.toml.Changes
workers/csoai-gspc-mcp/wrangler.tomlcsoai.org/mcp*workers/csoai-gspc-mcp/src/index.js.well-known/mcp.json.well-known/mcp/server-card.jsonWhat stays free/public (no Authorization)
initialize— no authtools/list— no authverify— free, loginless, no trustmeasure/jail-probe— returns contract (metered issuance on keystone)No key in Smithery. No SOV* branding in public chrome.
GHA Deployment Steps (REQUIRED FOR ROUTE FLIP)
After merge, a GHA workflow must run:
cd workers/csoai-gspc-mcp npx wrangler deployRequirements:
CF_ACCOUNT_IDandCF_API_TOKENsecrets in GHAcsoai.orgzoneRoute Conflict Note
The current
sov-mcp-gatewayworker ownscsoai.org/mcp*. The new routes in this worker will take over that path once deployed (Cloudflare prioritizes the most recently deployed worker routes). No need to patch or redeploysov-mcp-gateway.Related
Verification
After deploy, confirm: