Repository navigation
Fix confusing agents/user endpoint; clarify agent-handle route - #16
Merged
Merged
Conversation
- server.json: publish the stable https://paxai.app/mcp remote instead of the placeholder https://paxai.app/mcp/agents/user, which read like a user login rather than an agent handle. - README: make the "Start here" MCP endpoint explicit that {agent_name} is the agent handle (not a user login), and reconcile the named-route URL with the stable /mcp + X-Agent-Name form that server.json publishes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The registry remote should carry the agent identity. Restore the named route https://paxai.app/mcp/agents/{agent_name} and declare agent_name in the remote's variables object (per the official server.json schema), so MCP clients and the registry prompt for the agent handle before connecting. Update the README endpoint note to match. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Why
server.jsonadvertised the MCP remote ashttps://paxai.app/mcp/agents/user. Theuserpath segment reads like a user login, when it is actually meant to be an agent handle. For a public registry/Glama listing this is confusing and slightly wrong.Changes
server.json— publish the stablehttps://paxai.app/mcpremote (header-based agent binding viaX-Agent-Name) instead of theagents/userplaceholder. A registry client connects to a literal URL, so a fixed endpoint is correct here; verified it returns a cleanoauth_requiredchallenge with canonicalresource="https://paxai.app/mcp".README.md— make the "Start here" MCP endpoint explicit that the{agent_name}path segment is the agent handle (the name the agent is known by on aX), not a user login, and reconcile the named-route URL with the stable/mcpform thatserver.jsonpublishes.Not touched
archive/REPO_SETUP_GUIDE.mdstill references/mcp/agents/user— intentionally left as historical/internal notes not read by Glama or any client.Follow-up (separate)
Republishing
server.jsonto the official MCP Registry (version bump) so the registry entry matches this repo — held until the remaining server details are finalized.🤖 Generated with Claude Code