Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

proxy_start_server

Start an HTTP/HTTPS proxy server for traffic monitoring and analysis, with optional SSL bumping to intercept encrypted connections.

Instructions

Start the proxy server with optional SSL bumping

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoPort to run proxy server on
hostNoHost to bind proxy server tolocalhost
enableSSLBumpingNoEnable SSL bumping for HTTPS traffic interception

Implementation Reference

  • Executes the proxy_start_server tool: checks if server is running, starts proxy server with specified port, host, and SSL bumping option, returns detailed status including PAC URL and CA certificate info.
    case 'proxy_start_server':
      if (this.proxyServer.isRunning()) {
        return {
          content: [{
            type: "text",
            text: `Proxy server is already running on ${this.proxyServer.getAddress()}`
          }]
        };
      }
    
      await this.proxyServer.start(args.port, args.host, {
        enableSSLBumping: args.enableSSLBumping
      });
      
      const serverStatus = this.proxyServer.getStatus();
      return {
        content: [{
          type: "text",
          text: `šŸš€ Proxy server started!\n\nAddress: ${this.proxyServer.getAddress()}\nPAC URL: ${this.proxyServer.getAddress()}/proxy.pac\nCA Certificate: ${this.proxyServer.getAddress()}/ca.crt\nSSL Bumping: ${serverStatus.sslBumpingEnabled ? 'ENABLED' : 'DISABLED'}\nMonitoring: ${this.targetManager.getStats().enabled} domains${serverStatus.sslBumpingEnabled ? '\n\nāš ļø  SSL Bumping is active - install CA certificate for HTTPS interception!' : ''}`
        }]
      };
  • Defines the input schema and description for the proxy_start_server tool, specifying optional parameters for port, host, and SSL bumping.
    proxy_start_server: {
      name: "proxy_start_server",
      description: "Start the proxy server with optional SSL bumping",
      inputSchema: {
        type: "object",
        properties: {
          port: {
            type: "number",
            description: "Port to run proxy server on",
            default: 8080
          },
          host: {
            type: "string",
            description: "Host to bind proxy server to",
            default: "localhost"
          },
          enableSSLBumping: {
            type: "boolean",
            description: "Enable SSL bumping for HTTPS traffic interception",
            default: false
          }
        }
      }
    },
  • index.js:66-74 (registration)
    Registers all tools including proxy_start_server by providing their schemas and descriptions in response to ListToolsRequest in the MCP server.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: Object.entries(TOOLS).map(([name, tool]) => ({
          name,
          description: tool.description,
          inputSchema: tool.inputSchema
        }))
      };
    });
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. It mentions 'optional SSL bumping,' which hints at a security-related feature, but fails to describe critical behaviors such as whether this is a long-running process, what happens if the server is already active, potential side effects (e.g., port conflicts), or authentication needs. For a server-start tool, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that front-loads the core action ('Start the proxy server') and includes a key optional feature ('with optional SSL bumping'). There is no wasted verbiage, making it highly concise and well-structured for quick comprehension.

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 starting a server (a state-changing operation) and the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like runtime effects, error conditions, or what success looks like. For a tool in a proxy management context with many siblings, more context is needed to guide the agent effectively.

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?

The description adds minimal value beyond the input schema, which has 100% coverage with clear descriptions for all three parameters. It mentions 'optional SSL bumping,' which loosely relates to the enableSSLBumping parameter but doesn't elaborate on its implications or usage. Since the schema already fully documents parameters, the baseline score of 3 is appropriate, as the description doesn't significantly enhance understanding.

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 clearly states the action ('Start') and resource ('proxy server'), with additional context about optional SSL bumping. It distinguishes this tool from sibling tools like proxy_stop_server and proxy_server_status by indicating it initiates the server. However, it doesn't explicitly differentiate from proxy_generate_setup or other setup-related tools, which slightly reduces specificity.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the server must be stopped first), when not to use it (e.g., if the server is already running), or refer to sibling tools like proxy_stop_server or proxy_server_status for status checks. This leaves the agent without contextual usage cues.

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/mako10k/mcp-web-proxy'

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