Testing Your First Tool

This guide walks you through writing your first end-to-end tests for FrontMCP tools. You’ll learn how to set up the testing framework, write tests for tools, resources, and prompts, and run your test suite.

Prerequisites:

A FrontMCP project with at least one tool (see Your First Tool)
Basic familiarity with Jest

What You’ll Build

A complete E2E test suite that:

Starts your MCP server automatically
Tests tool execution with various inputs
Validates error handling
Tests resources and prompts

Step 1: Install the Testing Library

npm install -D @frontmcp/testing

Step 2: Configure Testing

The frontmcp test command auto-generates the correct Jest/SWC config. No manual jest.e2e.config.ts needed. Add a script to your package.json:

package.json

{
  "scripts": {
    "test:e2e": "frontmcp test"
  }
}

Step 3: Write Your First Test

Create a test file in the e2e/ directory using the .e2e.spec.ts extension (not .e2e.ts). The frontmcp test command discovers tests matching e2e/**/*.e2e.spec.ts:

e2e/server.e2e.spec.ts

import { test, expect } from '@frontmcp/testing';

// Configure the test to use your server
test.use({
  server: './src/main.ts',
  port: 3003,
});

test('server starts and lists tools', async ({ mcp }) => {
  const tools = await mcp.tools.list();
  expect(tools.length).toBeGreaterThan(0);
});

Run your test:

npm run test:e2e

The testing library automatically:

Starts your FrontMCP server
Connects an MCP client
Runs your test
Cleans up after completion

Step 4: Test Tool Execution

Testing Successful Execution

test('add tool returns correct sum', async ({ mcp }) => {
  const result = await mcp.tools.call('calculator:add', {
    a: 5,
    b: 3,
  });

  expect(result).toBeSuccessful();
  expect(result.json()).toBe(8);
});

Testing Multiple Scenarios

test.describe('Calculator Tools', () => {
  test('add returns sum of two numbers', async ({ mcp }) => {
    const result = await mcp.tools.call('calculator:add', { a: 10, b: 5 });
    expect(result).toBeSuccessful();
    expect(result.json()).toBe(15);
  });

  test('multiply returns product', async ({ mcp }) => {
    const result = await mcp.tools.call('calculator:multiply', { a: 4, b: 7 });
    expect(result).toBeSuccessful();
    expect(result.json()).toBe(28);
  });

  test('divide handles division', async ({ mcp }) => {
    const result = await mcp.tools.call('calculator:divide', { a: 20, b: 4 });
    expect(result).toBeSuccessful();
    expect(result.json()).toBe(5);
  });
});

Testing Error Cases

test('divide by zero returns error', async ({ mcp }) => {
  const result = await mcp.tools.call('calculator:divide', {
    a: 10,
    b: 0,
  });

  expect(result).toBeError();
});

test('missing required input returns validation error', async ({ mcp }) => {
  const result = await mcp.tools.call('calculator:add', {
    a: 5,
    // missing 'b' parameter
  });

  expect(result).toBeError(-32602); // Invalid params
});

Step 5: Test Tool Discovery

Verify your tools are properly registered:

test('calculator app exposes expected tools', async ({ mcp }) => {
  const tools = await mcp.tools.list();

  expect(tools).toContainTool('calculator:add');
  expect(tools).toContainTool('calculator:subtract');
  expect(tools).toContainTool('calculator:multiply');
  expect(tools).toContainTool('calculator:divide');
});

test('tools have proper descriptions', async ({ mcp }) => {
  const tools = await mcp.tools.list();
  const addTool = tools.find(t => t.name === 'calculator:add');

  expect(addTool).toBeDefined();
  expect(addTool?.description).toContain('Add');
});

Step 6: Test Resources

If your app has resources:

test('expense policy resource is readable', async ({ mcp }) => {
  const resources = await mcp.resources.list();
  expect(resources).toContainResource('expense://policy');

  const content = await mcp.resources.read('expense://policy');
  expect(content).toHaveMimeType('text/markdown');
  expect(content.text()).toContain('Expense Policy');
});

test('expense by ID resource template works', async ({ mcp }) => {
  const templates = await mcp.resources.listTemplates();
  expect(templates).toContainResourceTemplate('expense://expenses/{expenseId}');

  const content = await mcp.resources.read('expense://expenses/123');
  expect(content).toHaveMimeType('application/json');

  const expense = content.json();
  expect(expense.id).toBe('123');
});

Step 7: Test Prompts

If your app has prompts:

test('expense report prompt is available', async ({ mcp }) => {
  const prompts = await mcp.prompts.list();
  expect(prompts).toContainPrompt('expense-report');
});

test('expense report prompt generates messages', async ({ mcp }) => {
  const result = await mcp.prompts.get('expense-report', {
    startDate: '2024-01-01',
    endDate: '2024-01-31',
    category: 'Travel',
  });

  expect(result.messages).toHaveLength(1);
  expect(result.messages[0]).toHaveRole('user');
  expect(result.messages[0]).toContainText('2024-01-01');
  expect(result.messages[0]).toContainText('Travel');
});

Step 8: Organize Your Tests

Recommended file structure:

src/
├── main.ts                    # Server entry
└── apps/
    └── calculator/
        └── index.ts           # App definition
e2e/
├── server.e2e.spec.ts         # Server-level tests
└── calculator.e2e.spec.ts     # App-specific tests

Use test.describe() to group related tests:

e2e/calculator.e2e.spec.ts

