Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
sdk/js: publish as io.github.google/agentmesh with GitHub OIDC
Mrunal Pendemcd96fb5e7a20
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 6014fa6b..4f9aa525 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -104,19 +104,18 @@ jobs:echo "00b21004149a4ce66f0782508ae4a2bce67d1bea395a8da0bd8028159fb59579 $RUNNER_TEMP/mcp-publisher.tar.gz" | sha256sum -c -tar -xzf "$RUNNER_TEMP/mcp-publisher.tar.gz" -C "$RUNNER_TEMP" mcp-publisherecho "$RUNNER_TEMP" >> "$GITHUB_PATH"- - name: Publish dev.sam-mesh/mesh to the MCP registry+ - name: Publish io.github.google/agentmesh to the MCP registry# The registry checks mcpName in the npm package, so this runs after npm publish.# If this version is already listed, skip so the job can be safely retried.+ # GitHub OIDC (id-token: write above) grants the io.github.google/* namespace.working-directory: sdk/js- env:- MCP_REGISTRY_PRIVATE_KEY: ${{ secrets.MCP_REGISTRY_PRIVATE_KEY }}run: |ver="${SDK_VERSION#v}"- if curl -fsS "https://registry.modelcontextprotocol.io/v0.1/servers/dev.sam-mesh%2Fmesh/versions/${ver}" >/dev/null 2>&1; then- echo "dev.sam-mesh/mesh ${ver} is already listed in the MCP registry; skipping."+ if curl -fsS "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.google%2Fagentmesh/versions/${ver}" >/dev/null 2>&1; then+ echo "io.github.google/agentmesh ${ver} is already listed in the MCP registry; skipping."exit 0fi- mcp-publisher login dns --domain sam-mesh.dev --private-key "$MCP_REGISTRY_PRIVATE_KEY"+ mcp-publisher login github-oidcmcp-publisher publishpublish-sdk-python:diff --git a/sdk/js/README.md b/sdk/js/README.mdindex ce77a34e..b38aff8c 100644--- a/sdk/js/README.md+++ b/sdk/js/README.md@@ -84,11 +84,6 @@ Inference and A2A discovery return metadata, but this executable provides noHTTP proxy, `/v1` endpoint, local socket or `local_proxy_url`. Use an SDK clientor an `agentmesh-node` HTTP proxy to invoke those protocols.-This source implementation is the executable portion of-[#544](https://github.com/google/agentmesh/issues/544). Official MCP registry-registration and release automation are separate work; this configuration does-not depend on a published registry entry.-## UseBoth programs below are indiff --git a/sdk/js/package.json b/sdk/js/package.jsonindex f35ecefa..c2e1e4fe 100644--- a/sdk/js/package.json+++ b/sdk/js/package.json@@ -76,5 +76,5 @@"express": "^5.2.1","typescript": "^7.0.2"},- "mcpName": "dev.sam-mesh/mesh"+ "mcpName": "io.github.google/agentmesh"}diff --git a/sdk/js/server.json b/sdk/js/server.jsonindex ced6d4aa..8da826f6 100644--- a/sdk/js/server.json+++ b/sdk/js/server.json@@ -1,6 +1,6 @@{"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",- "name": "dev.sam-mesh/mesh",+ "name": "io.github.google/agentmesh","title": "Agent Mesh","description": "Discover and call remote MCP tools as your own authenticated Agent Mesh member.","repository": {