Merkl MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERKL_DEBUG | No | Enable debug logs by setting to 1 | 0 |
| MERKL_API_KEY | No | Bearer token for authenticated endpoints (optional) | |
| MERKL_BASE_URL | No | Base URL for the Merkl API | https://api.merkl.xyz |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-current-timestampC | Retrieves the current timestamp. |
| opportunities-searchC | This endpoint enables you to search for opportunities by providing specific criteria through query parameters. |
| opportunities-getD | GET /v4/opportunities/{id} |
| opportunities-campaignsD | GET /v4/opportunities/{id}/campaigns |
| opportunities-countC | GET /v4/opportunities/count |
| opportunities-bins-aprC | GET /v4/opportunities/bins/apr |
| opportunities-bins-tvlD | GET /v4/opportunities/bins/tvl |
| opportunities-aggregateD | GET /v4/opportunities/aggregate/{field} |
| opportunities-aggregate-maxD | GET /v4/opportunities/aggregate/max/{field} |
| opportunities-aggregate-minD | GET /v4/opportunities/aggregate/min/{field} |
| campaigns-searchC | This endpoint enables you to search for campaigns by providing specific criteria through query parameters. |
| campaigns-getD | GET /v4/campaigns/{id} |
| campaigns-countC | GET /v4/campaigns/count |
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 13 tools
Most tools are clearly separated by resource (campaigns vs opportunities) and action (search, get, count). The aggregate/max/min family is slightly overlapping in purpose, and get-current-timestamp is unrelated to the domain, but an agent can still distinguish the primary operations.
The set uses kebab-case consistently and mostly follows a predictable resource-action or resource-subresource-action pattern. The main deviation is get-current-timestamp, which reverses the verb-noun ordering used elsewhere.
With 13 tools, the server is well-scoped for a read-only API surface covering campaigns and opportunities. Each tool maps to a distinct query capability without excessive bloat.
The surface covers search, get, count, aggregation, and bin queries for opportunities, plus search/get/count for campaigns. It appears complete for a read-only API, though a few less-common query endpoints may still be missing.