Claude Code, Cursor and other clients

One command in your terminal, then sign in from inside Claude Code.

claude mcp add --transport http docstox https://mcp.docstox.com/mcp

Add --scope user to make it available in every project, not just this one.

Start Claude Code and type /mcp. Select docstox, choose Authenticate, sign in on docstox.com and click Allow. Back in Claude Code, ask about any NSE or BSE stock.

Prefer an API key? Skip the sign-in by sending your key as a header instead. Create one at /mcp/keys first.

claude mcp add --transport http docstox https://mcp.docstox.com/mcp \
  --header "Authorization: Bearer dox-YOUR_KEY_HERE"

Create an API key at /mcp/keys and copy it.

Open ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one project. Add the block below with your key in place of the placeholder.

{
  "mcpServers": {
    "docstox": {
      "url": "https://mcp.docstox.com/mcp",
      "headers": {
        "Authorization": "Bearer dox-YOUR_KEY_HERE"
      }
    }
  }
}

Save. DocStoX appears in Cursor's MCP list with its tools. Toggle it on if it is off, then ask in the Agent chat.

To keep the key out of the file, set an environment variable and write "Bearer ${env:DOCSTOX_API_KEY}" as the header value.

GitHub Copilot in VS Code connects to remote MCP servers and signs in through your browser.

Open the Command Palette (Ctrl Shift P, or Cmd Shift P on a Mac) and run MCP: Add Server. Choose HTTP, paste the server URL below and name it docstox. Pick where to save it: this workspace, or globally.

https://mcp.docstox.com/mcp

When VS Code asks to authenticate, allow it. Sign in on docstox.com and click Allow. Open Copilot Chat in Agent mode: DocStoX's tools appear in the tools picker.

You can also configure it by file, or with an API key instead of signing in. The same server goes in .vscode/mcp.json; remove the headers block to use OAuth instead.

{
  "servers": {
    "docstox": {
      "type": "http",
      "url": "https://mcp.docstox.com/mcp",
      "headers": {
        "Authorization": "Bearer dox-YOUR_KEY_HERE"
      }
    }
  }
}

For the OpenAI Codex CLI and IDE extension. Both read the same config.toml.

Create an API key at /mcp/keys and store it in an environment variable named DOCSTOX_API_KEY. Add this table to ~/.codex/config.toml. Codex reads the key from the variable, so it never sits in the file.

[mcp_servers.docstox]
url = "https://mcp.docstox.com/mcp"
bearer_token_env_var = "DOCSTOX_API_KEY"

Start codex and type /mcp. DocStoX is listed with its tools.

Codex also supports signing in instead of using a key. Add the server without a key, then log in; a browser window opens on docstox.com.

codex mcp add docstox --url https://mcp.docstox.com/mcp
codex mcp login docstox

Gemini CLI connects to the remote URL directly. No bridge needed.

Create an API key at /mcp/keys and copy it. Add the server for your user account, with your key in place of the placeholder.

gemini mcp add --transport http --scope user \
  --header "Authorization: Bearer dox-YOUR_KEY_HERE" \
  docstox https://mcp.docstox.com/mcp

Run gemini and type /mcp to see DocStoX and its tools.

The command above writes this entry to ~/.gemini/settings.json. Note the key is httpUrl, not url.

{
  "mcpServers": {
    "docstox": {
      "httpUrl": "https://mcp.docstox.com/mcp",
      "headers": {
        "Authorization": "Bearer dox-YOUR_KEY_HERE"
      }
    }
  }
}

Create an API key at /mcp/keys and copy it.

In the Cascade panel, open the ... menu at the top right, then select the Open MCP config file icon in the MCPs section. Add the entry below under mcpServers and save. Windsurf uses serverUrl for remote servers.

{
  "mcpServers": {
    "docstox": {
      "serverUrl": "https://mcp.docstox.com/mcp",
      "headers": {
        "Authorization": "Bearer dox-YOUR_KEY_HERE"
      }
    }
  }
}

Check the MCPs list shows DocStoX with its tools enabled.