3T MCP – Your data, one prompt away

Our MCP server gives your AI client direct access to your MongoDB and document database data. Query, explore, and investigate your data in plain English. Read-only, and entirely on your machine.

Connect now

For developers, data engineers, and AI builders

AI agents are powerful, but without real database context they’re guessing. 3T MCP gives any MCP-compatible AI client direct, read-only access to your live MongoDB environment.

Ask MongoDB in natural language

Query, explore, and investigate your data from the AI client you already use. All without writing a line of code or opening a separate tool.

Safe by design

Every tool is strictly read-only. Developers, analysts, and AI agents can explore freely. Nothing can be edited, deleted, or changed.

What 3T MCP can do

IDE-equivalent MongoDB workflows, available with a natural language prompt.

Collection browsing

List all databases and collections on any configured connection. Navigate your full MongoDB estate without switching tools.

Query execution

Run find queries against live data and get results in seconds. Explain how any query will execute before it runs in production.

Schema analysis

See the full shape of any collection – field names, types, and nested structures – before writing a single query.

PII scanner

Find fields that may contain personally identifiable information across your collections. Stay on top of compliance risk before data goes anywhere.

Why teams use 3T MCP

Skip straight to the answer

Instead of opening a connection, finding the right collection, and writing queries by hand, ask one question and get back exactly what you need.

Works where you already work

Your AI client becomes a MongoDB interface. No context switching, separate tools, or extra windows.

Safe enough for non-technical users

Product managers, analysts, and ops teams can self-serve data questions without risking anything. Every tool is read-only — always.

Built for restricted environments

The MCP server runs entirely on your machine. No cloud intermediary, no outbound data flow. Designed for teams where that matters.

Get started free

Get started

3T MCP is a single binary that works as a standard MCP server and as a CLI you can integrate into scripts and automation workflows. The MCP server runs locally on your machine as an MCP stdio process. Your data never passes through an intermediate service.

MacOS and Linux

The script detects your OS and architecture, downloads the correct binary, and installs it to /usr/local/bin when writable, or ~/.local/bin otherwise.

curl -sSf https://raw.githubusercontent.com/3tio/3t-mcp-releases/main/install.sh | sh

If the script prints a message about ~/.local/bin, add the directory to your shell’s PATH:
export PATH="$HOME/.local/bin:$PATH". To make it permanent, add the line above to ~/.bashrc, ~/.zshrc, or your shell’s equivalent, then open a new terminal.

Windows (PowerShell)

To download the binary on PowerShell, run the following command:

irm https://raw.githubusercontent.com/3tio/3t-mcp-releases/main/install.ps1 | iex

Verify and check the current MCP version

To verify that the MCP server has been installed, run the following command:

stt-cli --version

PowerShell users may have to open a new terminal window before running the command, as the installer updates your PATH but the current session may not see it yet.

3T MCP requires a 3T account. Authentication happens once, and credentials are stored locally and reused automatically.

Type the following command to launch your browser and complete sign-in by either logging in to your 3T Account, or creating a new one:

stt-cli login

Once the browser confirms success, return to the terminal to start testing the MCP.

If at any point the tool returns an authentication error, run the following command to to refresh your credentials:

stt-cli login

3T MCP runs as a local process started by stt-cli mcp. Your AI client needs to know how to launch it.

Claude Desktop

Open the Claude configuration file; its path depends on your operating system:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.claude/settings.json

Edit the file to match the following configuration:

{
  "mcpServers": {
    "3t-mcp": {
      "command": "stt-cli",
      "args": ["mcp"]
    }
  }
}

Restart Claude Desktop after saving.

VS Code

Create or edit .vscode/mcp.json in your workspace root. For a user-level (global) config, open the Command Palette (Cmd/Ctrl+Shift+P) and run MCP: Open User Configuration.

{
  "servers": {
    "3t-mcp": {
      "type": "stdio",
      "command": "stt-cli",
      "args": ["mcp"]
    }
  }
}
Cursor

Edit ~/.cursor/mcp.json for a global config, or .cursor/mcp.json in your project root for a project-specific one. You can also go to Cursor → Settings → MCP and add a new server from the UI.

{
  "mcpServers": {
    "3t-mcp": {
      "command": "stt-cli",
      "args": ["mcp"]
    }
  }
}
Any MCP-compatible client

For clients not listed above, use these settings:

Transport: stdio
Command: stt-cli
Args: ["mcp"]

3T MCP is on GitHub: you can find more details, including how to add connections, set up server flags and environmental variables, update the server, and more at our repository.

browse 3t mcp on github