TAAFT MCP Server
Officialby taaft
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Set to production for standalone deployment. | |
| TAAFT_API_KEY | No | API key for the internal TAAFT HTTP API, if required. | |
| PUBLIC_BASE_URL | No | External HTTPS origin for standalone deployment. Required when deploying the standalone server. | |
| TAAFT_SEARCH_PATH | No | Path used for the search endpoint. The adapter expects GET {TAAFT_SEARCH_PATH}?query=...&type=...&sort=...&limit=... | |
| TAAFT_API_BASE_URL | Yes | Base URL of the internal TAAFT HTTP API. Required to run the standalone Node.js server. | |
| TAAFT_TOOL_PATH_TEMPLATE | No | Path template used for the tool detail endpoint. The adapter replaces {slug} with the URL-encoded slug. |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues