gluecron_trigger_workflow — Gluecron MCP Tool
gluecron_trigger_workflow
(gluecron trigger workflow) is one of 63 tools on the
Gluecron
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call gluecron_trigger_workflow from your client
- Claude Code Gluecron gluecron_trigger_workflow run in your project directory
- Claude Desktop Gluecron gluecron_trigger_workflow ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Gluecron gluecron_trigger_workflow ~/.cursor/mcp.json
- VS Code Gluecron gluecron_trigger_workflow .vscode/mcp.json
- Zed Gluecron gluecron_trigger_workflow ~/.config/zed/settings.json
- Windsurf Gluecron gluecron_trigger_workflow ~/.codeium/windsurf/mcp_config.json
- Cline Gluecron gluecron_trigger_workflow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Gluecron gluecron_trigger_workflow ~/.gemini/settings.json
- Grok Gluecron gluecron_trigger_workflow .mcp.json (in your project root)
- ChatGPT Gluecron gluecron_trigger_workflow Settings → Connectors → Advanced → Developer mode
- Claude.ai Gluecron gluecron_trigger_workflow Settings → Connectors → Add custom connector
- LangChain Gluecron gluecron_trigger_workflow pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gluecron https://gluecron.com/mcpOther tools on this server
- gluecron_repo_search
- gluecron_repo_read_file
- gluecron_repo_list_issues
- gluecron_repo_explain_codebase
- gluecron_repo_health
- gluecron_create_issue
- gluecron_comment_issue
- gluecron_close_issue
- gluecron_reopen_issue
- gluecron_create_pr
- gluecron_get_pr
- gluecron_list_prs
- gluecron_comment_pr
- gluecron_merge_pr
- gluecron_close_pr
- gluecron_fork_repo
- gluecron_delete_repo
- gluecron_update_repo
- gluecron_search_repos
- gluecron_whoami
- gluecron_clone_url
- gluecron_label_issue
- gluecron_unlabel_issue
- gluecron_assign_issue
- gluecron_search_issues
- gluecron_request_changes
- gluecron_search_prs
- gluecron_open_draft_pr
- gluecron_generate_pr_description
- gluecron_read_file
- gluecron_write_file
- gluecron_delete_file
- gluecron_list_tree
- gluecron_get_commit
- gluecron_get_diff
- gluecron_create_branch
- gluecron_atomic_multi_file_commit
- gluecron_ship_spec
- gluecron_voice_to_pr
- gluecron_refactor_across_repos
- gluecron_explain_repo
- gluecron_chat_with_repo
- gluecron_chat_continue
- gluecron_generate_tests
- gluecron_generate_commit_message
- gluecron_generate_release_notes
- gluecron_propose_migration
- gluecron_propose_doc_update
- gluecron_get_workflow_run
- gluecron_get_workflow_logs
- gluecron_cancel_workflow_run
- gluecron_get_preview_url
- gluecron_provision_pr_sandbox
- gluecron_create_agent_session
- gluecron_acquire_lease
- gluecron_release_lease
- gluecron_get_agent_budget
- gluecron_semantic_search
- gluecron_find_symbol
- gluecron_pr_status_summary
- gluecron_ai_cost_summary
- gluecron_security_scan
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.