Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HTK_SERVER_URLNoHTTP Toolkit server URLhttp://127.0.0.1:45457
HTK_SERVER_TOKENNoAuthentication token (if server requires one)

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_versionA

Get the current HTTP Toolkit server version

get_configB

Get HTTP Toolkit proxy configuration including certificate paths, network interfaces, system proxy, and DNS servers

get_network_interfacesB

List all network interfaces on the system

trigger_updateB

Trigger an update check for the HTTP Toolkit server

shutdown_serverA

Shutdown the HTTP Toolkit server. WARNING: This will stop all interception.

list_interceptorsA

List all available HTTP traffic interceptors (browsers, terminals, mobile devices, Docker, etc.) and their activation status

get_interceptor_metadataC

Get detailed metadata for a specific interceptor. Returns available targets like Docker containers, Android devices, JVM processes, etc.

deactivate_interceptorB

Deactivate a running interceptor and stop capturing its traffic

intercept_chromeA

Launch a fresh independent Chrome window with all HTTP(S) traffic intercepted. The browser uses an isolated profile so it won't affect your normal browsing.

intercept_firefoxA

Launch a fresh independent Firefox window with all HTTP(S) traffic intercepted. Uses an isolated profile.

intercept_fresh_terminalA

Open a new terminal window where all launched processes and Docker containers will have their HTTP(S) traffic intercepted automatically.

intercept_existing_terminalA

Get a command to run in an existing terminal to start intercepting HTTP(S) traffic from processes launched in that terminal. Returns shell-specific commands for bash, zsh, fish, etc.

intercept_docker_containerB

Intercept all HTTP(S) traffic from a running Docker container. Injects proxy settings into the container to capture all outgoing HTTP traffic.

intercept_android_adbA

Intercept HTTP(S) traffic from an Android device or emulator connected via ADB. Automatically injects system HTTPS certificates into rooted devices and most emulators.

frida_android_setupA

Set up a Frida host on an Android device connected via ADB. This prepares the device for app-level interception by installing the Frida server and CA certificate.

frida_android_launchB

Launch the Frida server on an Android device. Must run frida_android_setup first.

frida_android_interceptA

Intercept a specific Android app using Frida dynamic instrumentation. Automatically disables most certificate pinning. Requires a rooted device with Frida server running (use frida_android_setup and frida_android_launch first).

frida_ios_interceptA

Intercept a specific iOS app using Frida dynamic instrumentation. Automatically disables most certificate pinning. Requires a jailbroken device running Frida Server connected via USB.

intercept_jvmA

Attach to a running JVM process (Java, Kotlin, Clojure, etc.) to intercept all its HTTP(S) traffic. Uses Java agent attachment.

intercept_electronB

Launch an Electron application with all its HTTP(S) traffic intercepted. Use get_interceptor_metadata with id "electron" to list available Electron apps.

send_http_requestA

Send an HTTP request through the HTTP Toolkit proxy. The request will be intercepted and visible in the HTTP Toolkit UI. Returns the full response including status code, headers, and body.

activate_interceptorA

Generic tool to activate any interceptor by ID with custom options. Use the dedicated tools (intercept_chrome, intercept_docker_container, etc.) when possible for better parameter validation.

capture_trafficA

Capture live HTTP(S) traffic being intercepted by HTTP Toolkit. Creates a temporary session, subscribes to traffic events via WebSocket, collects requests and responses for the specified duration, then returns all captured exchanges. Use this to see what HTTP requests are being made by intercepted browsers, apps, or containers.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/fdciabdul/httptoolkit-mcp'

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