CodeNeter

MCP servers

Connect external tools and data sources to the agent with Model Context Protocol servers.

MCP (Model Context Protocol) servers give the agent tools beyond your project files, such as an issue tracker, a database, or a documentation service. Once a server is configured and enabled, the agent can call its tools and read its resources during a task.

Configuration files

ScopeFile
User~/.codeneter/mcp.json
Project.codeneter/mcp.json in the project

The project file is used by the desktop app and the CLI. The editor extension reads only the user file. If both files define a server with the same name, the project's definition is used.

Both files list servers under mcpServers. This example shows the format for local and remote servers; replace the package, URL, and token with your server's details:

{
  "mcpServers": {
    "my-local-server": {
      "command": "npx",
      "args": ["-y", "<server-package>"],
      "env": { "API_TOKEN": "<your-token>" }
    },
    "my-remote-server": {
      "url": "https://example.com/mcp",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

You can also add servers, turn them on or off, and check their status in the MCP settings. Servers added there are saved to the user file.

Local and remote servers

  • Local servers run as a process on your computer. Set command, with optional args and env.
  • Remote servers connect over Streamable HTTP. Set url, with optional headers, for example to send an API token. Servers that only support the older SSE transport can't be used.

How the agent uses MCP

CodeNeter connects to your enabled servers when the agent starts working. The agent looks up a server's tools when it needs them and calls them as part of a task.

MCP tool calls ask for your approval by default. The request shows the tool and its input, and you can run it once, allow that tool for the rest of the conversation, or cancel it.

Trust and credentials

Only add servers you trust. A local server runs with your user account's access, and any token in the configuration gives the agent whatever that token allows. Use tokens with limited permissions, and keep them out of a project mcp.json that's committed to version control.