FastApply MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Server host binding | localhost |
| PORT | No | Server port | 8000 |
| DEBUG | No | Debug mode | false |
| LOG_LEVEL | No | Logging verbosity | INFO |
| CACHE_SIZE | No | Cache entry limit | 1000 |
| QDRANT_URL | No | Qdrant vector database | http://localhost:6333 |
| MAX_FILE_SIZE | No | 10MB file limit | 10485760 |
| FAST_APPLY_URL | No | Your FastApply server URL | http://localhost:1234/v1 |
| OPENAI_API_KEY | No | OpenAI integration | |
| QDRANT_API_KEY | No | Qdrant API key | |
| WORKSPACE_ROOT | No | Workspace confinement | |
| TIMEOUT_SECONDS | No | Operation timeout | 30 |
| FAST_APPLY_MODEL | No | Model identifier | fastapply-1.5b |
| ALLOWED_EXTENSIONS | No | Allowed file extensions | .py,.js,.ts,.jsx,.tsx,.md,.json,.yaml,.yml |
| FAST_APPLY_API_KEY | No | API key if required | |
| FAST_APPLY_TIMEOUT | No | Request timeout | 30.0 |
| FAST_APPLY_MAX_TOKENS | No | Response token limit | 8000 |
| FAST_APPLY_TEMPERATURE | No | Model consistency | 0.05 |
| FAST_APPLY_STRICT_PATHS | No | Path validation | 1 |
| MAX_CONCURRENT_OPERATIONS | No | Concurrent operations | 4 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_toolsB | Return metadata for all exposed tools (unified mode). |
| call_toolC | Handle tool calls with unified branching and robust safety checks. |
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 completely distinct purposes: call_tool handles tool execution with safety features, while list_tools provides metadata about available tools. There is no overlap in functionality, making them easily distinguishable.
Both tools follow a consistent verb_noun pattern (call_tool, list_tools) with clear, descriptive names. The naming convention is uniform throughout the set, making it predictable and easy to understand.
With only 2 tools, this server feels under-scoped for a general-purpose 'FastApply MCP Server'. The name suggests broader functionality, but the minimal tool set may limit agent capabilities in handling diverse tasks, indicating a potential mismatch with the implied scope.
Given the server name 'FastApply MCP Server', which implies application or deployment-related operations, the tool set is severely incomplete. It lacks core operations like applying configurations, managing resources, or handling deployments, leaving significant gaps for the domain it appears to target.