Skip to main content
Glama

delete_mcp_server

Permanently delete an MCP server from obot by providing its ID. This action is irreversible.

Instructions

Delete an MCP server from obot by id. Irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Schema definition for the 'delete_mcp_server' tool. Declares a single required 'id' string parameter and marks the operation as irreversible.
    {
      name: "delete_mcp_server",
      description: "Delete an MCP server from obot by id. Irreversible.",
      inputSchema: {
        type: "object",
        properties: { id: { type: "string" } },
        required: ["id"],
        additionalProperties: false,
      },
    },
  • Handler for delete_mcp_server. Sends a DELETE request to /api/mcp-servers/{id} via obotFetch and returns a confirmation message.
    case "delete_mcp_server": {
      await obotFetch(`/api/mcp-servers/${encodeURIComponent(args.id)}`, { method: "DELETE" });
      return { content: [{ type: "text", text: `deleted ${args.id}` }] };
    }
  • src/index.ts:54-136 (registration)
    The tool is registered as part of the 'tools' array (line 54-136) and exposed via ListToolsRequestSchema handler (line 143).
    const tools: Tool[] = [
      {
        name: "list_mcp_servers",
        description:
          "List MCP servers currently registered in obot. Returns id, name, runtime, configured-state, and the connectURL you'd hand to claude.ai.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
      },
      {
        name: "get_mcp_server",
        description: "Get full details of one MCP server by id (including manifest, env, missingRequiredEnvVars).",
        inputSchema: {
          type: "object",
          properties: { id: { type: "string", description: "MCP server id, e.g. ms1mwrmr" } },
          required: ["id"],
          additionalProperties: false,
        },
      },
      {
        name: "add_npx_mcp",
        description:
          "Install a new MCP server in obot that runs as `npx <package>` (stdio). Use this for npm-published MCP servers.",
        inputSchema: {
          type: "object",
          properties: {
            name: { type: "string", description: "Display name shown in obot UI." },
            package: { type: "string", description: "npm package name, e.g. n8n-mcp or @scope/foo." },
            shortDescription: { type: "string" },
            env: {
              type: "object",
              description:
                "Env vars passed to the MCP process. Keys go in manifest.env[]. Mark secrets via sensitiveKeys.",
              additionalProperties: { type: "string" },
            },
            sensitiveKeys: {
              type: "array",
              items: { type: "string" },
              description: "Keys in `env` that should be marked sensitive (API keys, tokens).",
            },
            alias: {
              type: "string",
              description: "Optional short alias used in URLs/logs.",
            },
          },
          required: ["name", "package"],
          additionalProperties: false,
        },
      },
      {
        name: "add_remote_mcp",
        description: "Register a remote MCP server URL so obot proxies it. Use for HTTP/SSE MCPs hosted elsewhere.",
        inputSchema: {
          type: "object",
          properties: {
            name: { type: "string" },
            url: { type: "string", description: "Remote MCP endpoint URL." },
            shortDescription: { type: "string" },
            alias: { type: "string" },
          },
          required: ["name", "url"],
          additionalProperties: false,
        },
      },
      {
        name: "delete_mcp_server",
        description: "Delete an MCP server from obot by id. Irreversible.",
        inputSchema: {
          type: "object",
          properties: { id: { type: "string" } },
          required: ["id"],
          additionalProperties: false,
        },
      },
      {
        name: "list_catalog_entries",
        description:
          "List MCP catalog entries available in obot's default catalog. Optional substring filter on name/id.",
        inputSchema: {
          type: "object",
          properties: { search: { type: "string" } },
          additionalProperties: false,
        },
      },
    ];
  • The obotFetch helper function used by all tool handlers, including delete_mcp_server, to make authenticated HTTP requests to the obot API.
    async function obotFetch(path: string, init: RequestInit = {}): Promise<any> {
      const res = await fetch(`${OBOT_URL}${path}`, {
        ...init,
        headers: {
          Authorization: `Bearer ${OBOT_TOKEN}`,
          "Content-Type": "application/json",
          Accept: "application/json",
          ...(init.headers as Record<string, string> | undefined),
        },
      });
      const text = await res.text();
      let body: unknown = text;
      try {
        body = text ? JSON.parse(text) : null;
      } catch {
        // keep raw text
      }
      if (!res.ok) {
        const detail = typeof body === "string" ? body : JSON.stringify(body);
        throw new Error(`obot ${res.status} ${res.statusText} on ${path}: ${detail}`);
      }
      return body;
    }
Behavior3/5

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

Despite no annotations, the description highlights irreversibility, which is a key behavioral trait. However, it does not disclose permissions, effects on dependent resources, or error scenarios, leaving gaps.

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 short sentences, front-loaded with the primary action. Every word earns its place, no superfluous content.

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?

For a simple delete tool with one required parameter and no output schema, the description covers purpose and irreversibility. Lacks but not critical: indication of expected response.

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

Parameters2/5

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

The single parameter 'id' has no description in the schema (coverage 0%) and the tool description does not explain what the ID represents. This leaves ambiguity for the agent.

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?

Clear verb 'Delete' and specific resource 'MCP server from obot by id'. It distinctly describes the tool's action and differentiates from sibling tools like add, get, list.

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 on when to use this tool versus alternatives. The description only notes irreversibility but lacks context on prerequisites or when other tools are more appropriate.

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/kiarashedraki/obot-admin-mcp'

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