Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

Transfer Credential to Project

n8n_transfer_credential
Idempotent

Transfer credentials between projects in n8n to manage access and organize automation resources.

Instructions

Transfer a credential to a different project.

Args:

  • credentialId (string): Credential ID to transfer

  • destinationProjectId (string): Target project ID

Returns: Confirmation of transfer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
credentialIdYesCredential ID to transfer
destinationProjectIdYesTarget project ID

Implementation Reference

  • The implementation of the 'n8n_transfer_credential' tool, including its registration, description, schema definition, and the handler function that calls the /credentials/{credentialId}/transfer endpoint.
        server.registerTool('n8n_transfer_credential', {
            title: 'Transfer Credential to Project',
            description: `Transfer a credential to a different project.
    
    Args:
      - credentialId (string): Credential ID to transfer
      - destinationProjectId (string): Target project ID
    
    Returns:
      Confirmation of transfer.`,
            inputSchema: z.object({
                credentialId: z.string().min(1).describe('Credential ID to transfer'),
                destinationProjectId: z.string().min(1).describe('Target project ID')
            }).strict(),
            annotations: {
                readOnlyHint: false,
                destructiveHint: false,
                idempotentHint: true,
                openWorldHint: false
            }
        }, async (params) => {
            await put(`/credentials/${params.credentialId}/transfer`, {
                destinationProjectId: params.destinationProjectId
            });
            return {
                content: [{ type: 'text', text: `✅ Credential transferred to project ${params.destinationProjectId}` }],
                structuredContent: { transferred: true, credentialId: params.credentialId, projectId: params.destinationProjectId }
            };
        });
Behavior3/5

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

Annotations already indicate this is a mutable (readOnlyHint=false), non-destructive (destructiveHint=false), idempotent (idempotentHint=true) operation. The description adds minimal behavioral context beyond this, mentioning only a confirmation return without detailing side effects like permission requirements or credential state changes. It doesn't contradict annotations.

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

Conciseness4/5

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

The description is well-structured and front-loaded with the core purpose, followed by parameter and return details. It avoids unnecessary fluff, though the 'Args' and 'Returns' sections could be integrated more seamlessly into a single narrative flow.

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

Completeness3/5

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

Given the tool's moderate complexity (2 parameters, no output schema), the description covers the basic operation but lacks details on error conditions, authentication needs, or what 'confirmation' entails. Annotations provide safety hints, but more behavioral context would enhance completeness for a mutation tool.

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 description coverage is 100%, with both parameters clearly documented in the schema. The description's 'Args' section repeats this information without adding extra meaning, such as format examples or constraints. Baseline 3 is appropriate since the schema fully covers parameter semantics.

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 ('Transfer a credential') and resource ('to a different project'), distinguishing it from sibling tools like 'n8n_transfer_workflow' which transfers workflows instead of credentials. The verb 'transfer' is precise and the scope is well-defined.

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?

No guidance is provided on when to use this tool versus alternatives like 'n8n_update_credential' or 'n8n_create_credential', nor are prerequisites or exclusions mentioned. The description only states what the tool does, not when it should be selected.

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