Skip to main content
Glama
hsiangjenli

Gitignore MCP Tool

by hsiangjenli

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITIGNORE_API_BASENoBase URL for gitignore.io APIhttps://www.toptal.com/developers/gitignore/api

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_gitignore_templatesB

List all available gitignore templates from gitignore.io

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • templates: List of available gitignore templates

    • Example:

{
  "templates": [
    "string"
  ]
}
generate_gitignoreC

Generate a .gitignore file based on specified templates and save it to the specified path

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • success: Whether the operation was successful

      • message: Status message

      • content: Generated .gitignore content

    • Example:

{
  "success": true,
  "message": "string",
  "content": "string"
}
  • 422: Validation Error

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "detail": [
    "unknown_type"
  ]
}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes with no overlap. 'generate_gitignore' creates a file based on templates, while 'list_gitignore_templates' provides the available template list. An agent would never confuse these tools as they serve different stages of the workflow.

Naming Consistency5/5

Both tools follow a perfect verb_noun pattern with consistent snake_case naming. 'generate_gitignore' and 'list_gitignore_templates' use clear, descriptive verbs that match their actions, creating a predictable naming convention throughout the tool set.

Tool Count2/5

With only 2 tools, this server feels under-scoped for a gitignore management system. While the tools cover basic functionality, there are obvious missing operations like updating existing gitignore files, deleting them, or managing custom templates that would make the surface more complete.

Completeness3/5

The tools provide core read and generate functionality but lack full lifecycle coverage. There's no way to update or delete generated gitignore files, and while templates can be listed, there's no ability to manage them. The surface covers basic workflows but leaves significant gaps for more complex scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues