# 3tg MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.3tg%2Fmcp
Registry id: `mcp-registry/dev.3tg/mcp`
Status: live (checked 2026-10-26T18:10:16.208Z)

## Measurements (30 days)

- Uptime: 99.97%
- Checks: 4952
- Outages (90 days): 3

## Install

```json
{
  "mcpServers": {
    "3tg-mcp-server": {
      "type": "http",
      "url": "https://mcp.3tg.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http 3tg-mcp-server https://mcp.3tg.dev/mcp
```

## Tools (10)

- `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
- `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 pa
- `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-edit
- `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 outpu
- `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 scaffold
- `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 `
- `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, an
- `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
- `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-
- `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 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
