The Model Context Protocol (MCP) enables AI models to interact with your local Momentic tests via the desktop server. This allows AI assistants in various IDEs to understand, create, and modify your test suites directly.
MCP is currently publicly available for the Momentic local app as of version 2.17.1 (recommended Momentic >= 2.17.2).

​
Overview

The MCP server provides AI models with access to your Momentic project through a set of specialized tools. These tools allow AI assistants to:
  • Browse and understand your test structure
  • Create new tests with AI assistance
  • Edit existing tests using natural language
  • Manage test environments and configurations
  • Access test and module information

​
Before you start

Local only: The desktop MCP server runs on your machine so remember to run the momentic application before trying to connect to the MCP server.IDE support: Use an editor that supports MCP (e.g., Cursor, Windsurf, Claude Desktop, Codex, VS Code/Copilot).Project configured: Ensure your project has a valid momentic.config.yaml

​
Step 1: Enable the MCP server

We support two different transport protocols currently on localhost:
  1. SSE Transport: Available in any version Momentic >= 2.17.1 
    GET /api/mcp/sse
POST /api/mcp/sse?sessionId=<session-id>
url: http://localhost:58888/api/mcp/sse
  2. Streamable HTTP Transport (newer standard): available in any version Momentic >= 2.17.2 
    POST/GET/DELETE /api/mcp/
Header: mcp-session-id: <session-id>
url: http://localhost:58888/api/mcp
New features will be aimed at the Streamable HTTP standard but we will continue to support SSE for legacy versions of IDEs.

​
Step 2: Set up your MCP client

Make sure you have started the Momentic Application: 
npx momentic@latest app
Follow the steps for your IDE below.
Example configuration (used in Cursor as of 2025‑09‑19). This is an example and may not work universally across VS Code–branched IDEs.
{
  "mcpServers": {
    "momentic-desktop": {
      "url": "http://localhost:58888/api/mcp"
    }
  }
}
Setup Steps:
  1. Open Cursor’s command palette (Cmd Shift P)
  2. Navigate to “View: Open MCP Settings” command
  3. Add the momentic-mcp
  4. Restart the MCP server

​
Step 3: Use tools in your IDE

  • Verify you have started the Momentic application
  • Verify the MCP server appears in your IDE (e.g., Copilot Agent mode → Tools)
  • Try a simple action (e.g., list tests) to confirm connectivity
  • If tools don’t appear, restart both the IDE and the Momentic desktop server
NOTE: Several IDEs only provide support for MCP in agent mode

​
Security considerations

  • Local Only: The MCP server is designed for local development only
  • No Authentication: Currently no authentication is required for local access
  • Session Management: Sessions are automatically cleaned up on disconnection
  • Resource Access: MCP tools have access to your local file system and project data

​
Example Usage:

​
Best practices

  1. Start Desktop Server: Always start your Momentic app before connecting MCP
  2. Project Context: Ensure you’re in the correct project directory
  3. Prompting: While you will see success with unclear directions of how to edit a test, using step by step descriptions will yield faster test edit times and steps closer to exactly what you are envisioning. We suggest keeping the amount of steps per edit_test tool call under 10.
  4. Session Management: Allow sessions to clean up properly by disconnecting cleanly
  5. Tool Safety: All of our tools other than edit test currently cannot do any harm or changes to your project (file creation or read only). Enabling these to auto run is safe. If you use the momentic_edit_test tool be sure you have tracked your changes to the test file it is editing as it will not ask you for permission for each change.

​
Available Tools

​
Environment Tools

List environments defined in the project’s momentic.config.yaml file.Usage: Returns a JSON array of all configured environments with their settings and configurations.Parameters: NoneExample: momentic_environment_list - Returns all available test environments

​
Module Tools

List all modules in your project.Usage: Returns detailed information about each module including ID, name, description, file paths, and metadata.Parameters: NoneExample: momentic_module_list - Returns all project modules

​
Test Tools

List all tests in your project.Usage: Returns comprehensive test information including metadata, labels, and file paths.Parameters: NoneExample: momentic_test_list - Returns all project tests