Dappier MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DAPPIER_API_KEY | Yes | Your Dappier API key obtained from https://platform.dappier.com/profile/api-keys |
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 |
|---|---|
| dappier_real_time_searchB | |
| dappier_ai_recommendationsB | |
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: one fetches AI recommendations with various data models, the other performs real-time search. No overlap in functionality.
Both tools share the 'dappier_' prefix and use descriptive noun phrases ('ai_recommendations', 'real_time_search'), though the first uses underscores between words and the second uses a more compound adjective form, leading to minor inconsistency.
With only 2 tools, the server is very focused. For a purpose-built API covering recommendations and search, this number is reasonable though minimal. Slightly under the typical 3-15 range but not drastically.
The server covers its stated domains (recommendations and real-time search) adequately, but lacks tools for managing data models or retrieving raw content. It's sufficient for basic use but leaves out potential CRUD operations.