Skip to main content
Glama

n8n_transfer_credential

Move credentials between n8n projects to maintain access control and organization when restructuring workflows.

Instructions

Transfer a credential to another project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCredential ID
destinationProjectIdYesTarget project ID

Implementation Reference

  • Request handler for 'n8n_transfer_credential' tool.
    case 'n8n_transfer_credential': {
      if (!args?.id || !args?.destinationProjectId) {
        throw new Error('id and destinationProjectId are required');
      }
      const result = await n8nClient.transferCredential(args.id as string, args.destinationProjectId as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • N8nClient helper method that executes the actual API call for transferring a credential.
    async transferCredential(id: string, destinationProjectId: string): Promise<any> {
      const response = await this.client.put(`/credentials/${id}/transfer`, {
        destinationProjectId
      });
      return response.data;
    }
  • src/index.ts:649-659 (registration)
    Tool registration for 'n8n_transfer_credential' including input schema.
      name: 'n8n_transfer_credential',
      description: 'Transfer a credential to another project',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Credential ID' },
          destinationProjectId: { type: 'string', description: 'Target project ID' },
        },
        required: ['id', 'destinationProjectId'],
      },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. States 'transfer' but fails to clarify critical behavioral details: whether this moves (removes from source) or copies the credential, whether the credential ID changes, or if existing references break.

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?

Single sentence with zero waste. Action verb front-loaded. Efficient structure despite brevity; every word earns its place.

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

Completeness2/5

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

Transfer operations typically involve destructive side effects and prerequisites. With no annotations, output schema, or behavioral details in the description, critical context is missing for safe invocation.

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

Parameters3/5

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

Schema has 100% description coverage ('Credential ID', 'Target project ID'), satisfying baseline. Description provides semantic action context ('Transfer') linking the two parameters but adds no format constraints or usage examples beyond the schema.

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

Purpose4/5

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

Specific verb 'Transfer' with clear resource 'credential' and scope 'to another project'. Distinguishes from sibling n8n_transfer_workflow by specifying the resource type, though it could clarify the transfer mechanism (move vs copy).

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus alternatives like n8n_create_credential, or prerequisites such as whether the destination project must exist or required permissions.

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

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