Skip to main content

Connecting an AI Agent

Connect an AI agent to the neonto MCP server through automatic discovery in VS Code, or by pointing an external MCP client at the server's endpoint URL. This page covers the generic setup commands plus a walkthrough per client.

Before you connect

  • Log in with a valid neonto license. The server rejects every request with HTTP 401 until authentication succeeds.
  • Pin neonto.mcp.port in your settings. If the configured port is busy, the server falls back to a random free port — and the URL in your client config then points at the wrong one. All guides below assume the default port 6789.

Setup commands

neonto Editor provides two helper commands that the client guides below rely on.

Create an .mcp.json file

  1. Open the Command Palette (Ctrl+Shift+P / F1).
  2. Run neonto: Create File for MCP.
  3. neonto writes a .mcp.json file into the root of your open workspace folder, pre-filled with the server's current URL.

Command Palette with "neonto: Create File for MCP" highlighted

The generated file looks like this:

{
"mcpServers": {
"neonto": {
"type": "http",
"url": "http://127.0.0.1:6789/mcp"
}
}
}

The generated .mcp.json file highlighted in the Explorer, with the "MCP file created." confirmation notification

Copy the server URL

  1. Open the Command Palette.
  2. Run neonto: Copy MCP Server URL.
  3. The endpoint URL (e.g. http://127.0.0.1:6789/mcp) is copied to your clipboard and shown in a notification.

Discovering the URL without a command

The running server's URL is also written to a temporary file on activation, so tooling like the Copilot CLI can discover it without you running a command. The same URL is also shown in the "neonto MCP server started" notification when the extension activates.

VS Code Copilot Chat

Copilot Chat discovers the neonto MCP server automatically. No configuration is required: once the extension activates and you are authenticated, neonto's tools appear alongside Copilot Chat's other available tools.

Copilot Chat's Configure Tools picker with the neonto MCP server section highlighted, listing tools like shacl_validation and sparql_query

Claude Code

Claude Code reads a project-root .mcp.json natively — so running neonto: Create File for MCP in your workspace is the entire setup. Approve the server when Claude Code prompts on next start.

Alternatively, register the server from the terminal:

claude mcp add --transport http neonto http://127.0.0.1:6789/mcp

Verify the connection with /mcp in the Claude Code terminal, or — in the Claude Code VS Code extension — via the MCP servers panel: the neonto server should be listed as connected.

The Claude Code panel in VS Code with the MCP servers dialog open, showing the project server "neonto" with a green Connected badge

Codex

Codex extension in VS Code (step by step)

The Codex VS Code extension is configured through its own settings UI — no config file needed.

Step 1 — Open the Codex panel in VS Code (the CODEX tab).

The Codex panel in VS Code with a workspace open

Step 2 — Open the Command Palette (Ctrl+Shift+P) and run neonto: Copy MCP Server URL.

Command Palette with "neonto: Copy MCP Server URL" highlighted

Step 3 — A notification confirms the copied endpoint: http://127.0.0.1:6789/mcp.

Notification confirming the MCP server URL was copied to the clipboard

Step 4 — In the Codex panel, open the settings (gear icon).

The gear icon in the Codex panel toolbar

Step 5 — Choose Codex settings from the account menu.

The Codex account menu with the "Codex settings" entry

Step 6 — In the Codex Settings tab, select MCP servers.

The Codex Settings tab with the "MCP servers" section selected

Step 7 — Click Add server.

The "Add server" button in the Codex MCP servers list

Step 8 — Name the server Neonto, select Streamable HTTP, and paste the copied URL.

The add-server form with name "Neonto", type "Streamable HTTP", and the pasted server URL

Step 9 — Verify: ask Codex "Can you access the neonto mcp?". Codex should confirm that the mcp__neonto tools are available.

Codex chat confirming access to the neonto MCP tools

Codex CLI

Add the server to ~/.codex/config.toml (or .codex/config.toml inside a trusted project):

[mcp_servers.neonto]
url = "http://127.0.0.1:6789/mcp"

On older Codex versions, Streamable HTTP servers additionally require the flag experimental_use_rmcp_client = true in a [features] section.

Verify with:

codex mcp list

Copilot CLI

Either run copilot mcp add interactively (choose HTTP as the server type), or add the entry to ~/.copilot/mcp-config.json — the format is identical to the generated .mcp.json shown above.

Copilot CLI can also discover the running server through the temporary URL file neonto writes on activation. Manage and verify servers with the /mcp command in an interactive session.

Antigravity

Open Settings → Customizations → "Open MCP Config" to edit mcp_config.json (global: ~/.gemini/config/mcp_config.json; per project: .agents/mcp_config.json). Note that Antigravity uses serverUrl — not url — for remote servers:

{
"mcpServers": {
"neonto": {
"serverUrl": "http://127.0.0.1:6789/mcp"
}
}
}

Reload the MCP configuration from the Customizations tab, then confirm the neonto tools are listed.

opencode

Add the server to opencode.json in your project root (type remote covers Streamable HTTP):

{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"neonto": {
"type": "remote",
"url": "http://127.0.0.1:6789/mcp",
"enabled": true
}
}
}

Other MCP clients

Any MCP client that accepts a Streamable HTTP endpoint can connect with just the server URL: use the generated .mcp.json entry as a template, or paste the copied URL into the client's own configuration.

Verify the connection

Once connected, ask your agent to list its available tools and confirm neonto's tools (for example sparql_query or turtle_syntax_guide) appear.

The Codex panel in VS Code answering "Which neonto tools do you have access to?" with the neonto MCP tools grouped by category