Agentify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level for the server. Supported values are 'debug', 'info', 'warn', and 'error'. | info |
| WEBHOOK_URL | No | Alternative environment variable for specifying the webhook notification URL. | |
| AGENTIFY_WEBHOOK_URL | No | The URL for webhook notifications. Used to track when AI starts and completes tasks with real-time delivery. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| task-startedB | Call this when you start any task, answer a question, or start work. |
| auto-task-trackerA | AUTOMATICALLY monitors task progress during long-running operations. Self-triggers every 10 seconds when: tasks run longer than 30 seconds, multiple tools are being used, or complex processing is detected. Updates progress without user prompting. |
| task-completedA | Call this when you finish any task, answer a question, or complete work. This tracks your activity and helps monitor progress. |
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 3 tools
Each tool has a distinct role: auto-task-tracker for automatic monitoring, task-started for initiating, and task-completed for finishing. No overlap.
All names use hyphens and are descriptive, but 'auto-task-tracker' is a noun phrase while 'task-started' and 'task-completed' are verb phrases, slightly inconsistent.
3 tools is minimal but reasonable for a simple task tracking server, covering the basic lifecycle without being too sparse.
Covers start, auto-tracking, and end. Missing manual progress updates or error states, but sufficient for basic automation.