MCP Server Setup

Model Context Protocol servers expose tools that Navigator can call during a chat response. Start with one known server, confirm its tools are visible, then decide whether it should be available globally, in a preset, or only through @ mentions.

Setup flow

Choose a transport

Use stdio for local command-based servers, SSE for event-stream servers, or streamable HTTP for modern remote servers.

Add server configuration

Register the server in the Navigator MCP settings or through file-based MCP configuration if FILE_BASED_MCP_CONFIG=true.

Test discovery

Confirm Navigator can connect to the server and list available tools.

Run a safe tool call

Test with a read-only or harmless tool before enabling automation-heavy actions.

Create a preset

Group the server’s tools into a preset if users will need them often.

Example stdio server

{
  "name": "playwright",
  "description": "Browser automation tools",
  "transport": "stdio",
  "command": "npx",
  "args": ["@playwright/mcp@latest"]
}

Example remote server

{
  "name": "internal-crm",
  "description": "Read customer records and update pipeline tasks",
  "transport": "streamable-http",
  "url": "https://tools.example.com/mcp",
  "headers": {
    "Authorization": "Bearer ${CRM_MCP_TOKEN}"
  }
}

Testing checklist

The command or remote URL works outside Navigator
Required environment variables are available to the server
Navigator can list tools from the server
Manual tool mode is enabled while testing mutating tools
Timeouts are configured for long-running tools

MCP configuration reference

See configuration fields, transport examples, and troubleshooting notes.

Configuration

Project

Setup flow

Example stdio server

Example remote server

Testing checklist

MCP configuration reference

​Setup flow

​Example stdio server

​Example remote server

​Testing checklist

MCP configuration reference

Setup flow

Example stdio server

Example remote server

Testing checklist