Trefle
Server Details
Trefle MCP — global plant database (1M+ species)
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-trefle
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 19 of 19 tools scored. Lowest: 2.9/5.
The server mixes plant tools with a large set of Pipeworx data tools. The catch-all 'ask_pipeworx' overlaps with many specific tools like 'validate_claim' and 'compare_entities', making it unclear which tool an agent should use. Plant tools are distinct but coexist with unrelated tools, causing ambiguity.
Tool names use mixed conventions: snake_case verbs (ask_pipeworx, compare_entities), single verbs (forget, recall, remember), and noun_noun compounds (entity_profile, polymarket_arbitrage). No consistent pattern is followed, reducing predictability.
With 19 tools spanning two unrelated domains (plant data and Pipeworx data query), the server is overburdened. The plant domain has only 5 tools, while the Pipeworx domain adds 14, making the set feel bloated and unfocused for a server named 'Trefle'.
For the plant domain, the tools cover search and retrieval reasonably well, but miss common operations like filtering or listing all plants. The Pipeworx tools are extensive but include meta-tools (e.g., 'discover_tools') that indicate an incomplete surface. Overall, the server's dual purpose leaves gaps in both areas.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!