Skip to main content
Glama

list_mcp_integrations

Read-onlyIdempotent

Retrieve paginated MCP integrations for your organization. Filter by workspace to discover integration IDs for detailed queries.

Instructions

List MCP integrations in the organization. Returns paginated integration records plus total and has_more for discovering integration IDs; use get_mcp_integration for one integration's full Portkey-side config and list_mcp_servers for the servers under an integration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
current_pageNoPage number for pagination
page_sizeNoNumber of results per page (max 100)
workspace_idNoFilter by workspace ID

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 tool handler for 'list_mcp_integrations' that calls the service method and formats the response (total, has_more, integrations).
    server.tool(
    	"list_mcp_integrations",
    	"List MCP integrations in the organization. Returns paginated integration records plus total and has_more for discovering integration IDs; use get_mcp_integration for one integration's full Portkey-side config and list_mcp_servers for the servers under an integration.",
    	MCP_INTEGRATIONS_TOOL_SCHEMAS.listMcpIntegrations,
    	async (params) => {
    		const result = await service.mcpIntegrations.listMcpIntegrations(params);
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							total: result.total,
    							has_more: result.has_more,
    							integrations: result.data.map(formatMcpIntegration),
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	},
    );
  • Zod input schema for list_mcp_integrations: current_page, page_size, workspace_id.
    listMcpIntegrations: {
    	current_page: z.coerce
    		.number()
    		.positive()
    		.optional()
    		.describe("Page number for pagination"),
    	page_size: z.coerce
    		.number()
    		.int()
    		.positive()
    		.max(100)
    		.optional()
    		.describe("Number of results per page (max 100)"),
    	workspace_id: z.string().optional().describe("Filter by workspace ID"),
    },
  • Registration of 'list_mcp_integrations' via server.tool() inside registerMcpIntegrationsTools, also registered in TOOL_DOMAIN_REGISTRARS at src/tools/index.ts:47.
    export function registerMcpIntegrationsTools(
    	server: McpServer,
    	service: PortkeyService,
    ): void {
    	server.tool(
    		"list_mcp_integrations",
    		"List MCP integrations in the organization. Returns paginated integration records plus total and has_more for discovering integration IDs; use get_mcp_integration for one integration's full Portkey-side config and list_mcp_servers for the servers under an integration.",
    		MCP_INTEGRATIONS_TOOL_SCHEMAS.listMcpIntegrations,
    		async (params) => {
    			const result = await service.mcpIntegrations.listMcpIntegrations(params);
    			return {
    				content: [
    					{
    						type: "text",
    						text: JSON.stringify(
    							{
    								total: result.total,
    								has_more: result.has_more,
    								integrations: result.data.map(formatMcpIntegration),
    							},
    							null,
    							2,
    						),
    					},
    				],
    			};
    		},
    	);
  • Service method listMcpIntegrations that makes the HTTP GET request to /mcp-integrations with pagination params.
    export class McpIntegrationsService extends BaseService {
    	async listMcpIntegrations(
    		params?: ListMcpIntegrationsParams,
    	): Promise<ListMcpIntegrationsResponse> {
    		return this.get<ListMcpIntegrationsResponse>("/mcp-integrations", {
    			current_page: params?.current_page,
    			page_size: params?.page_size,
    			workspace_id: params?.workspace_id,
    		});
    	}
  • Type definitions for ListMcpIntegrationsResponse and ListMcpIntegrationsParams.
    export interface ListMcpIntegrationsResponse {
    	object: "list";
    	total: number;
    	has_more: boolean;
    	data: McpIntegration[];
    }
    
    export interface ListMcpIntegrationsParams {
    	current_page?: number;
    	page_size?: number;
    	workspace_id?: string;
    }
Behavior4/5

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint. Description adds pagination details (total, has_more) and response structure. No contradictions.

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?

Two efficient sentences: first states purpose, second adds guidance and response details. No unnecessary words.

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?

Given low complexity, presence of output schema, and rich annotations, the description sufficiently covers pagination, filtering, and exit points for deeper details.

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 coverage is 100% and descriptions are fully present in schema. Description adds no additional parameter-level context beyond the schema.

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?

Clearly states 'List MCP integrations in the organization' and mentions pagination. Differentiates from siblings like get_mcp_integration and list_mcp_servers.

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?

Explicitly directs to use get_mcp_integration for full config and list_mcp_servers for servers under an integration, providing clear when-to-use vs alternatives.

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