Schema | devflows-mcp

devflows-mcp

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": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
engine_statusA	Check that the local CIB seven engine is reachable and report its version.
deploy_processC	Deploy the release process to the engine. Deploying it twice is harmless.
list_processesA	List the process definitions the engine currently knows about.
start_releaseA	Start a release run for a repository. `Runs the repository quality gates, then waits for a human to approve. With dry_run true, which is the default, nothing is tagged or published.`
get_runB	Report the state, the current activity, the gate report and the variables of a run.
list_gatesB	List the gates a release of this repository would run. Does not touch the engine.
approve_gateB	Approve or reject a waiting release. This is the human decision in the process.

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/0langa/cibseven-devflows'

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