MIND is listed as active in the registry but did not answer our last check. 711 installs a week from npm. It exposes 31 tools. Last commit 28 Oct 2026.
MIND knowledge-graph memory for agents. 44 tools: CRM, Life, MoneyMIND, Budget, Sheets, Email, Sign.
Installs per day
peak 384 · avg 34 · +571% w/w
a month agotoday
Uptime history
61 days of history · worst day 0%
61 days agonow
0.0%
Uptime 24h
0 of 91 checks
31
Tools
read from the server
116 ms
Response time
average over 24h
711
Installs / week
npm and PyPI
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.
8 Sep
a tool changed version
What the code does
We read the source, 4 d ago · tools taken from the live server · rules 995398eba69f
Capabilities
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
Touches key and credential files
src/integration-guide.ts:23
- Secrets. Never upload \`.env\` or \`.env.*\`, \`*.pem\`, \`*.p12\`, \`*.key\`, \`id_rsa\`/\`id_ed25519\` and siblings, \`credentials*\`, \`service-account*\`, \`secrets*\`, \`*.keychain\`, or any file whose contents match a credential pattern (\`sk-\`, \`ghp_\`, \`AKIA\`, \`BEG…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
run in your terminal
claude mcp add mind --transport http https://www.m-i-n-d.ai/mcpSettings → Connectors → Add custom connector, then paste this address
https://www.m-i-n-d.ai/mcp~/.codex/config.toml
[mcp_servers.mind]
url = "https://www.m-i-n-d.ai/mcp".cursor/mcp.json
{
"mcpServers": {
"mind": {
"url": "https://www.m-i-n-d.ai/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"mind": {
"type": "http",
"url": "https://www.m-i-n-d.ai/mcp"
}
}
}Available tools 31
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
mind
mind_accounts
Manage multi-MIND accounts. A 'MIND' is a knowledge-graph account; one person can own or be granted access to many. Use to discover every MIND you can access (list), spin up a new one (create), permanently delete one (delete), see who can access a MIND (members), grant an existing user access (grant), or email an invitation (invite).
mind_admin
Admin-only tool for managing MIND users and the Featured Minds Portal. Requires an admin API key. Full CRUD over featured minds (create / list / get_full / update / update_owner_profile / reorder / delete), plus user provisioning and tier/credit management. The Featured Minds Portal at /admin/featuredmindsportal uses these same endpoints — get_featured_mind_full + update_featured_mind_owner_profile let you edit the linked user's LLM model, public chat prompt, temperature, reasoning effort, brand fields, and avatar/banner from any MCP client.
mind_agents
Admin-only Agent Command Center — canonical registry of every Astra AI agent (running on VPS, planned, archived). Query before scaffolding a new agent. Update status / current_job / responsibilities after non-trivial work. Every agent is owned by a MIND account (owner_username) and can be transferred or shared with other accounts as owner/viewer. Backed by /admin/agents on the MIND backend; admin API key required.
mind_automate
Create and manage automations in MIND — scheduled workflows, event triggers, and rules that run automatically. Connect CRM events to actions, schedule recurring tasks, and build custom pipelines.
mind_bootstrap_templates
Seed all 16 MIND Front Layer templates into this MIND tenant as system documents. After running, the templates become queryable through mind_query so agents can ask 'what should I fill out for SOUL?' and retrieve the spec from their own knowledge graph. Idempotent — re-runs create fresh copies. Run once per new tenant.
mind_context
Get your persistent context from MIND — identity, preferences, rules, and recent activity. Call this at the start of every session to know who you are, who the user is, and what matters right now.
mind_crm
Manage contacts and relationships in MIND CRM. Use for tracking people, companies, leads, interaction history, and activity logging.
mind_focuses
Manage Focuses — the top-level buckets that group Life Projects. Every project lives inside one focus (or 'No Focus'). Use list to see all focuses + their project counts, create to add a new bucket (e.g. 'Astra', 'Atlas', 'Fundraising'), update/delete to maintain them. Pass the returned focus_id to mind_life when creating projects.
mind_folder_routes
Configure deterministic system-folder routing — which folder each kind of system-generated doc (life items, CRM, chat saves, tasks, training, reasoning trajectories, playbooks, trader signals, cloud imports) is filed into automatically. Actions: list, set, clear, apply_recommended (idempotent one-tap setup that creates Life/CRM/Chats/Reasoning/Trader folders and wires every source_type to its destination). User uploads are unaffected — this is system writes only.
mind_folder_suggest
Ask MIND which folder a piece of content belongs in. Reads every folder's routing_hint (set via mind_folders set_hint) and uses a cheap LLM to pick the best match. Returns folder_id=null when no folder's hint clearly applies — in that case leave the doc unfiled rather than guess. Typical agent flow: suggest → mind_remember (create the doc) → mind_folders move_documents (file it to the suggested folder).
mind_folders
Organize your MIND documents into folders. Folders are a presentation layer — the knowledge graph still indexes and retrieves across every document regardless of folder. Use mind_remember to create a document, then mind_folders move_documents to file it. Actions: list, create, rename, move, delete, move_documents, set_hint (set the agent-routing hint read by mind_folder_suggest).
mind_get_template
Fetch the full augmented markdown for one MIND Front Layer template. Returns a self-contained spec — when to create a document of this type, what slots to fill, and how to store the filled copy. Always read the template before writing a typed document.
mind_graph
Get MIND knowledge graph statistics, diagnostics, and label details. Use to check graph health, growth, and entity breakdown.
mind_insights
Access insights from MIND's Autonomous Learning Engine — patterns detected in your knowledge graph, weekly summaries, and proactive intelligence. Also trigger on-demand analysis.
mind_life
Manage Focus → Project → Outcome hierarchy + calendar in MIND Life. Items are either projects (top-level domain/client buckets that live inside a Focus) or outcomes (deliverables that live under a parent project). Use `item_type` + `parent_id` + `focus_id` on create/update to wire the hierarchy. Use list filters (item_type, parent_id, focus_id, top_level_only) to slice the board. Share a project with another MIND account using share/list_shares/revoke_share (requires LIFE_SHARING_ENABLED on the backend; grantee gets the project + its outcomes on their board).
mind_list_templates
List the 16 MIND Front Layer template types (SOUL, IDENTITY, BELIEFS, USER, AGENTS, TOOLS, SENSES, SKILLS, BEHAVIOR, LESSON, DECISION, POLICY, WORKFLOW, PREFERENCE, GOAL, RELATIONSHIP). Use this first to see what typed documents an agent can fill in. Each entry includes a short description and the source_tag used when storing filled documents.
mind_notify
Read and manage MIND notifications — alerts, reminders, insight notifications, and system messages.
mind_osint
Operate Ozzie — the autonomous OSINT analyst — through MIND. Investigate a target (domain, IP, org, person) and get a cited intelligence dossier; or set up live-feed alerts and watchlists in plain English. Ozzie's dossiers and alerts persist in its MIND knowledge graph, so use mind_query to recall past intelligence and mind_osint to run new work.
mind_personas
Influencer Factory Command Center — synthetic-persona creators that publish across Blotato platforms. Admin-only. Phase 1 surface: persona CRUD (auto-creates a Featured MIND row with IF fields), face anchor (AI-generate via Nano Banana Pro OR user-uploaded with rights affirmation), face variants (image-to-image via n8n + Fal.ai, always pinned to anchor — never chained), voice (ElevenLabs library search + clone + sample), per-platform bios (with optional LLM draft), Blotato account registration (YouTube/IG/LinkedIn/X/Threads/Pinterest; TikTok marked manual_upload). Each persona is publicly chattable at /m/{username} via its linked Featured MIND.
mind_profile
Manage your MIND profile, AI prompt settings, and model preferences. Update your bio, set custom system prompts for chat and thought generation, and choose your preferred LLM model.
mind_query
Search your MIND knowledge graph. Returns AI-synthesized answer from your stored documents, entries, and feed posts. Use this BEFORE making decisions — MIND is your memory.
mind_remember
Store and manage content in your MIND knowledge graph. Use for facts, decisions, learnings, research, notes — anything worth remembering. Auto-categorized. Always log outcomes here after completing tasks. Supports create (default), delete, search, get, and list.
⚠️ PRIVATE vs PUBLIC: `document` and `entry` are PRIVATE to the user's knowledge graph. `feed_post` is a PUBLIC social-media post that appears on the user's public feed for everyone to see. Default to `entry` for all agent outcomes, logs, decisions, and research. NEVER use `feed_post` unless the user explicitly says "post", "share", "tweet", "feed", or "thought to my feed" — deploy logs, PR notes, work outcomes, and agent activity belong in `entry`, NOT on the public feed.
mind_research
Launch and manage deep research jobs. Research runs autonomously — it gathers information, analyzes it, and stores findings in the knowledge graph. Use for competitive analysis, market research, technical deep-dives.
mind_save_typed
Save a filled-out Front Layer document with the proper type tag so retrieval can filter by it later. Wraps mind document creation and pre-bakes the source tag (`front-layer-<type>`). Use this — not raw mind_remember — for any SOUL/IDENTITY/BELIEFS/USER/BEHAVIOR/LESSON/POLICY/etc. document. Pass the markdown body (frontmatter + content) as the `content` field.
mind_sense
Access MINDsense emotional intelligence — the user's living emotional state, signal history, emotional timeline, and KG entity weights. Use this to understand how the user is feeling and what emotionally significant events have occurred.
mind_share
Share a MIND document via a public link (like sharing a claude.ai artifact, but the doc lives in MIND). Create returns a share_url anyone can open — HTML docs render fully interactive. Supports expiry (expires_in_days), password protection, per-recipient grants, view counts, and revocation.
mind_social
Interact with MIND's social layer — create thoughts (PUBLIC feed posts), browse the feed, manage communities, and engage with other users' content. ⚠️ create_thought posts to the user's PUBLIC social feed for everyone to see — NEVER call unless the user explicitly said "post", "share", "tweet", "feed", or "thought to my feed". For private agent outcomes, deploy logs, or work updates, use mind_remember with type=entry instead.
mind_social_analytics
Read social media analytics from MIND's Social Dashboard — YouTube/LinkedIn/X/Twitch channel stats, recent videos with performance, retention curves, traffic sources, comment sentiment, and goal progress. Use this to answer questions like 'how did Tuesday's video do?' or 'am I on pace for 1k subs?'
mind_tasks
Manage site-wide tasks in MIND — assignable, completable, reportable work items. A task can attach to a Life project (parent_type=life_item), a CRM contact (parent_type=contact), an agent (parent_type=agent), or stand alone. Assign tasks to a MIND member, an agent, or an external email. Use action=reports for completion analytics.
mind_tickets
Agent ticket queue — file, view, answer, triage, and resolve tickets on any agent in the Command Center. A ticket is client feedback / critique / an idea / a feature request / a bug. Every ticket lives on an agent (agent_slug is always required) and auto-assigns to the Ernie triage agent. Use action=create to file one, action=comment to answer a thread, action=update or action=resolve to triage. Backed by /admin/agents/{slug}/tickets; admin API key required.
mind_train
Train MIND's knowledge graph. Start guided training sessions to teach it about yourself, or save existing chat conversations into the knowledge graph for persistent memory.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://www.m-i-n-d.ai/mcp | streamable-http | answering | 116 ms | 10 min ago |
Alternatives to MIND
same job, measured the same wayNysa
by usenysa
Shared memory for teams that work with AI agents: meetings, email and calendar in one brain.
Agentcomms
by cloudcorprecords
Agent email, agent-to-agent messaging, and cloud file storage for AI agents.
Known
by known
Shared memory for teams: every AI agent works from your company's knowledge, decisions and history.
OpenMail
by openmail
Gmail for agents: create inboxes, read and reply to mail, send email, manage domains. OAuth sign-in.
MailByGet
by mailbyget
Temporary receive-only email inboxes for agents. Create, list and read messages without signup.
Superpowers
by superpowers
Pay-per-call tools for agents: search, page reading, emails, company data, media. Sign in, no key
Lycatra
by lycatra
Connect agents to Lycatra knowledge, memory, collaboration, schedules, notifications, and teams.
Commune
by shanjai-raj
Email and SMS MCP server for AI agents — 41 tools for inboxes, sending, search, and SMS.
MIND — questions
Answers built from our own checks of this server.
What can MIND do?
It exposes 31 tools, read directly from the server on our last check. Among them: mind_accounts, mind_admin, mind_agents, mind_automate, mind_bootstrap_templates, mind_context and 25 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is MIND working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 116 ms. The bar chart above shows every period we have measured.
The registry lists MIND as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect MIND?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MIND need an API key?
No. MIND completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 31 of them are readable on this page. This is what we observed, not what the docs claim.
How many people use MIND?
The npm package @astramindapp/mcp-server was installed 711 times in the last week. Week over week that is +571%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is MIND open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 7 stars on GitHub. The licence covers the code in the repository, not the hosted service at m-i-n-d.ai, which runs on its operator's own terms.