Configure MCP in desktop apps
This guide shows how to load the NEO MCP servers (playwright, jira, azure-devops) when you work with a desktop app instead of a code editor. Before you start, check Configure the MCPs to see which servers you need and what data goes into each one.
| App | Does it work for NEO? |
Where it's configured |
|---|---|---|
| Claude Desktop | ✅ Both in the chat and in the Code tab | claude_desktop_config.json and, in the Code tab, also .mcp.json |
| ChatGPT Desktop | ✅ Through Codex inside the app · ❌ in the regular chat | ~/.codex/config.toml |
| GitHub Copilot app | ✅ | The repository or Copilot CLI configuration, plus the app's own |
| Microsoft Copilot (Windows) | ❌ | There's no documentation for adding your own MCP servers |
Remember: the three
NEOservers are local: the app has to launch them on your computer withnpxoruvx. That's why you need Node.js installed and, if you use Jira, uv, even if you only work with the desktop app.
Claude Desktop
Claude Desktop has two ways of working, and MCPs behave differently in each one:
| Tab | What it is | Which MCP configuration it reads |
|---|---|---|
| Chat | The Claude chat | Only claude_desktop_config.json |
| Code | Claude Code inside the desktop app (option B in Getting started) | The project's .mcp.json, ~/.claude.json, and also claude_desktop_config.json |
To work with
NEO, you'll usually use the Code tab, opened on the project folder. In that case you don't need to touchclaude_desktop_config.json: the project's.mcp.jsonis enough, just like in Claude Code in VS Code. Andlippia-neo-bootstrap-stackcan create it for you.
Option 1 — Code tab with .mcp.json (recommended)
- Open the app → Code tab → choose the folder of the test repository.
- Make sure there's a
.mcp.jsonin the project root, with the reference configuration and your real values. - Open a new session: the project's servers are loaded at startup.
- To check, use the + button → Connectors (or
/mcpin the session).
Option 2 — claude_desktop_config.json (chat and Code tab)
Use this when you also want to use the servers from the chat, or have them available in all your projects.
- Open the app → Claude menu → Settings → Developer → Edit Config. This opens the file:
| System | Path |
|---|---|
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
- Paste the servers under the
mcpServersroot key. It's the same format as.mcp.json, but without thetypefield:
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest", "--browser", "chromium"]
},
"jira": {
"command": "uvx",
"args": ["mcp-atlassian"],
"env": {
"JIRA_URL": "https://your-site.atlassian.net/",
"JIRA_USERNAME": "your.email@company.com",
"JIRA_API_TOKEN": "<token>",
"CONFLUENCE_URL": "https://your-site.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "your.email@company.com",
"CONFLUENCE_API_TOKEN": "<token>",
"READ_ONLY_MODE": "true"
}
},
"azure-devops": {
"command": "npx",
"args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
"env": {
"AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-org",
"AZURE_DEVOPS_AUTH_METHOD": "pat",
"AZURE_DEVOPS_PAT": "<token>"
}
}
}
}
- Quit the app completely and open it again. Closing the window isn't enough: on Windows, also quit from the icon in the system tray.
- Check: + button (in the message box) → Connectors → Manage connectors. The servers should be listed there.
If a server is in both places (
claude_desktop_config.jsonand.mcp.json) with the same name, the Code tab connects only once and uses the definition fromclaude_desktop_config.json. To avoid confusion, load each server in only one place.The CLI and the VS Code extension don't read
claude_desktop_config.json. A server you loaded only there won't appear in Claude Code outside the desktop app.
Katalon Studio
katalon-studio is a remote (HTTP) server. For NEO, use it from the Code tab with the project's .mcp.json (Option 1), which accepts "type": "http". Don't load it in claude_desktop_config.json: that configuration is meant for local servers. Details in Set up the Katalon Studio MCP.
If something fails in Claude Desktop
| What you see | What to do |
|---|---|
| The server doesn't appear | Restart the app completely and check that the JSON is valid (one extra comma breaks the whole file) |
It fails with ENOENT and ${APPDATA} appears in the error (Windows) |
Add this to that server's env: "APPDATA": "C:\\Users\\<your-user>\\AppData\\Roaming\\" |
| You want to see the exact error | Logs in %APPDATA%\Claude\logs (Windows) or ~/Library/Logs/Claude (macOS): mcp.log and mcp-server-<nombre>.log |
Claude Desktop also lets you install servers as extensions (
.mcpbfiles, from Settings → Extensions) and add remote connectors (Settings → Connectors → Add custom connector). TheNEOservers are loaded with the JSON configuration above.
ChatGPT Desktop
In the ChatGPT app there are two different places where MCPs appear, and only one of them works for NEO:
| Where | Which servers it accepts | Does it work for NEO? |
|---|---|---|
| Codex inside the desktop app | Local (STDIO) and remote | ✅ Yes |
| ChatGPT chat (connectors / developer mode) | Only remote ones: a public HTTPS URL | ❌ No: the NEO servers are local |
Configure Codex in the desktop app
The desktop app shares its configuration with Codex CLI and the Codex extension. If you already configured it in one of them, it's already in all three.
Through the interface:
- Open the app → Codex → Settings → MCP servers → Add server.
- Choose STDIO.
- Fill in the name (
playwright), the command (npx), and the arguments (-y @playwright/mcp@latest --browser chromium). Add the environment variables if it'sjiraorazure-devops. - Click Save and then Restart.
Through the file: edit ~/.codex/config.toml (on Windows, %USERPROFILE%\.codex\config.toml) using the TOML format shown in Codex in VS Code.
What about the ChatGPT chat?
The regular chat only connects to remote servers (an HTTPS URL using the Streamable HTTP protocol), which you add by turning on developer mode in Settings → Security and login and then from Plugins → +. The NEO servers run on your computer, so they can't be connected to the chat. To use NEO with OpenAI, use Codex.
GitHub Copilot app (desktop)
GitHub has a Copilot desktop app (Windows, macOS, and Linux) designed for working with agents, which supports MCP servers and skills.
According to GitHub's documentation, the app uses the MCP servers already configured in the repository or in Copilot CLI, and lets you add more from its own settings. In practice:
- Configure the servers as in GitHub Copilot CLI:
~/.copilot/mcp-config.jsonfor all your projects, or.mcp.json/.github/mcp.jsonin the repository root. - Open the repository in the app and check its MCP settings to confirm the servers appear.
This app is new and its documentation doesn't have a detailed MCP walkthrough yet. If something doesn't match what you see on screen, the Copilot CLI configuration is the most stable reference.
The GitHub Desktop app (the one for managing repositories) is something else: we didn't find any evidence that it supports MCP servers.
Microsoft Copilot (Windows app)
We didn't find official documentation for adding your own MCP servers to the Microsoft Copilot app for Windows, so we don't recommend it for NEO at the moment. In the Microsoft ecosystem, Copilot with MCP is available in the IDEs: see GitHub Copilot in Visual Studio and GitHub Copilot in VS Code.