Luke.ClickUpMcpServer
0.1.1
dotnet tool install --global Luke.ClickUpMcpServer --version 0.1.1
dotnet new tool-manifest
dotnet tool install --local Luke.ClickUpMcpServer --version 0.1.1
#tool dotnet:?package=Luke.ClickUpMcpServer&version=0.1.1
nuke :add-package Luke.ClickUpMcpServer --version 0.1.1
MCP Server
This README was created using the C# MCP server project template. It demonstrates how you can easily create an MCP server using C# and publish it as a NuGet package.
The MCP server is built as a dotnet global tool package that requires the .NET runtime to be installed on the target machine. The project is configured to target .NET 9.0 and supports multiple runtime identifiers:
win-x64
win-arm64
osx-arm64
linux-x64
linux-arm64
linux-musl-x64
If your users require more platforms to be supported, update the list of runtime identifiers in the project's <RuntimeIdentifiers />
element.
See aka.ms/nuget/mcp/guide for the full guide.
Please note that this template is currently in an early preview stage. If you have feedback, please take a brief survey.
Checklist before publishing to NuGet.org
- Test the MCP server locally using the steps below.
- Update the package metadata in the .csproj file, in particular the
<PackageId>
. - Update
.mcp/server.json
to declare your MCP server's inputs.- See configuring inputs for more details.
- Pack the project using
dotnet pack
.
The bin/Release
directory will contain the package file (.nupkg), which can be published to NuGet.org.
Developing locally
To test this MCP server from source code (locally) without using a built MCP server package, you can configure your IDE to run the project directly using dotnet run
.
{
"servers": {
"ClickUpMcpServer": {
"type": "stdio",
"command": "dotnet",
"args": [
"run",
"--project",
"<PATH TO PROJECT DIRECTORY>"
]
}
}
}
Testing the MCP Server
Once configured, you can ask Copilot Chat for a random number, for example, Give me 3 random numbers
. It should prompt you to use the get_random_number
tool on the ClickUpMcpServer
MCP server and show you the results.
Publishing to NuGet.org
Automated Publishing via GitHub Actions
This repository includes a GitHub Actions workflow that automatically builds, packs, and publishes the MCP server to NuGet.org. The workflow is triggered on:
- Push to
master
branch (publishes latest version with auto-generated version numbers) - Tags matching
v*
pattern (publishes release versions using the tag as version) - Pull requests (builds and tests only)
Version Management:
- For pushes to
master
: Automatically generates versions in format0.1.{COMMIT_COUNT}-beta+{SHORT_SHA}
- For tagged releases: Uses the tag name (without 'v' prefix) as the version number
Setup Required:
- Set the
CLICKUP_MCPSERVER_NUGET_API_KEY
secret in your GitHub repository settings - The workflow publishes to
https://api.nuget.org/v3/index.json
Manual Publishing
For manual publishing, you can still use the traditional dotnet commands:
- Run
dotnet pack -c Release
to create the NuGet package - Publish to NuGet.org with
dotnet nuget push bin/Release/*.nupkg --api-key <your-api-key> --source https://api.nuget.org/v3/index.json
Using the MCP Server from NuGet.org
Once the MCP server package is published to NuGet.org, you can configure it in your preferred IDE. Both VS Code and Visual Studio use the dnx
command to download and install the MCP server package from NuGet.org.
- VS Code: Create a
<WORKSPACE DIRECTORY>/.vscode/mcp.json
file - Visual Studio: Create a
<SOLUTION DIRECTORY>\.mcp.json
file
For both VS Code and Visual Studio, the configuration file uses the following server definition:
{
"servers": {
"ClickUpMcpServer": {
"type": "stdio",
"command": "dnx",
"args": [
Luke.ClickUpMcpServer,
"--version",
"latest",
"--yes"
],
"env" : {
"TEAM_ID": "",
"PERSONAL_API_KEY": ""
}
}
}
}
More information
.NET MCP servers use the ModelContextProtocol C# SDK. For more information about MCP:
Refer to the VS Code or Visual Studio documentation for more information on configuring and using MCP servers:
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
Version | Downloads | Last Updated |
---|---|---|
0.1.1 | 258 | 9/15/2025 |
0.1.1-beta | 192 | 9/14/2025 |
0.1.0 | 256 | 9/15/2025 |
0.1.0-beta | 197 | 9/14/2025 |