Get the FREE Ultimate OpenClaw Setup Guide →

GEmojiSharp

:octocat: GitHub Emoji for C#, dotnet and beyond

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio hlaueriksson-gemojisharp dotnet run --project GEmojiSharp.McpServer/GEmojiSharp.McpServer.csproj \
  --env ASPNETCORE_URLS="http://0.0.0.0:5000" \
  --env DOTNET_ENVIRONMENT="Production"

How to use

GEmojiSharp is a GitHub Emoji library for C#/.NET that ships an MCP server to expose its emoji lookup and transformation capabilities over an API. The MCP server provides endpoints to query the GitHub emoji dataset, convert between aliases (like :tada:) and their actual emoji characters, and perform demojification/emojification operations using the GEmojiSharp library under the hood. Once running, you can integrate it into tooling or other services that rely on consistent GitHub emoji rendering or conversions.

To use the MCP server, start the service according to your environment. By default it binds to port 5000 (adjust via ASPNETCORE_URLS). You can then send HTTP requests to the exposed endpoints to fetch the emoji list, look up an emoji by alias or character, and convert text with emoji aliases. If your tooling supports MCP-style servers, configure it to communicate with the GEmojiSharp.McpServer instance to leverage the library’s emoji data and transformation helpers in real time.

How to install

Prerequisites:

  • .NET SDK (e.g., .NET 6+ or the version required by the project).
  • Git to clone the repository.

Steps:

  1. Clone the repository git clone https://github.com/hlaueriksson/GEmojiSharp.git
  2. Navigate to the MCP server project (adjust path if needed) cd GEmojiSharp/GEmojiSharp.McpServer
  3. Restore and build dotnet restore dotnet build
  4. Run the MCP server dotnet run --project GEmojiSharp.McpServer.csproj
  5. Verify the server is running by hitting the configured URL (default http://localhost:5000)

Notes:

  • If you’re deploying to a different environment, adjust the ASPNETCORE_URLS environment variable accordingly before starting.

Additional notes

Environment variables and configuration tips:

  • ASPNETCORE_URLS controls the listening URL and port (default 5000). Set this to http://0.0.0.0:5000 to expose publicly in containers.
  • DOTNET_ENVIRONMENT can be set to Development/Staging/Production to control logging and behavior.
  • If you’re running behind a reverse proxy or in a container, ensure proper port exposure and TLS termination as needed.
  • The MCP server relies on the GEmojiSharp library data; ensure network access to fetch any required emoji resources or data during startup if the project prompt requires it.
  • Check for updates to the GEmojiSharp.McpServer package alongside GEmojiSharp core library to keep emoji data in sync with GitHub Emoji data.

Related MCP Servers

Sponsor this space

Reach thousands of developers