MCP Productions

Provides an MCP server that enables AI assistants to explore Test2w endpoints, perform test requests, and use documentation to integrate the Test2w API.

typescript

0

GitHub Stars

typescript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "johnglavan71-mcp-productions": {
      "command": "npx",
      "args": [
        "-y",
        "test2w-mcp"
      ],
      "env": {
        "TEST2W_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

You can run and interact with the Test2w API through an MCP server, enabling AI assistants to explore endpoints, make test requests, and understand how to integrate the API into your applications. This guide shows you how to use the MCP server, install it locally, and configure it for secure access to Test2w resources.

How to use

To use the Test2w MCP Server, acquire the MCP command to launch it from your development environment, then connect your MCP client to access the API endpoints. The server enables AI assistants to browse API endpoints, issue requests for testing, and learn how the SDK can be integrated into your project. Start by ensuring you have an API key for Test2w and your MCP client configured to use that key.

How to install

Prerequisites: ensure you have Node.js (version 20.x or later) installed and access to a terminal. You will also need an API key for Test2w if you plan to interact with protected endpoints.

# Install the Test2w TypeScript API Library (server client)
npm install test2w

Additional content

The MCP server supports multiple ways to run and configure it. You can connect using an MCP client that executes a standard command to start the MCP server, or you can interact with the server through the library’s endpoint methods and the optional raw response handling utilities described below.

Key capabilities include handy methods to retrieve lists of resources (for example, activity lists) and to access raw HTTP responses when you need to inspect headers or timing information. You can also perform undocumented requests using generic HTTP verbs if you need access to endpoints not explicitly documented in the public API. The library provides error handling classes to help you distinguish between client-side and server-side issues, and it can automatically retry certain transient failures to improve resilience.

Security and observability options include configurable log levels, a pluggable logger, and configurable fetch options (for proxying, custom fetch implementations, and timeouts). This ensures you can adapt the MCP server to your environment while gaining insight into request/response behavior during development and testing.

Tools and endpoints described

The MCP server exposes common API interaction tools and endpoints used to access the Test2w REST API. Notable capabilities include listing resources via the activity.list endpoint, accessing raw response data with asResponse and withResponse, and performing undocumented requests through generic HTTP verbs (get, post, etc.). You can also configure logging, retries, and timeouts to tailor behavior to your development workflow.

Available tools

activity.list

List activities from the Test2w API using the activity namespace.

APIPromise.asResponse

Access the raw Response object when a request succeeds, without consuming the body.

APIPromise.withResponse

Obtain the raw Response together with parsed data by consuming the body.

get

Make an undocumented GET request to an arbitrary path.

post

Make an undocumented POST request to an arbitrary path.

APIError

Base error type for API-related failures, with specialized subclasses for different HTTP status codes.