Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Disconnect Source Control

n8n_source_control_disconnect
DestructiveIdempotent

Disconnect from the remote Git repository to remove Git integration from n8n workflows.

Instructions

Disconnect from the remote Git repository.

⚠️ WARNING: This will remove the Git integration!

Returns: Confirmation of disconnection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/users-sourcecontrol.ts:287-294 (handler)
    Handler function for n8n_source_control_disconnect tool which performs a post request to disconnect source control.
    async () => {
  await post('/source-control/disconnect');
  
  return {
    content: [{ type: 'text', text: '✅ Source control disconnected successfully.' }],
    structuredContent: { disconnected: true }
  };
}
  • src/tools/users-sourcecontrol.ts:269-286 (registration)
    Registration of the n8n_source_control_disconnect tool including schema and metadata.
      server.registerTool(
    'n8n_source_control_disconnect',
    {
      title: 'Disconnect Source Control',
      description: `Disconnect from the remote Git repository.

⚠️ WARNING: This will remove the Git integration!

Returns:
  Confirmation of disconnection.`,
      inputSchema: EmptySchema,
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: true,
        openWorldHint: false
      }
    },

Tool Definition Quality

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds significant behavioral context beyond annotations: it explicitly warns that this 'will remove the Git integration' (reinforcing destructiveHint=true) and specifies what the tool returns ('Confirmation of disconnection'). This provides crucial operational details that annotations alone don't convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly structured: a clear action statement, a prominent warning, and a return value specification—all in three concise lines with zero wasted words. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no parameters and no output schema, the description provides complete context: what it does, the critical warning about consequences, and what to expect in response. This fully compensates for the lack of output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Disconnect from the remote Git repository') and distinguishes it from siblings like 'n8n_source_control_pull', 'n8n_source_control_push', and 'n8n_source_control_status' by focusing on removing integration rather than syncing or checking status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use it (to remove Git integration) and includes a warning about consequences, but doesn't explicitly mention when NOT to use it or name specific alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/DrBalls/n8n-mcp-server-v2'

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