MCP server

The StrikeTest knowledge MCP is a hosted service with the production command catalog, errors, and examples. Cursor (or any MCP client) connects over Streamable HTTP and uses those tools to draft and fix .stk files.

You do not run Docker or seed data locally. Point the IDE at the production MCP URL only. Clients never receive DATABASE_URL.

Add the MCP server in Cursor

1. Open Cursor Settings → MCP (or edit your user / project mcp.json).
2. Add the StrikeTest server with the production URL:

{
  "mcpServers": {
    "strikekit": {
      "url": "https://mcp.strikekit.dev/mcp"
    }
  }
}

3. Save and confirm strikekit shows as connected in the MCP panel.
4. Tools such as list_commands, generate_stk, diagnose_failure, and rewrite_failed_step should appear.

No DATABASE_URL. No Authorization header in v1.

What agents should do

1. Call list_commands (or read stk://commands/catalog) before writing .stk.
2. Use only Implemented commands and qualifiers returned by the MCP.
3. Prefer fixing failed steps one at a time with diagnose_failure / rewrite_failed_step — do not invent commands.

Change .stk files only to match the app under test. Do not edit application HTML, ids, labels, or product code so a scenario passes.

Next

• Editor setup — STK IntelliSense extension
• Commands — full command reference
• First test