Configuration
Configure setup, chat providers, agents, and advanced settings for NeoStack AI
In-Editor Settings
Open Tools > Agent Chat > Settings for the setup users need most often.
Setup
Start on the Setup tab if chat is not ready. It shows:
- NeoStack Cloud account/key status
- Chat provider readiness
- MCP server status and effective port
- Local prerequisites for ACP agents
Chat & Agents
Use Settings > Chat & Agents > Chat Providers to configure NeoStack Cloud, OpenRouter, Ollama, Vercel, or custom OpenAI-compatible providers.
Use the advanced sections on the same tab for ACP agent registry entries, custom system prompt text, tool timeout, agent response timeout, and model visibility.
Project Settings Recovery
If the WebUI is unavailable, open Edit > Project Settings > Plugins > NeoStack AI. This contains lower-level recovery settings such as auto-update, MCP port, browser MCP requests, and path overrides.
Common Settings
| Setting | Description |
|---|---|
| NeoStack Cloud key | Simplest path for NeoStack Cloud chat, subscription checks, extensions, and remote access |
| Provider API keys | Keys for OpenRouter, Vercel, or custom providers |
| Tool Execution Timeout | Seconds an editor/MCP tool can run before the agent receives a tool timeout |
| Agent Response Timeout | Seconds an ACP agent prompt can be silent before NeoStack reports a timeout. 0 disables this and is recommended for unattended long tasks |
| Path Overrides | Advanced recovery path overrides for external CLIs |
MCP Server Settings
Use Settings > Setup or Settings > MCP to copy the live MCP endpoint. The plugin starts on the preferred port but may scan to a nearby port if that port is busy.
| Setting | Description |
|---|---|
| Server Port | Preferred HTTP port for MCP server (default: 9315) |
| Require Auth Token | On by default. Local CLI clients (Claude Code, Codex, etc.) connect to the loopback endpoint without a token; the session token gates non-loopback binds and browser requests. The NeoStack bridge and desktop app send it automatically |
| Allow Browser Requests | Advanced option for browser-origin MCP clients |
Supported MCP Protocols
The MCP server serves the modern stateless protocol and the established session transports on the same endpoint:
| Protocol era | Specification | Endpoints | Behavior |
|---|---|---|---|
| Modern stateless HTTP | MCP 2026-07-28 | POST /mcp |
Per-request negotiation, standard routing headers, cache hints, and capability-gated long-running Tasks |
| Session Streamable HTTP | MCP 2025-03-26 through 2025-11-25 | POST /mcp, GET /mcp, DELETE /mcp |
Backward compatibility for current MCP clients |
| HTTP+SSE | MCP 2024-10-07 and 2024-11-05 | GET /sse, POST /message |
Compatibility for older clients |
All protocol eras are served simultaneously. Modern requests are detected from their required request metadata; legacy clients continue to use initialize and sessions unchanged.
Modern clients can opt into the experimental io.modelcontextprotocol/tasks extension. NeoStack then returns a task immediately for a tool call, allowing the client to poll or cancel it without keeping one HTTP request open. Clients that do not declare the extension receive the normal synchronous tool-call behavior. Resources and prompts are intentionally not advertised until NeoStack has concrete implementations for them.