agentminds-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTMINDS_API_KEY | No | API key for connecting to AgentMinds. Required for push/connect on registered sites. | |
| AGENTMINDS_API_URL | No | Base URL for the AgentMinds API. | https://api.agentminds.dev |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agentminds_connectA | Connect to AgentMinds Central — fully automatic. CRITICAL RULES:
If no key: register first, then push data, then get recommendations. If has key: push data → get recommendations. Before calling this, collect DETAILED agent data from this project:
|
| agentminds_pushA | Push detailed agent data to AgentMinds Central. IMPORTANT: Send FULL data, not just names and scores. Each agent report MUST include:
The MORE detail you send, the BETTER recommendations you get back. Empty data = empty recommendations. Example: {agent: "lead_hunter", report: {severity: "warning", summary: "567 leads found but 0% open rate", metrics: {total_leads: 567, emails_found: 230, open_rate: 0, bounce_rate: 8.3}, warnings: [{severity: "critical", message: "0% email open rate - emails likely going to spam"}], recommendations: [{title: "Warm up email domain before bulk sending", priority: "critical"}]}, memory: {learned_patterns: [{pattern: "cold_email_spam", category: "email_deliverability", confidence: 0.9, status: "active", impact: "critical", detail: "Bulk cold emails without domain warmup go to spam"}]}} |
| agentminds_actionsA | Get action plan — ONLY works if you already pushed data. If no data was pushed, this returns nothing. DO NOT fabricate recommendations. Show only what this tool returns. |
| agentminds_agent_detailA | Get detailed info about a specific agent — metrics, warnings, patterns, recommendations. Use when user asks about a specific agent like 'health agent ne diyor?', 'security durumu'. |
| agentminds_site_overviewA | Get full overview of your site — all agents, their status, scores. Use when user asks 'site durumu', 'genel durum', 'tüm agentları göster'. |
| agentminds_statusA | Check AgentMinds Central system health — is the server up, any alerts, circuit breakers. Use when user asks 'sistem durumu', 'AgentMinds çalışıyor mu?'. |
| agentminds_registerA | Register a new site with AgentMinds Central. Returns API key. Use when user says 'kayıt ol', 'register', 'yeni site ekle'. |
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 7 tools
Each tool has a clearly distinct purpose: registration, data pushing, overviews, agent details, actions, connection, and status. No overlap or ambiguity.
All tools follow a consistent 'agentminds_' prefix with lower_snake_case naming pattern, making them predictable and easy to distinguish.
Seven tools is well-scoped for the AgentMinds domain; each tool serves a necessary function without redundancy or excess.
The tool surface covers the full lifecycle: registration, data pushing, individual and overview queries, recommendations, and system health. No obvious gaps.