MCP

​

Overview

• 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

​

Step 1: Enable the MCP server

1. SSE Transport: Available in any version Momentic >= 2.17.1
   Copy

   Ask AI

   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
   Copy

   Ask AI

   POST/GET/DELETE /api/mcp/
   Header: mcp-session-id: <session-id>
   url: http://localhost:58888/api/mcp
   

​

Step 2: Set up your MCP client

{
  "mcpServers": {
    "momentic-desktop": {
      "url": "http://localhost:58888/api/mcp"
    }
  }
}

​

Step 3: Agent Rules

// Use this one if you want to have the agent ask you before edits
Never directly edit a Momentic test or module YAML file, only use the edit test MCP tool, and prompt the user before making changes.

// Use this if you want the agent to just implement your prompt without added approval
Never directly edit Momentic test or module YAMLs. Only use the Momentic MCP tools to edit Momentic YAMLs. If they are unavailable tell the user you are unable to edit the YAML files.

​

Step 4: 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

​

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:

create a new test called demo test for the yc website

Then once you create that test load its full data, use this to then edit the test

click on the companies tab
choose a major name brand company and click on their profile
check that the team size is visible
click on the jobs tab
assert that the blurb about what the company does is no longer visible

name: "demo-test"
baseUrl: "https://www.ycombinator.com"
description: "Test for YC website - companies tab navigation and job page verification"

id: "391f065b-48f3-4548-ab15-079543fa69e0"

id: "391f065b-48f3-4548-ab15-079543fa69e0"
message: |
  Add test steps to:
  1. Navigate to the YC website
  2. Click on the 'Companies' tab
  3. Find and click on a major brand company like DoorDash or Coinbase
  4. Verify that the team size is visible on the company profile
  5. Click on the 'Jobs' tab
  6. Assert that the company description blurb is no longer visible on the jobs page

​

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

​

Module Tools

​

Test Tools