Skip to main content
Glama

add_remote_mcp

Register a remote MCP server URL to allow obot to proxy HTTP/SSE MCPs hosted elsewhere.

Instructions

Register a remote MCP server URL so obot proxies it. Use for HTTP/SSE MCPs hosted elsewhere.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
urlYesRemote MCP endpoint URL.
shortDescriptionNo
aliasNo

Implementation Reference

  • Schema registration for the 'add_remote_mcp' tool: defines name, description, and inputSchema with required fields name (string) and url (string), plus optional shortDescription and alias.
    {
      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,
      },
    },
  • src/index.ts:54-136 (registration)
    The tool is registered in the tools array (line 101-115) which is returned 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,
        },
      },
    ];
  • Handler for 'add_remote_mcp': constructs a manifest with runtime 'remote' and remoteConfig.url, POSTs to /api/mcp-servers via obotFetch, and returns id and connectURL.
    case "add_remote_mcp": {
      const body: Record<string, any> = {
        manifest: {
          name: args.name,
          shortDescription: args.shortDescription ?? "",
          runtime: "remote",
          remoteConfig: { url: args.url },
        },
      };
      if (args.alias) body.alias = args.alias;
      const data = await obotFetch("/api/mcp-servers", {
        method: "POST",
        body: JSON.stringify(body),
      });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ id: data.id, connectURL: data.connectURL }, null, 2),
          },
        ],
      };
    }
  • The obotFetch helper function used by the handler 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;
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions proxy behavior but lacks details on side effects, authentication, rate limits, or what happens on failure. Insufficient for a registration tool.

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?

Extremely concise two sentences with no waste. Front-loaded with purpose and use case.

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?

With 4 parameters, no output schema, and no annotations, description is too minimal. Lacks info on return values, validation, error handling, or any guarantees about the proxy behavior.

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?

Only 25% of parameters have descriptions in schema (url only). Description adds no further parameter details, leaving agents to guess semantics for name, shortDescription, alias.

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?

Description clearly states it registers a remote MCP server URL for proxying, and specifies use case for HTTP/SSE MCPs, differentiating it from siblings like add_npx_mcp.

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

Usage Guidelines4/5

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

Explicitly states to use for HTTP/SSE MCPs hosted elsewhere, providing clear context. However, no explicit when-not-to-use or alternative tools mentioned beyond the context.

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