AiDD MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| connectB | Connect to AiDD account via browser authentication |
| disconnectB | Disconnect from AiDD account |
| statusB | Check authentication status |
| start_workflowC | Start the AiDD workflow |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: connect and disconnect handle authentication lifecycle, start_workflow initiates the core functionality, and status checks the current state. There is no ambiguity between these four operations.
All tools follow a consistent verb-based naming pattern (connect, disconnect, start_workflow, status) using snake_case throughout. The naming is predictable and readable without any deviations in style.
With 4 tools, this server is well-scoped for its apparent authentication and workflow management domain. Each tool earns its place, providing essential operations without bloat or missing elements for a minimal viable surface.
The toolset covers the core authentication lifecycle (connect, disconnect, status) and workflow initiation (start_workflow), which is complete for a basic interface. A minor gap exists in lacking tools for managing workflows after starting (e.g., stop, monitor, or list workflows), but agents can likely work with this minimal set.