feat: add MCP registry publishing automation (#2)

Add configuration and automation for publishing to the Model Context Protocol (MCP) Registry for improved server discoverability.

- Add server.json with remote server configuration using streamable-http transport
- Add GitHub Actions workflow for automated publishing on version tags
- Update README with publishing instructions
- Configure GitHub OIDC authentication for registry publishing
- Fix routes section formatting in README for proper GitHub rendering

The server is configured as a remote MCP server pointing to the live Vercel deployment at https://docusign-navigator-mcp.vercel.app/mcp

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <[email protected]>

Author: coston

.github/workflows/publish-mcp.yml

@@ -0,0 +1,43 @@
+name: Publish to MCP Registry
+
+on:
+  push:
+    tags:
+      - 'v*'
+  workflow_dispatch:
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v5
+        with:
+          node-version: 'lts/*'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run lint
+        run: npm run lint
+
+      - name: Run type check
+        run: npm run type-check
+
+      - name: Install MCP Publisher
+        run: |
+          curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
+
+      - name: Login to MCP Registry
+        run: ./mcp-publisher login github-oidc
+
+      - name: Publish to MCP Registry
+        run: ./mcp-publisher publish

README.md

@@ -12,22 +12,24 @@ A Model Context Protocol (MCP) server that provides secure DocuSign Navigator in
 
 ## Routes
 
+```
 API Routes
 ├── Health & Monitoring
-│ └── GET /health
+│   └── GET /health
 │
 ├── OAuth 2.0 Discovery (.well-known)
-│ ├── GET /.well-known/oauth-authorization-server
-│ └── GET /.well-known/oauth-protected-resource
+│   ├── GET /.well-known/oauth-authorization-server
+│   └── GET /.well-known/oauth-protected-resource
 │
 ├── OAuth 2.0 Flow
-│ ├── GET/POST /register
-│ ├── GET /authorize
-│ ├── POST /token
-│ └── GET /auth/callback
+│   ├── GET/POST /register
+│   ├── GET /authorize
+│   ├── POST /token
+│   └── GET /auth/callback
 │
 └── MCP (Model Context Protocol)
-└── POST /mcp Main endpoint
+    └── POST /mcp (Main endpoint)
+```
 
 ## Quick Start
 
@@ -264,6 +266,10 @@ DOCUSIGN_REDIRECT_URI=https://your-app.vercel.app/auth/callback
 # Note: BASE_URL should be empty in production (Vercel sets VERCEL_URL automatically)
 ```
 
+### Publishing to MCP Registry
+
+This server is published to the [MCP Registry](https://github.com/modelcontextprotocol/registry) for easy discovery. Publishing happens automatically via GitHub Actions when you create a version tag (e.g., `git tag v1.0.0 && git push origin --tags`) or can be triggered manually from the Actions tab. The server is configured in [server.json](server.json) as a remote server pointing to the live Vercel deployment.
+
 ## Architecture
 
 - **Framework**: Vercel API routes deployed on Vercel

server.json

@@ -0,0 +1,17 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
+  "name": "io.github.thisdot/docusign-navigator-mcp",
+  "description": "Secure DocuSign Navigator integration for AI assistants to access and analyze agreement data.",
+  "version": "1.0.0",
+  "websiteUrl": "https://github.com/thisdot/docusign-navigator-mcp#readme",
+  "repository": {
+    "url": "https://github.com/thisdot/docusign-navigator-mcp",
+    "source": "github"
+  },
+  "remotes": [
+    {
+      "type": "streamable-http",
+      "url": "https://docusign-navigator-mcp.vercel.app/mcp"
+    }
+  ]
+}