FastApply MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_FILE_SIZE | No | Maximum file size in bytes | 10485760 |
| FAST_APPLY_URL | No | FastApply server URL | http://localhost:1234/v1 |
| FAST_APPLY_MODEL | No | FastApply model name | fastapply-1.5b |
| FAST_APPLY_TIMEOUT | No | Request timeout in seconds | 300.0 |
| FAST_APPLY_MAX_TOKENS | No | Maximum number of tokens for model responses | 8000 |
| FAST_APPLY_AUTO_BACKUP | No | Enable automatic backups before file modifications | False |
| FAST_APPLY_TEMPERATURE | No | Model temperature for response generation | 0.05 |
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 |
|---|---|
| list_toolsB | Return metadata for available tools. |
| call_toolC | Handle tool calls. |
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 2 tools
The two tools have clearly distinct purposes: call_tool handles tool execution, while list_tools provides metadata about available tools. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Both tools follow a consistent verb_noun naming pattern (call_tool and list_tools) with the same snake_case convention. This predictability aids in understanding and usage without any deviations.
With only 2 tools, this server feels thin and under-scoped for most practical applications. While it covers basic MCP functionality, it lacks domain-specific operations that would justify a dedicated server, making the count too low for effective agent use.
The tool surface is severely incomplete for any meaningful domain. It only provides meta-operations (calling and listing tools) without any actual functionality for a specific purpose, leaving obvious gaps that will cause agent failures in real-world tasks.