leafengines MCP Server

🌱 Agricultural AI: Soil analysis, crop recommendations, weather forecasts. FREE TurboQuant.

Publisher claimed. No tool list reported, and Pod has not connected to this server.

Status

Pod has not dialled leafengines yet, so everything on this page is what its publisher reported rather than what we observed. Registries describe servers; they do not connect to them. Until a check runs, treat the tool list below as a claim.

Connect

Published as @ancientwhispers54/leafengines-mcp-server on npm. Runs locally.

Known issues

28 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded — those are release checklists and internal refactors, not things that will go wrong for you. Showing 12.

Most discussed

[D1] Wire telegram-webhook to telegram_query_signals ingestion pipeline

D1 Complete ✓

Summary

telegram-webhook now logs every command invocation to public.telegram_query_signals with full metadata (user_hash, tier, command, tool_name, fips_code, state_code, county_name, response_success, latency_ms). Downstream triggers populate bigfoot_autogen_queue and correlation_edges automatically.

Fixes Applied

logQuerySignal() added to telegram-webhook/index.ts (13 call sites)
await added to logQuerySignal calls so Supabase isolate doesn't te

Read the thread · 2026-07-13 · closed · 0 comments

Implement Slack interactive commands: /soil, /crop, /onboard, /summary

Port core Telegram commands to Slack slash commands with Slack-appropriate UX.

Commands:

/soil <county> — Soil analysis, rich block with soil map image
/crop <county> — Crop suitability, bulleted recommendation list
/onboard — 3-step onboarding, ephemeral flow with 'Next' button
/summary — Usage + milestone, progress bar block + milestone emoji
/link — Link identity, modal with API key input
/recent — Saved sessions, dropdown of recent sessions

*Interaction model:

Read the thread · 2026-06-18 · open · 0 comments

Route n8n leafEnginesNotify alerts to Slack (not just Telegram)

Expand the n8n notification node to support Slack alongside the existing Telegram/email fallbacks.

Changes:

leafEnginesNotify node: add channel: slack option
Payload fields: slack_webhook_url, slack_channel, message_blocks (rich formatting)
Frost alerts, soil anomalies, and water quality breaches trigger Slack messages
Fallback chain: Slack -> Telegram -> Email (ordered by user preference)

Rich Slack formatting:

Use Block Kit for actionable alerts (e.g., 'View Detai

Read the thread · 2026-06-18 · open · 0 comments

Enable team pooling via shared API key in Slack channels

Support shared team API keys in Slack group channels. A single Team API key can be shared by 3-5 people with pooled daily limits.

Implementation:

Detect group channel context (not DM) in Slack message handler
If channel has a configured team key, route all queries through that key
Pool limits: 150 AI calls + 500 data calls per day across the team
/soil and other commands work in group channels with team accountability
Log slack_channel_id in telemetry for audit

Security:

Read the thread · 2026-06-18 · open · 0 comments

Add analysis_sessions continuity for Slack -> cross-platform bookmarking

Enable Slack users to access saved analysis sessions started on other platforms.

Commands to implement:

/recent — last 5 saved sessions across all channels
/deepdive [session_id] — retrieve full multi-turn analysis
/favorites — user-bookmarked sessions (starred)

Data model:

analysis_sessions table already exists; add channel_source enum (telegram, slack, mcp, web)
Add slack_thread_ts column for Slack thread continuity

Acceptance:

User starts soil an

Read the thread · 2026-06-18 · open · 0 comments