Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PEEK_FILES_ROOTNorestricts multipart.files.<name>.path, download_to, and save_to to canonical paths under this prefix; unset means no constraint. Does not apply to multipart.files.<name>.content_base64 (no path involved)
PEEK_TLS_INSECURENoskip TLS verification0
PEEK_JQ_TIMEOUT_MSNoper-mask jq timeout5000
PEEK_USE_NATIVE_JQNoswitch to subprocess jq (reserved, not heavily exercised)0
PEEK_INLINE_BODY_CAPNohard cap on body_mode: inline (256 KB)262144
PEEK_SCHEMA_MAX_DEPTHNorecursion depth for schema renderers10
PEEK_CACHE_TTL_SECONDSNocache entry lifetime (10 min)600
PEEK_DEFAULT_TIMEOUT_MSNoper-request HTTP timeout30000
PEEK_HEAD_PREVIEW_ITEMSNoarray items kept verbatim in body_preview (rest collapsed)5
PEEK_MAX_RESPONSE_BYTESNohard cap on cached body size (50 MB)52428800
PEEK_HEAD_PREVIEW_STRINGNostring truncation length in body_preview200
PEEK_MAX_INLINE_FILE_BYTESNohard cap on multipart.files.<name>.content_base64 (10 MB pre-base64)10485760
PEEK_HEAD_PREVIEW_THRESHOLDNobody_mode: auto upgrades to head below this; otherwise schema65536
PEEK_INLINE_THRESHOLD_BYTESNobody_mode: auto upgrades to inline below this8192
PEEK_SCHEMA_MAX_OBJECT_KEYSNoper-object key cap200
PEEK_SCHEMA_SAMPLE_MAX_STRINGNostring truncation in samples100

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
http_requestA

Perform an HTTP request and return a compact schema of the response, not the full body.

Default flow (use this for any non-trivial response): (1) call http_request to get { schema, cache_id }; (2) call http_read with cache_id and a jq mask to extract only the field(s) you need. This keeps your context small even on multi-MB responses.

body_mode controls how much of the body comes back inline: schema (no body — schema only) head (schema + truncated preview of arrays/strings — middle ground) inline (schema + full body — costly; capped by PEEK_INLINE_BODY_CAP) auto (default — server picks based on byte thresholds) Reach for inline ONLY when body is known-small AND every field is needed; a 200KB JSON inlined is ~12K tokens of context for data you may never use.

Multipart uploads stream files via chunked transfer encoding (no Content-Length). Most servers accept this; some legacy proxies / primitive test servers reject it.

Cookbook: • Explore an unknown endpoint: http_request {method: "GET", url} → schema shows what is there http_read {cache_id, mask: ".data | map({id, name})"} • Top 10 GitHub issues by comment count: http_request {method: "GET", url: "https://api.github.com/repos/OWNER/REPO/issues"} http_read {cache_id, mask: "sort_by(-.comments)[:10] | .[] | {id, title, comments}"}

http_readA

Read a cached response body, optionally filtered through a jq mask. Tip: lead with length (e.g. mask: ".data | length") to learn the size before listing items. Required for binary bodies — pass save_to to stream the body to disk; binaries are never inlined into your context.

http_inspectA

Re-render the cached response schema in a different format (paths | shape | sample | json_schema) without making a second HTTP call. Try shape for nested structures, sample to see one realistic record, or json_schema for downstream typed pipelines.

server_infoA

Debug helper. No params. Returns the current mcp-peek version, runtime detection (npx | docker | unknown), cwd, files_root (PEEK_FILES_ROOT, or null when unset), and an effective_limits object summarising every configured cap / threshold / timeout (15 fields — see README for the full list). Use when a path is rejected unexpectedly, or to confirm which container/host the server is actually running in.

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/ed-smartass/mcp-peek'

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