# <type>: <subject>
#
# <body>
#
# <footer>
# Type should be one of the following:
# * feat - A new feature
# * fix - A bug fix
# * docs - Documentation only changes
# * style - Changes that do not affect the meaning of the code
# * refactor - A code change that neither fixes a bug nor adds a feature
# * perf - A code change that improves performance
# * test - Adding missing tests or correcting existing tests
# * build - Changes that affect the build system or external dependencies
# * ci - Changes to our CI configuration files and scripts
# * chore - Other changes that don't modify src or test files
# * revert - Reverts a previous commit
#
# NOTE: Version bumping is done manually by updating package.json
# The CI/CD pipeline will automatically build, test, and publish when code changes
#
# Examples:
# feat: add new password generator tool
# fix: resolve issue with base64 encoding
# chore: update dependencies
# docs: improve README examples
#
# Subject line rules:
# * Use imperative mood ("add" not "added" or "adds")
# * Don't capitalize first letter
# * No period at the end
# * Limit to 50 characters
#
# Body rules:
# * Wrap at 72 characters
# * Explain what and why, not how
# * Can include multiple paragraphs
#
# Footer rules:
# * Reference issues: "Closes #123" or "Fixes #456"
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wrenchpilot/it-tools-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server