Run your NeoMind AI team (https://neomindhub.com) from any MCP client: get briefings, review leads and customer enquiries, ask any AI teammate, and approve or reject their work. OAuth with a NeoMind account.
Scored across 11 tools
Each tool has a clearly distinct purpose: approval actions (list/get/approve/reject), conversation reading, lead listing and do-not-contact, teammate listing/messaging, and a summary briefing. get_briefing aggregates information, but its description clearly positions it as a starting summary while the specific list tools provide detail, so overlap is minimal.
All tools use consistent snake_case verb_noun naming, with predictable verbs such as get_, list_, approve_, reject_, ask_, and mark_. The longer mark_lead_do_not_contact name still follows the same pattern.
Eleven tools is a well-scoped size for a business-owner AI assistant covering briefings, approvals, conversations, leads, and teammates. Each tool appears to earn its place without excessive fragmentation.
The approval lifecycle is fully covered with list, read, approve, and reject operations, and the surface covers briefings, leads, conversations, and teammates. Minor gaps exist around leads and conversations being mostly read-only, with no lead detail/update beyond do-not-contact and no direct conversation reply.
Approve one item your AI team prepared — this carries it out (it may publish a post, send an email to a customer, or change the owner's website). First read it with get_item and show the owner what it says; only call once they have clearly said to approve it, passing the contentHash get_item gave. Only the business owner's connection can do this.
Inputs: id (required), contentHash.
Send a message to one of your AI teammates (by key, from list_teammates) and get their reply. It lands in the same conversation the owner sees in NeoMind, so they can carry on there. Pass session_id only to continue a specific earlier conversation.
Inputs: message (required), teammate (required), session_id.
Catch up on your business: what your AI team did, what needs you (problems, work waiting for approval), and new customer enquiries and leads since a given number of hours ago (default 24). Start here when the owner asks what's happening.
Inputs: since_hours.
Read the transcript of one customer enquiry, in order, by its id (from list_conversations or get_briefing). Long conversations show the most recent 60 messages, with a link to the rest.
Inputs: id (required).
Read one item your AI team prepared, in full — exactly what approving it would publish, send or change — with the contentHash approve_item needs. Show the owner what it says before approving it.
Inputs: id (required).
List recent customer enquiries — the conversations your AI receptionist and phone agent had with customers on your website, phone and messaging — newest first. Use get_conversation with an id to read the full transcript.
Inputs: limit, offset.
List the leads your AI team captured (name, contact details, what they want, status), newest first. Filter by status, search text (name, email or phone) or a captured-date range.
Inputs: q, to, from, limit, +2 more.
List the work your AI teammates have prepared that is waiting for you to approve or reject: social posts, replies, emails, website changes, articles and content calendars. Each item shows what it says, what approving it would do, its id (for approve_item / reject_item) and a link to open it in NeoMind. Read an item in full with get_item before approving it.
Inputs: limit.
List the AI teammates on your NeoMind team — who they are and what each one does. Each teammate's key is what ask_teammate takes.
Inputs: no named parameters.
Mark one lead as do-not-contact, by lead id (from list_leads): your AI team will never follow them up again, and any follow-up waiting for them is dismissed. Only call when the owner has said so. Only the business owner's connection can do this.
Inputs: id (required).
Reject (dismiss) one item your AI team prepared, by id, so it doesn't go ahead. Only call when the owner has said to reject it. Only the business owner's connection can do this.
Inputs: id (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.