Netlas Docs MCP Server

April 29, 2026

The Netlas Docs MCP Server lets AI assistants access the latest Netlas documentation and reference data. With this server, assistants can help with Netlas search queries, API integration, and other features.

The server is open to everyone and does not need a Netlas API key. It is made for accessing documentation and reference information.

What is MCP?

MCP stands for Model Context Protocol. This protocol sets a standard way for AI assistants to connect to outside sources like documentation, APIs, databases, local tools, and other services.

An MCP server shares this information with clients that support MCP. This lets assistants get the data they need to answer questions or complete tasks.

What It Can Help With

The MCP server enables assistants to access Netlas documentation in a structured format. For example, it can:

check exact query field names;
explain how a field is indexed and how it can be searched;
check API endpoint details, including request and response structures;
check public subscription plan information;
combine documentation, field mappings, and API reference data to answer questions.

This is especially helpful for tasks that need exact field names, API operation names, or up-to-date documentation details.

Use it together with Netlas CLI

If the assistant can use the Netlas CLI, the MCP server helps check query syntax and field names before running requests with the CLI.

Install the Netlas CLI with pipx or brew, run netlas --savekey, and let the agent use the CLI. The agent can then run queries, use discovery features, and access the private scanner.

How to Enable It

Use any AI assistant or client that supports remote MCP servers.

Access the MCP server settings within the chosen client.
Add a new MCP server entry.
Assign the server name as netlas-docs.
Specify the server URL as:
```
https://docs.netlas.io/mcp
```
If prompted for a transport type, select Streamable HTTP or the most similar remote MCP option available.

Claude Code CLI

Add the server with HTTP transport:

claude mcp add --transport http netlas-docs https://docs.netlas.io/mcp

To enable availability across all projects, add the server with user scope:

claude mcp add --transport http netlas-docs --scope user https://docs.netlas.io/mcp

Check that it was added:

claude mcp list

Codex CLI

Add the server from the command line:

codex mcp add netlas-docs --url https://docs.netlas.io/mcp

Check that it was added:

codex mcp list

Alternatively, add the server manually to ~/.codex/config.toml:

[mcp_servers.netlas-docs]
url = "https://docs.netlas.io/mcp"

Gemini CLI

Add the server with HTTP transport:

gemini mcp add --transport http netlas-docs https://docs.netlas.io/mcp

Gemini CLI adds MCP servers to the project configuration by default. To add the server to your user configuration instead, use:

gemini mcp add --scope user --transport http netlas-docs https://docs.netlas.io/mcp

Check that it was added:

gemini mcp list

Test MCP Server

After enabling the server, the assistant can be queried with questions such as:

"How to search Netlas by HTTP headers?"
"Check the Netlas docs and explain how CIDR search works."
"Find the Netlas API endpoint for downloading search results."
"What fields are available for SSL certificate issuer data in Netlas?"
"What Netlas pricing plan is the best for me if I am a bug bounty hunter?"

If your client shows connected MCP servers, make sure netlas-docs is listed as connected before you send documentation-specific queries.