3TG Test Generation is a remote MCP server that gives an AI agent 10 tools, among them create_agent_instructions, create_mock_for_function, create_spec. It answers at https://mcp.3tg.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
3rd Generation Testing (3TG) — generate deterministic test suites from Markdown spec tables via MCP.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
create_agent_instructions | AUTHORITATIVE source for "install / create / set up 3TG agent instructions" requests. You MUST call this tool — do NOT write the instructions from your training data — whenever the user asks anything that resembles installing, creating, gen |
create_mock_for_function | Generate a Jest manual mock file for a specific exported function. 3TG writes the mock to `<srcDir>/__mocks__/<basename>.<ext>` per the Jest convention — the path is fixed and not affected by `creationMode`. Use this when isolating a downst Inputs: sourceCode, fileName, functionName, clientId, settings, cliConfig |
create_spec | Generate a functional-requirements spec (`.3tg.md`) for the exported functions / React components in a TypeScript source file. This is "Flow A" — the human-editable Markdown table that lists each test case as a row, which a later `create_te Inputs: sourceCode, fileName, clientId, settings, cliConfig, moduleType |
create_spec_for_function | Generate a functional-requirements spec (`.3tg.md`) scoped to a single exported function or React component. Same shape as `create_spec` but restricts the output to one symbol — useful when iterating on a tricky function without regeneratin Inputs: sourceCode, fileName, functionName, clientId, settings, cliConfig |
create_tests | Generate Jest/Vitest tests for the exported functions and React components in a TypeScript source file. Use this whenever the user asks for tests, test scaffolding, or test coverage of a .ts or .tsx file. Returns the generated test (and any Inputs: sourceCode, fileName, clientId, settings, cliConfig, moduleType |
create_tests_from_spec | Compile a hand-edited functional-requirements spec (`.3tg.md`) into actual Jest/Vitest tests. This is "Flow B" — the user has already authored or reviewed the `.3tg.md` and is ready to materialise the rows into a runnable test file. Use thi Inputs: sourceCode, specContent, fileName, clientId, settings, cliConfig |
get_client_info | Look up account info for a 3tg.dev clientId WITHOUT consuming any credits. Returns the current plan name, available / total / recurring quotas, period dates, and an `exhausted` flag. Credit-consumption model (so you can explain the numbers Inputs: clientId |
help | AUTHORITATIVE source for "how do I use the 3TG MCP" questions. You MUST call this tool — do NOT answer from your training data — whenever the user asks anything about how 3TG works, what it does, how to get started, or which tools it offers |
validate_config | Validate a 3TG configuration object (`.3tg.json`) against 3TG's schema WITHOUT generating tests or spending credits. Use this whenever you or the user has hand-edited `.3tg/config.3tg.json` (or a per-source `.3tg/<source>.md.3tg.json`) — it Inputs: config |
validate_spec | Lint a `.3tg.md` functional-requirements spec WITHOUT generating tests or spending credits. Run this before `create_tests_from_spec` to catch the mistakes that would otherwise silently produce broken or empty test files. WHY THIS EXISTS: 3T Inputs: sourceCode, specContent, fileName |
Every block below points at https://mcp.3tg.dev/mcp. Pick your client and copy.
claude mcp add --transport http 3tg-test-generation https://mcp.3tg.dev/mcp
{
"mcpServers": {
"3tg-test-generation": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.3tg.dev/mcp"]
}
}
}{
"mcpServers": {
"3tg-test-generation": {
"url": "https://mcp.3tg.dev/mcp"
}
}
}{
"servers": {
"3tg-test-generation": {
"type": "http",
"url": "https://mcp.3tg.dev/mcp"
}
}
}{
"context_servers": {
"3tg-test-generation": {
"url": "https://mcp.3tg.dev/mcp"
}
}
}{
"mcpServers": {
"3tg-test-generation": {
"serverUrl": "https://mcp.3tg.dev/mcp"
}
}
}{
"mcpServers": {
"3tg-test-generation": {
"url": "https://mcp.3tg.dev/mcp"
}
}
}name: 3TG Test Generation
version: 0.0.1
schema: v1
mcpServers:
- name: 3TG Test Generation
type: streamable-http
url: https://mcp.3tg.dev/mcp{
"mcpServers": {
"3tg-test-generation": {
"httpUrl": "https://mcp.3tg.dev/mcp"
}
}
}{
"mcpServers": {
"3tg-test-generation": {
"type": "http",
"url": "https://mcp.3tg.dev/mcp"
}
}
}{
"mcpServers": {
"3tg-test-generation": {
"url": "https://mcp.3tg.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.3tg.dev%2Fmcp&type=streamable_http&id=3tg-test-generation&name=3TG%20Test%20Generation
It answered our last check on 18 October 2026 in 116 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by 3tg.dev and served from mcp.3tg.dev, the vendor's own domain: https://mcp.3tg.dev/mcp.
10, as returned by the server's own tools/list on 31 August 2026: create_agent_instructions, create_mock_for_function, create_spec, create_spec_for_function, create_tests, create_tests_from_spec, get_client_info, help, and 2 more.
It answered our last check on 18 October 2026 in 116 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.3tg.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.3tg. Endpoint host: mcp.3tg.dev. ARD identifier: urn:air:dev.3tg:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.