VS Code added MCP support (GA, July 2025) through the GitHub Copilot extension. With apex-mcp configured, Copilot’s Agent mode gains all 116 Oracle APEX tools — enabling you to generate pages, run schema inspections, and build complete applications directly from the editor chat panel. Two transport modes are available:Documentation Index
Fetch the complete documentation index at: https://mintlify.com/TechFernandesLTDA/apex-mcp/llms.txt
Use this file to discover all available pages before exploring further.
stdio for local development and http for GitHub Codespaces or any remote development environment.
VS Code uses a different config format from Claude, Cursor, and Gemini. The top-level key is
"servers" (not "mcpServers") and each entry requires a "type" field ("stdio" or "http"). Using the wrong format will cause VS Code to silently ignore the configuration.Stdio Mode (local development)
Use this mode when apex-mcp and VS Code are running on the same machine.Create .vscode/mcp.json
Create the file Replace every
.vscode/mcp.json at the root of your project (or edit it if it already exists). Note the VS Code-specific format: "servers" at the top level and "type": "stdio" on each entry.YOUR_* placeholder with your actual Oracle and APEX credentials. The ORACLE_WALLET_DIR path must be absolute and point to the directory containing cwallet.sso.Unlike Cursor and Claude Code, VS Code’s stdio config does not require a cwd field — the working directory defaults to the workspace root. If your apex-mcp install is elsewhere, add "cwd": "/absolute/path/to/apex-mcp".Enable the MCP server
Open VS Code in the apex-mcp directory. VS Code will detect the new
.vscode/mcp.json and display a prompt: “Enable MCP server ‘apex-mcp’?” — click Enable.If the prompt does not appear, open the Command Palette (⇧⌘P / Ctrl+Shift+P) and run MCP: List Servers to check the server status.HTTP Mode (Codespaces and remote development)
When VS Code is connected to a remote host, a dev container, or GitHub Codespaces, the stdio transport cannot cross the local/remote boundary. Use HTTP mode instead: start apex-mcp as an HTTP server inside the remote environment and point VS Code at its URL.Start apex-mcp in HTTP mode inside the remote environment
In the integrated terminal of your Codespace or remote host, export your Oracle credentials and start the server:The server will be available at
http://localhost:8000/mcp (VS Code port-forwards it automatically in Codespaces).Update .vscode/mcp.json to use HTTP transport
Replace the stdio configuration with an HTTP entry. The
"type": "http" format does not require command, args, or env — just the server URL:Config Format Reference
VS Code’s MCP format differs from the other supported clients. Keep this table handy when adapting configs:| Client | Top-level key | type field |
|---|---|---|
| VS Code | "servers" | Required — "stdio" or "http" |
| Claude Code | "mcpServers" | Not used |
| Cursor | "mcpServers" | Not used |
| Gemini CLI | "mcpServers" | Not used |
Troubleshooting
| Problem | Solution |
|---|---|
| No tools shown in Agent mode | Check View → Output → MCP for error details |
"servers" not recognized | Confirm VS Code 1.93+ and that the Copilot extension is up to date |
"type" is required error | Add "type": "stdio" or "type": "http" to the server entry |
| Tools visible but fail | Verify env vars — ORACLE_WALLET_DIR must be an absolute path to the wallet directory |
| Works locally, fails in remote | Switch to HTTP transport mode (see above) |
| Enable prompt never appeared | Run MCP: List Servers from the Command Palette to trigger server registration |
