Cisco MCP Pods Server

Instructions

Implementation Reference

• src/podsClient.js:61-64 (handler)

  The core handler function that executes the tool logic: makes a GET request to the /api/v2/pods/keyword endpoint using the configured base URL and authentication.

  async getPodKeyword() {
    const url = `${this.baseUrl}/api/v2/pods/keyword`;
    return this.makeRequest(url, { method: 'GET' });
  }

• src/index.js:33-39 (schema)

  The tool schema definition including name, description, and empty input schema (no parameters required). Used in ListTools response.

    name: 'get_pod_keyword',
    description: 'Get the pod keyword/password record. Returns the current keyword configuration.',
    inputSchema: {
      type: 'object',
      properties: {},
    },
  },

• src/index.js:209-219 (registration)

  Tool execution handler in the CallToolRequestSchema switch statement: calls podsClient.getPodKeyword() and formats response as text content.

  case 'get_pod_keyword': {
    const result = await podsClient.getPodKeyword();
    return {
      content: [
        {
          type: 'text',
          text: JSON.stringify(result, null, 2),
        },
      ],
    };
  }

• src/server-http.js:117-122 (registration)

  Identical tool registration and schema in the HTTP server variant (createMCPServer).

  name: 'get_pod_keyword',
  description: 'Get the pod keyword/password record. Returns the current keyword configuration.',
  inputSchema: {
    type: 'object',
    properties: {},
  },

• src/server-http.js:227-231 (registration)

  Tool execution handler in HTTP server's CallToolRequestSchema switch statement.

  case 'get_pod_keyword': {
    const result = await podsClient.getPodKeyword();
    return {
      content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
    };