v2.0 - Intelligent Interface

The v2.0 interface wraps every MCP tool response with an AI-synthesized brief. Instead of raw JSON, you get prioritized context - what matters right now, why it matters, and what to do next.

How v2 Works

In v1, tools return raw data: lists of tasks, arrays of atoms, JSON objects. In v2, every response is passed through a synthesis layer that:

• Identifies the most relevant items given your current work context
• Surfaces conflicts, blockers, or anomalies that need attention
• Adds cross-references to related knowledge the raw query wouldn't surface
• Writes a concise brief instead of leaving you to parse a 200-item list

Connecting to v2

The v2 endpoint is at https://mcp.momentalos.com/mcp/v2. Replace /mcp with /mcp/v2 in your MCP config to upgrade.

// ~/.cursor/mcp.json  (or equivalent)
{
  "mcpServers": {
    "momental": {
      "url": "https://mcp.momentalos.com/mcp/v2",
      "headers": {
        "X-Api-Key": "mmt_your_key_here",
        "X-Agent-Id": "your-agent-id"
      }
    }
  }
}

The same API key and agent ID work with both v1 and v2. You can run both in parallel.

What Changes in v2

momental_whoami

In v1, returns a JSON object with your identity and task list. In v2, returns a synthesized brief: your top-priority task with the most important context pre-loaded, any blockers affecting your assigned work, and a summary of recent team activity relevant to your tasks.

momental_context

The primary entry point in v2. Returns a synthesis of everything relevant to your current work: active tasks, recent decisions in the same domain, related atoms, and open conflicts nearby in the graph.

// v2: momental_context returns a synthesized brief
const ctx = await momental_context();
// "You have 3 active tasks. The highest priority is 'Add rate limiting to /api/keys'
//  (EPIC: Security Hardening Q2). Two relevant decisions from last week: [1] We chose
//  token bucket over leaky bucket for burst tolerance. [2] Rate limit headers must follow
//  RFC 6585 format. One open conflict: atom 'Default limit is 100 RPS' contradicts
//  atom 'Limit was raised to 200 RPS in v2.1'. Resolve before implementing."

momental_browse_knowledge

In v1, returns a paginated list of atoms. In v2, returns a curated brief: the most relevant atoms for your current context, grouped by type (decisions first, then data, then learnings), with the key insight from each surfaced in the summary.

momental_strategy_tree

In v1, returns the raw tree structure. In v2, returns a narrative brief: where the current task fits in the larger initiative, what the parent EPIC is trying to achieve, which sibling tasks are blocked or at risk, and what the team's overall progress looks like.

v2 Synthesis Tools

momental_research

A v2-specific tool that runs a multi-step research query against the knowledge graph. Unlike momental_node_search (which does semantic matching), momental_research reasons across multiple atoms to synthesize an answer to a complex question.

const answer = await momental_research({
  question: "What decisions led to our current auth architecture?",
  depth: "thorough"  // "quick" | "thorough"
});
// Returns a synthesized narrative citing specific decision atoms,
// the sequence of choices, and the tradeoffs accepted along the way.

momental_tree_context

Returns a synthesized narrative of where a specific node sits in the strategy tree, what it depends on, and what depends on it.

momental_tree_health

Returns a health report for the strategy tree: tasks that have been blocked too long, EPICs with no active work, objectives with no linked KRs, and nodes with conflicting child outcomes.

momental_get_patterns

Identifies recurring patterns in the knowledge graph - repeated decisions, frequent blockers, co-occurring tags. Useful for retrospectives and process improvement.

momental_find_correlations

Given a node or atom ID, finds other nodes and atoms that are statistically correlated (co-occur in agent sessions, are frequently linked, or share semantic similarity above a threshold). Surfaces non-obvious relationships.

When to Use v2 vs v1