概览
What is Comedy MCP Server?
A Model Context Protocol (MCP) server that provides comedy-related tools and services for AI assistants, built with ASP.NET Core. It integrates with Cursor IDE and offers tools for generating programming jokes and funny code comments.
How to use Comedy MCP Server?
Clone the repository, set up the .env file, restore dependencies with dotnet restore, and build with dotnet build. Run with dotnet run (development, production, or with MCP Inspector via npx @modelcontextprotocol/inspector dotnet run). Verify by opening http://localhost:5000 or testing tools with node test-mcp.js.
Key features of Comedy MCP Server
- Generates random programming jokes
- Creates humorous code comments from context
- Echo service with logging demonstration
- Swagger integration for API documentation
- Health check endpoint for server status
- CORS support for MCP inspector tool
Use cases of Comedy MCP Server
- Adding humor to AI‑assisted code review sessions
- Generating funny comments to lighten development workflows
- Demonstrating MCP tool integration in .NET projects
- Testing MCP communication with Cursor IDE or other clients
FAQ from Comedy MCP Server
What are the prerequisites to run Comedy MCP Server?
.NET 8.0 SDK or later, Node.js 14+ (for MCP inspector), a code editor (Cursor IDE recommended), and Git.
How do I run the server in development mode?
Use dotnet run --environment Development. To debug MCP tools, run with npx @modelcontextprotocol/inspector dotnet run.
What MCP tools does Comedy MCP Server provide?
Three tools: GetProgrammingJoke (no parameters, returns a random joke), GetCodeComment (requires codeContext and topic parameters, returns a funny comment), and EchoWithLog (echoes a message with logging).
How can I verify the server is running correctly?
Open http://localhost:5000 to see the "Comedy MCP Server is running!" message, access Swagger at /swagger, or run the included node test-mcp.js script.
What should I do if the port is already in use?
Change the port in appsettings.json or stop the process using the current port. If dependencies are missing, run dotnet restore again.