import { test, expect } from '@frontmcp/testing';

test.use({
  server: './src/main.ts',
  port: 3003,
});

test.describe('Calculator App', () => {
  test.describe('Basic Operations', () => {
    test('add works', async ({ mcp }) => {
      const result = await mcp.tools.call('calculator:add', { a: 1, b: 2 });
      expect(result.json()).toBe(3);
    });

    test('subtract works', async ({ mcp }) => {
      const result = await mcp.tools.call('calculator:subtract', { a: 5, b: 3 });
      expect(result.json()).toBe(2);
    });
  });

  test.describe('Advanced Operations', () => {
    test('power works', async ({ mcp }) => {
      const result = await mcp.tools.call('calculator:pow', { base: 2, exp: 8 });
      expect(result.json()).toBe(256);
    });

    test('sqrt works', async ({ mcp }) => {
      const result = await mcp.tools.call('calculator:sqrt', { n: 16 });
      expect(result.json()).toBe(4);
    });
  });

  test.describe('Error Handling', () => {
    test('sqrt of negative returns error', async ({ mcp }) => {
      const result = await mcp.tools.call('calculator:sqrt', { n: -1 });
      expect(result).toBeError();
    });
  });
});

Complete Example

Here’s a complete test file:

e2e/server.e2e.spec.ts

import { test, expect } from '@frontmcp/testing';

test.use({
  server: './src/main.ts',
  port: 3003,
  logLevel: 'warn',
});

test.describe('MCP Server E2E Tests', () => {
  test('server is running and healthy', async ({ mcp }) => {
    expect(mcp.isConnected()).toBe(true);
    expect(mcp.serverInfo.name).toBeDefined();
  });

  test.describe('Tools', () => {
    test('lists all expected tools', async ({ mcp }) => {
      const tools = await mcp.tools.list();

      expect(tools).toContainTool('calculator:add');
      expect(tools).toContainTool('calculator:multiply');
    });

    test('add tool computes correctly', async ({ mcp }) => {
      const result = await mcp.tools.call('calculator:add', { a: 100, b: 200 });

      expect(result).toBeSuccessful();
      expect(result.json()).toBe(300);
    });

    test('invalid input returns error', async ({ mcp }) => {
      const result = await mcp.tools.call('calculator:add', {
        a: 'not a number',
        b: 5,
      });

      expect(result).toBeError(-32602);
    });
  });

  test.describe('Resources', () => {
    test('lists available resources', async ({ mcp }) => {
      const resources = await mcp.resources.list();
      expect(resources.length).toBeGreaterThanOrEqual(0);
    });
  });

  test.describe('Prompts', () => {
    test('lists available prompts', async ({ mcp }) => {
      const prompts = await mcp.prompts.list();
      expect(prompts.length).toBeGreaterThanOrEqual(0);
    });
  });
});

Best Practices

Use descriptive test names

// Good - describes what's being tested
test('add tool returns sum of two positive numbers', async ({ mcp }) => {});

// Bad - too vague
test('add works', async ({ mcp }) => {});

Test both success and error cases

Always test:

Happy path (valid inputs)
Edge cases (zero, negative, empty)
Error cases (invalid inputs, missing params)

Use custom matchers

// Good - clear intent, better error messages
expect(result).toBeSuccessful();
expect(tools).toContainTool('my-tool');

// Bad - generic assertions
expect(result.isError).toBe(false);
expect(tools.some(t => t.name === 'my-tool')).toBe(true);

Use port: 0 in CI

Auto-select ports to avoid conflicts:

test.use({
  server: './src/main.ts',
  port: process.env.CI ? 0 : 3003,
});

Next Steps

Test Fixtures

Learn about all available test fixtures

Custom Matchers

Full reference for MCP-specific matchers

Auth Testing

Test authentication and authorization

HTTP Mocking

Mock external API calls

Get Started

FrontMCP

Features

Extensibility

Testing

React SDK

Guides

Testing Your First Tool

What You’ll Build

Step 1: Install the Testing Library

Step 2: Configure Testing

Step 3: Write Your First Test

Step 4: Test Tool Execution

Testing Successful Execution

Testing Multiple Scenarios

Testing Error Cases

Step 5: Test Tool Discovery

Step 6: Test Resources

Step 7: Test Prompts

Step 8: Organize Your Tests

Complete Example

Best Practices

Next Steps

Test Fixtures

Custom Matchers

Auth Testing

HTTP Mocking

Get Started

FrontMCP

Features

Extensibility

Testing

React SDK

Guides

Documentation Index

​What You’ll Build

​Step 1: Install the Testing Library

​Step 2: Configure Testing

​Step 3: Write Your First Test

​Step 4: Test Tool Execution

​Testing Successful Execution

​Testing Multiple Scenarios

​Testing Error Cases

​Step 5: Test Tool Discovery

​Step 6: Test Resources

​Step 7: Test Prompts

​Step 8: Organize Your Tests

​Complete Example

​Best Practices

​Next Steps

Test Fixtures

Custom Matchers

Auth Testing

HTTP Mocking

What You’ll Build

Step 1: Install the Testing Library

Step 2: Configure Testing

Step 3: Write Your First Test

Step 4: Test Tool Execution

Testing Successful Execution

Testing Multiple Scenarios

Testing Error Cases

Step 5: Test Tool Discovery

Step 6: Test Resources

Step 7: Test Prompts

Step 8: Organize Your Tests

Complete Example

Best Practices

Next Steps