KingBuilds MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host to bind for HTTP transport | 0.0.0.0 |
| MCP_PORT | No | Port for HTTP transport | 8080 |
| ALLOWED_DIR | No | Sandbox directory for file operations | ./data |
| MCP_TRANSPORT | No | Transport mode: stdio or streamable-http | streamable-http |
| MAX_FILE_BYTES | No | Max file size for read/write operations | 1048576 |
| REQUEST_TIMEOUT | No | HTTP request timeout in seconds | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | Read a UTF-8 text file from within the server's sandboxed directory (/app). Path is relative to that directory. Refuses files above the configured size limit or outside the sandbox. |
| write_fileA | Write UTF-8 text to a file within the server's sandboxed directory (/app). Path is relative to that directory. Creates parent directories as needed; refuses to write outside the sandbox or above the configured size limit. |
| list_directoryA | List files and subdirectories within the server's sandboxed directory (/app). Path is relative to that directory ('' or '.' for the root). |
| scrape_web_pageA | Fetch a public web page and extract its content. Without |
| transform_dataA | Transform or aggregate tabular/record data. operation='convert' converts between JSON (array of objects) and CSV (requires output_format). operation in {sum, average, min, max, count, unique} aggregates a single |
| http_requestA | Make an authenticated HTTP request to a public API. The server attaches its own configured credential (bearer token or API key) — do not attempt to pass Authorization headers yourself, they will be ignored. GET/POST/PUT/PATCH/DELETE/HEAD supported. Blocks requests to private, loopback, link-local, and other non-public addresses, and re-validates every redirect hop. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: HTTP requests, directory listing, file reading, web scraping, data transformation, and file writing. No two tools overlap in purpose, making selection unambiguous.
Five of six tools follow a verb_noun pattern (list_directory, read_file, scrape_web_page, transform_data, write_file). http_request breaks the pattern as it is noun_noun, creating a minor inconsistency.
With six tools, the server offers a focused set covering file operations, web access, and data manipulation. The count is appropriate for the scope and doesn't feel sparse or bloated.
The set covers core capabilities: file read/write, directory listing, HTTP requests, web scraping, and data transformation. Missing operations like file deletion or appending are minor gaps given the sandboxed environment.