Gobb

What is Gobb

Gobb is an MCP Automation Tool Suite designed specifically for .NET developers, aimed at enhancing development workflows by reducing time spent on repetitive tasks.

Use cases

Use cases for Gobb include automating code generation, improving debugging processes, and enhancing overall productivity in software development projects.

How to use

To use Gobb, developers need to install the tool suite and follow the setup instructions provided in the documentation. Once installed, users can leverage its functionalities to automate various aspects of their development process.

Key features

Key features of Gobb include integration with LLM agents, automation of mundane tasks, and enhancements to the development workflow, particularly for .NET 9.0 applications.

Where to use

Gobb is primarily used in software development environments, particularly those utilizing .NET technologies, to streamline coding processes and improve efficiency.

Table of Contents

1. About The Project
   • Core Functionality
   • Built With
2. Getting Started
   • Prerequisites
   • Installation
3. Roadmap
4. License
5. Contact
6. Acknowledgments

About The Project

As a Software Engineer, I am constantly trying to improve my development workflow. This is exactly why I created Gobb, which is a MCP server that aims to reduce time spent on mundane tasks.

As I have experimented with VS Code’s Agent Mode and Cursor, I have been impressed with AI’s ability to write code. However, there are a few pieces missing from these Chat Agents that would significantly improve my workflow. The goal of Gobb is to bridge these gaps by providing external functionality through MCP to these LLM agents.

Core Functionality

Gobb is still early in development, so it is limited in features. Gobb currently includes:

• TicketTool - A service to retrieve Tickets/Issues and inject them into an agent’s context window.
  • Methods:
    • GetTicketContextAsync - A method to retrieve a Ticket’s context and return it to the agent.
  • Supported Ticket Systems:
    • Jira
    • GitHub Issues

Built With

• 

(back to top)

Getting Started

To get Gobb running locally, follow these steps!

Prerequisites

The following software/tools need to be installed

• VS Code (or any IDE with an Agent mode, I have only tested Gobb with VS Code so far)
  • You will need Agent Mode enabled.
  • This will require you to have a GitHub account to use GitHub Copilot.
• Docker
  • I prefer to use Docker-Desktop.
• .NET 9.0 - Optional
  • Install this SDK if you want to develop Gobb, otherwise you can just run the docker image.
  • I prefer to use Visual Studio Community for easy integration with .NET, but you can run dotnet commands in VS Code instead.

Installation

1. Create an API token to use Jira’s API.

2. Open any repository in VSCode and create a .vscode folder if it doesn’t already exist.

3. Under this folder add a file called mcp.json. The following example shows how this should look:

   {
      "inputs": [],
      "servers": {
          "gobb": {
              "command": "docker",
              "args": [
                  "run",
                  "-i",
                  "--rm",
                  "-e", "JiraClientOptions__Url={INSERT_URL}",
                  "-e", "JiraClientOptions__Email={INSERT_EMAIL}",
                  "-e", "JiraClientOptions__ApiToken={INSERT_APITOKEN}",
                  "-e", "TicketClient__Type=Jira",
                  "jpuksta1/gobb"
              ]
          }        
      }
    }
   

   This config allows VS Code to execute Gobb’s latest image (stored in the jpuksta1/gobb registry). This config expects the following environment variables:

   1. The JIRA URL that hosts your Ticket data. Example: https://domain.atlassian.net
   2. The email that your JIRA account is registered with.
   3. The API Token you just created.
   4. (Optional) If using GitHub as the ticket client:
      • TicketClient__Type: Set to GitHub.
      • GitHubClient__RepositoryOwner: The owner of the GitHub repository.
      • GitHubClient__RepositoryName: The name of the GitHub repository.

4. Once mcp.json is set up, there should be a “Start” option that appears in the config.

   

   Once started, you should see this wrench icon in your Agent chat window.
   

   Note: Make sure that you have Agent Mode selected, otherwise this will not appear.

   If you click on the wrench icon, you will be able to see Gobb and it’s available methods!
   

5. Interact with your Agent chat window to call Gobb:
   For this demonstration, I have created a simple Jira Ticket: Gobb-1, which looks like this:
   

   When I tell Copilot to get the summary and description of this ticket, it will call my Gobb MCP server:
   

   Click “Continue”, and watch the magic:

   

6. Continue Vibe Coding and Interact with your Agent to tell it to keep/undo changes!

7. Optional: If you want to locally debug Gobb, then you will need to inject the URL, Email, and ApiToken in the appsettings.json file. Notes on how to debug can be found under Debug Notes.

   Gobb supports dynamic selection of ticket providers (Jira or GitHub). To configure this, update the appsettings.json file or set environment variables as needed.

   appsettings.json Example

• Type: Specifies the ticket provider to use. Set to Jira for Jira integration or GitHub for GitHub integration.
• GitHubClient: Only required if Type is set to GitHub. Configure the repository owner, name, and token here.

Other appsettings.json Configuration

In addition to the dynamic ticket provider configuration, the appsettings.json file includes the following settings:

• Logging: Configures the logging levels for the application.

  • Default: The default logging level for the application.
  • System: The logging level for system-related logs.
  • Microsoft: The logging level for Microsoft-related logs.

• JiraClientOptions: Contains the configuration for connecting to Jira.

  • Url: The base URL of your Jira instance (e.g., https://domain.atlassian.net).
  • Email: The email address associated with your Jira account.
  • ApiToken: The API token for authenticating with Jira.

These settings are essential for the application’s functionality and should be configured according to your environment.

(back to top)

Roadmap

I plan to fill this out as I come up with more use-cases of MCP for my personal development workflow, or if I get any good suggestions.

• [ ] Add Ability to Create JIRA tickets
• [x] Support GitHub’s ticket system
• [ ] Explore/Support integrating git operations
• [ ] Explore/Support LSP to easily address Errors/Warnings/etc

See the open issues for a full list of proposed features (and known issues).

(back to top)

License

Distributed under the MIT License. See LICENSE for more information.

(back to top)

Contact

Feel free to connect with me on LinkedIn!

(back to top)

Acknowledgments

• Best-READEME-Template - This is a great template for creating a README!

(back to top)