Schema | mcp-dev-workflow

mcp-dev-workflow

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
branch_nameA	Generate a convention-following git branch name from a change type, ticket id and title. Example: {type:'feat', id:'ABC-123', title:'Add login'} => feat/ABC-123-add-login.
commit_messageA	Validate and normalize a Conventional Commit message (type(scope): subject). Returns { valid, normalized, errors, warnings, parsed } and flags type, length and imperative-mood issues.
pr_checklistA	Build a Markdown pull-request body from a list of commits (and optional changed files): a summary, a change list grouped by conventional type, and a checklist (tests, docs, breaking changes).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SergioRodas/mcp-dev-workflow'

If you have feedback or need assistance with the MCP directory API, please join our Discord server