Nefesh — Real Time Human State Awareness for AI vs Discourse MCP
In-depth architectural comparison of the Nefesh — Real Time Human State Awareness for AI and Discourse MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Nefesh — Real Time Human State Awareness for AI
Communication · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: No auth required
Discourse MCP
Communication · Local stdio
Quality: 81/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Nefesh — Real Time Human State Awareness for AI if you need specialized Communication tools running via a hosted cloud SSE transport. Choose Discourse MCP if your workspace requires Communication integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Nefesh — Real Time Human State Awareness for AI when:
You need dedicated capabilities in the Communication domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Fuses biometric signals into a stress score (0-100) for AI adaptation. MCP + A2A native.
Official Discourse MCP server for forum integration. Search topics, read posts, manage categories and tags, discover users, and interact with Discourse communities.
Nefesh — Real Time Human State Awareness for AI Tools (6)
request_api_key
Request a free API key. You MUST ask the user for their real email first. Do not invent or guess emails. The user receives a verification link they must click. Poll with `check_api_key_status` until ready.
check_api_key_status
Poll for API key activation using the same email the user provided. Returns `pending` or `ready` with API key.
get_human_state
Get stress state (0-100), `suggested_action` (maintain/simplify/de-escalate/pause), and `adaptation_effectiveness` — a closed-loop showing whether your previous action reduced stress.
ingest
Send biometric signals (heart rate, HRV, voice tone, expression, sentiment, 30+ fields) and get unified state back. Include `subject_id` for trigger memory.
get_trigger_memory
Get psychological trigger profile — which topics cause stress (active) and which have been resolved over time.
get_session_history
Get timestamped state history with trend (rising/falling/stable).
Discourse MCP Tools (16)
discourse_select_site
Validate and select a Discourse site. Returns JSON with site URL and title.
discourse_search
Search site content. Returns JSON object with results array of matching topics (id, slug, title) and meta (total, has_more).
discourse_filter_topics
Discover topics through a filtered, top, or hot view. Filtered uses Discourse TopicsFilter syntax; top uses Discourse's authoritative top score and defaults to weekly; hot is defined exactly as daily top (not sentiment, controversy, or real-time velocity). Returns a uniform rich topic projection and truthful pagination metadata.
discourse_read_topic
Read topic metadata and posts. Large post limits can require multiple upstream requests. For moderation queues, prefer reviewable list/detail evidence instead of fanning this tool out across flagged topics.
discourse_read_post
Read a specific post. Returns JSON with id, topic_id, post_number, username, created_at, and raw content.
discourse_read_topic_posts
Read exact, earliest, latest, around-post, or username-filtered topic evidence. Selection is bounded to 50 posts and reports the visible stream size without claiming the entire topic was loaded.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Nefesh — Real Time Human State Awareness for AI Configuration
Nefesh — Real Time Human State Awareness for AI is categorized under Communication and uses a remote streaming HTTP/SSE transport. In contrast, Discourse MCP belongs to Communication using local stdio subprocess. Select Nefesh — Real Time Human State Awareness for AI when you need capabilities focused on communication and Discourse MCP when you require tools for communication.
Search post-level evidence with Discourse query syntax. Unlike discourse_search, this preserves matched posts, highlighted blurbs, authors, topics, categories, and truthful bounded continuation. This is keyword search, not Discourse AI semantic search.
discourse_get_user
Get user info. Returns JSON with id, username, name, trust_level, created_at, bio, admin, and moderator.
discourse_list_user_posts
Get paginated list of user posts/replies. Returns JSON object with posts array (id, topic_id, post_number, slug, title, created_at, excerpt, category_id) and meta (page, limit, has_more).
discourse_list_users
List users via admin API. Requires admin API key. Returns ~100 users per page (Discourse's fixed page size). Returns JSON with users array and pagination meta.
discourse_get_chat_messages
Get messages from a chat channel. Returns JSON object with channel_id, messages array (id, username, created_at, message, edited, thread_id, in_reply_to_id), and meta.
discourse_get_draft
Retrieve a specific draft by key. Returns JSON with draft_key, sequence, and parsed data (title, reply, categoryId, tags, action).