Skip to main content
Glama

update_mcp_integration

Update an MCP integration's name, description, URL, authentication, or transport. Changes take effect immediately; altering URL or auth_type can disrupt connected clients.

Instructions

Update an MCP integration's name, description, URL, auth, or transport. Changes apply immediately and altering url or auth_type can break connected clients; use update_mcp_server when you only need to rename or re-describe a server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe MCP integration ID or slug to update
nameNoNew display name
descriptionNoNew description
urlNoNew URL endpoint
auth_typeNoNew authentication type
transportNoNew transport protocol
custom_headersNoNew custom headers for authentication. Sent via configurations.custom_headers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Implementation Reference

  • The MCP tool handler for 'update_mcp_integration'. It extracts id and custom_headers from params, calls service.mcpIntegrations.updateMcpIntegration(), and returns a success message.
    server.tool(
    	"update_mcp_integration",
    	"Update an MCP integration's name, description, URL, auth, or transport. Changes apply immediately and altering url or auth_type can break connected clients; use update_mcp_server when you only need to rename or re-describe a server.",
    	MCP_INTEGRATIONS_TOOL_SCHEMAS.updateMcpIntegration,
    	async (params) => {
    		const { id, custom_headers, ...rest } = params;
    		await service.mcpIntegrations.updateMcpIntegration(id, {
    			...rest,
    			...(custom_headers ? { configurations: { custom_headers } } : {}),
    		});
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							message: `Successfully updated MCP integration "${id}"`,
    							success: true,
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	},
    );
  • Zod schema for the updateMcpIntegration tool, defining optional fields: name, description, url, auth_type, transport, custom_headers, plus the required id.
    updateMcpIntegration: {
    	id: z.string().describe("The MCP integration ID or slug to update"),
    	name: z.string().optional().describe("New display name"),
    	description: z.string().optional().describe("New description"),
    	url: z.string().optional().describe("New URL endpoint"),
    	auth_type: z
    		.enum(["oauth_auto", "headers", "none"])
    		.optional()
    		.describe("New authentication type"),
    	transport: z
    		.enum(["http", "sse"])
    		.optional()
    		.describe("New transport protocol"),
    	custom_headers: z
    		.record(z.string(), z.string())
    		.optional()
    		.describe(
    			"New custom headers for authentication. Sent via configurations.custom_headers",
    		),
    },
  • Registration of the tool via server.tool('update_mcp_integration', ...) inside the registerMcpIntegrationsTools function.
    server.tool(
    	"update_mcp_integration",
    	"Update an MCP integration's name, description, URL, auth, or transport. Changes apply immediately and altering url or auth_type can break connected clients; use update_mcp_server when you only need to rename or re-describe a server.",
    	MCP_INTEGRATIONS_TOOL_SCHEMAS.updateMcpIntegration,
    	async (params) => {
    		const { id, custom_headers, ...rest } = params;
    		await service.mcpIntegrations.updateMcpIntegration(id, {
    			...rest,
    			...(custom_headers ? { configurations: { custom_headers } } : {}),
    		});
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							message: `Successfully updated MCP integration "${id}"`,
    							success: true,
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	},
    );
  • Service method updateMcpIntegration() that sends a PUT request to /mcp-integrations/{id} with the update data.
    async updateMcpIntegration(
    	id: string,
    	data: UpdateMcpIntegrationRequest,
    ): Promise<{ success: boolean }> {
    	await this.put(`/mcp-integrations/${this.encodePathSegment(id)}`, data);
    	return { success: true };
    }
  • TypeScript interface UpdateMcpIntegrationRequest defining the shape of the update payload (name?, description?, url?, auth_type?, transport?, configurations?).
    export interface UpdateMcpIntegrationRequest {
    	name?: string;
    	description?: string;
    	url?: string;
    	auth_type?: string;
    	transport?: string;
    	configurations?: {
    		custom_headers?: Record<string, string>;
    	};
    }
Behavior4/5

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

Annotations already indicate non-readonly, non-destructive, non-idempotent behavior. The description adds behavioral context by stating that changes apply immediately and altering url or auth_type can break connected clients, which is critical risk information beyond what annotations provide.

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 two sentences, front-loaded with the core action. Every sentence provides essential information: what is updated, immediate effects, and differentiation from sibling. No redundant or missing words.

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

Completeness4/5

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

Given the tool's complexity (7 parameters, 2 enums, nested objects) and the presence of an output schema, the description covers the main aspects: fields that can be updated, immediate application, and risks. It does not describe the return value, but the output schema exists to provide that. It could mention potential side effects for other parameters but is sufficient for most agents.

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?

The input schema has 100% coverage with detailed descriptions for each parameter, so the description's general listing of fields adds no new semantic value. The baseline of 3 is appropriate since the schema already documents the parameters well.

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 explicitly states the verb 'Update' and the resource 'MCP integration', listing the specific fields: name, description, URL, auth, or transport. It distinguishes itself from the sibling tool 'update_mcp_server' by noting that this tool handles URL/auth/transport changes, while the sibling is for renaming/re-describing.

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

Usage Guidelines5/5

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

The description provides clear when-to-use guidance by naming the alternative 'update_mcp_server' for cases where only renaming or re-describing is needed. It also warns about the impact of changing url or auth_type, indicating when caution is needed.

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/s-b-e-n-s-o-n/portkey-admin-mcp'

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