Skip to main content
Glama
danielrosehill

MetaMCP Admin MCP

bulk_import_servers

Import multiple MCP server configurations simultaneously from Claude Desktop JSON format to set up servers across MetaMCP instances.

Instructions

Bulk import MCP servers (Claude Desktop JSON format)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serversYesMap of server name to config (Claude Desktop format)
instanceNoInstance name

Implementation Reference

  • The bulkImportServers method that executes the tool logic by calling the MetaMCP API mutation 'frontend.mcpServers.bulkImport'
    async bulkImportServers(mcpServers: Record<string, any>) {
      return this.mutate<{
        success: boolean;
        imported: number;
        errors?: string[];
        message?: string;
      }>("frontend.mcpServers.bulkImport", { mcpServers });
    }
  • src/index.ts:157-183 (registration)
    Tool registration with name 'bulk_import_servers', description, Zod schema for input validation, and handler function that calls client.bulkImportServers()
    // Bulk import servers
    server.tool(
      "bulk_import_servers",
      "Bulk import MCP servers (Claude Desktop JSON format)",
      {
        servers: z
          .record(
            z.string(),
            z.object({
              command: z.string().optional(),
              args: z.array(z.string()).optional(),
              env: z.record(z.string(), z.string()).optional(),
              url: z.string().optional(),
              headers: z.record(z.string(), z.string()).optional(),
              description: z.string().optional(),
              type: z.string().optional(),
            })
          )
          .describe("Map of server name to config (Claude Desktop format)"),
        instance: z.string().optional().describe("Instance name"),
      },
      async ({ servers, instance }) => {
        const client = getClient(clients, instance);
        const result = await client.bulkImportServers(servers);
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it specifies the input format, it fails to disclose critical behavioral traits for a bulk operation: idempotency (whether it upserts or fails on existing), atomicity, partial failure handling, or side effects on the target instance.

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 a single, efficient sentence with zero redundancy. Every word earns its place by specifying quantity ('bulk'), action ('import'), resource ('MCP servers'), and format constraints. However, for a complex nested operation, it may be excessively terse.

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?

Given the complexity of bulk imports (nested object schema, potential for partial failures, no output schema), the description is incomplete. It lacks information on return values, success/failure indicators, or whether existing servers are overwritten or preserved.

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% (both 'servers' and 'instance' parameters have descriptions). The tool description reinforces the 'Claude Desktop JSON format' constraint mentioned in the schema for the servers parameter but adds no additional semantic context beyond what the schema already provides.

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?

The description provides a specific action ('Bulk import'), resource ('MCP servers'), and format specification ('Claude Desktop JSON format'). The term 'bulk' distinguishes this from the sibling 'create_server' which implies single creation, though it does not explicitly name the alternative.

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

Usage Guidelines3/5

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

The term 'bulk' implies usage context (when importing multiple servers at once), but there are no explicit guidelines on when to prefer this over 'create_server', nor any mention of prerequisites or validation requirements for the Claude Desktop format.

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/danielrosehill/MetaMCP-Admin-MCP'

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