Back to search
mcp-publish
MCP serverGitHub
MCP server that publishes agent results to a configurable file location (NuGet: JSdotNet.MCP.Publish)
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked today
Badge for your README
Markdown
[](/listings/jsdotnet--mcp-publish)HTML
<a href="/listings/jsdotnet--mcp-publish"><img src="/api/listings/jsdotnet--mcp-publish/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
dotnet tool install --global JSdotNet.MCP.Publish
The tool command is `jsdotnet-publish-mcpserver`.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 86 lines
- # JSdotNet Publish Results MCP Server
- Model Context Protocol (MCP) server that lets an AI agent publish its results to a **configurable file location**.
- NuGet id: `JSdotNet.MCP.Publish`. Split out of [JSdotNet/Project-Guidelines-MCP](https://github.com/JSdotNet/Project-Guidelines-MCP), which now holds only the application defaults.
- ## Installation
- ```bash
- dotnet tool install --global JSdotNet.MCP.Publish
- ```
- The tool command is `jsdotnet-publish-mcpserver`.
- ## Configuring the publish location
- The publish root is resolved in this order:
- 1. Configuration key `Publish:RootPath` — supplied on the command line (`--Publish:RootPath=D:\results`) or as the environment variable `Publish__RootPath`.
- 2. Environment variable `JSDOTNET_PUBLISH_PATH`.
- 3. Default: `%LOCALAPPDATA%\JSdotNet\PublishedResults` (Linux/macOS: `~/.local/share/JSdotNet/PublishedResults`).
- Additional settings:
- | Key | Default | Description |
- |-----|---------|-------------|
- | `Publish:RootPath` | per-user folder | Directory results are written to. Created if missing. Environment variables in the value are expanded. |
- | `Publish:AllowOverwriteByDefault` | `false` | When `true`, `publish_result` may replace existing files without `overwrite=true`. |
- All tool paths are relative to the root; absolute paths and `..` segments are rejected so the server can never write outside the configured location.
- ### Example `.mcp.json`
- ```json
- {
- "mcpServers": {
- "jsdotnet-publish": {
- "type": "stdio",
- "command": "jsdotnet-publish-mcpserver",
- "args": ["--Publish:RootPath=D:\\reports"],
- "tools": ["*"]
- }
- }
- }
- ```
- Or with an environment variable:
- ```json
- {
- "mcpServers": {
- "jsdotnet-publish": {
- "type": "stdio",
- "command": "jsdotnet-publish-mcpserver",
- "env": { "JSDOTNET_PUBLISH_PATH": "D:\\reports" },
- "tools": ["*"]
- }
- }
- }
- ```
- ## Tools
- | Tool | Purpose |
- |------|---------|
- | `publish_result` | Write a result to a file (fails on existing file unless `overwrite=true`). |
- | `append_result` | Append text to a file, creating it and its folders when needed. |
- | `list_published` | List published files (newest first), optionally filtered by a glob such as `*.md`. |
- | `read_published` | Read back the content of a published file. |
- | `delete_published` | Delete a published file. |
- | `get_publish_location` | Report the resolved absolute publish root. |
- | `get_usage_logs` | Recent tool invocations for this server process. |
- ## Development
- ```bash
- dotnet build JSdotNet.MCP.Publish.slnx
- dotnet test --project tests/JSdotNet.MCP.Publish.Tests/JSdotNet.MCP.Publish.Tests.csproj
- ```
- Package versions are managed centrally in `Directory.Packages.props` with lock files. CI
- (`.github/workflows/ci.yml`) builds, tests with an 80% coverage floor, runs CodeQL, and on
- `main` packs and pushes to NuGet.org (secret `NUGET_API_KEY`), versioned by GitVersion.
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.