You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: update download link of mcp-publisher in GitHub Actions to 1.1.0 (#565)
This pull request makes a minor update to the documentation for
installing the MCP Publisher in GitHub Actions workflows. The change
updates the installation command to use version 1.1.0 of the MCP
Publisher instead of version 1.0.0.
The `mcp-publisher` version in GitHub Actions has to be updated so it
can publish the MCP server to the newest version of MCP Registry.
Documentation update only. No test needed.
No
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [x] Documentation update
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [x] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [x] My code follows the repository's style guidelines
- [x] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [x] I have added or updated documentation as needed
None
Copy file name to clipboardExpand all lines: docs/reference/server-json/generic-server-json.md
+113Lines changed: 113 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -672,3 +672,116 @@ For MCP servers that follow a custom installation path or are embedded in applic
672
672
}
673
673
```
674
674
675
+
676
+
### Remote Server with URL Templating
677
+
678
+
This example demonstrates URL templating for remote servers, useful for multi-tenant deployments where each instance has its own endpoint. Unlike Package transports (which reference parent arguments/environment variables), Remote transports define their own variables:
Clients configure the tenant identifier, and the `{tenant_id}` variable in the URL gets replaced with the provided variable value to connect to the appropriate tenant endpoint (e.g., `https://anonymous.modelcontextprotocol.io/mcp/us-cell1` or `https://anonymous.modelcontextprotocol.io/mcp/emea-cell1`).
703
+
704
+
### Local Server with URL Templating
705
+
706
+
This example demonstrates URL templating for local/package servers, where variables reference parent Package arguments or environment variables:
"description": "Local MCP server with configurable port",
713
+
"title": "Configurable Server",
714
+
"version": "1.0.0",
715
+
"packages": [
716
+
{
717
+
"registryType": "npm",
718
+
"registryBaseUrl": "https://registry.npmjs.org",
719
+
"identifier": "@example/mcp-server",
720
+
"version": "1.0.0",
721
+
"transport": {
722
+
"type": "streamable-http",
723
+
"url": "http://localhost:{port}/mcp"
724
+
},
725
+
"packageArguments": [
726
+
{
727
+
"type": "named",
728
+
"name": "--port",
729
+
"description": "Port for the server to listen on",
730
+
"default": "3000",
731
+
"valueHint": "port"
732
+
}
733
+
]
734
+
}
735
+
]
736
+
}
737
+
```
738
+
739
+
The `{port}` variable in the URL references either the `--port` argument name or the `port` valueHint from packageArguments. When the package runs with `--port 8080`, the URL becomes `http://localhost:8080/mcp`.
0 commit comments