Skip to content

VS Code Fictura get_pull_request_status

How to: VS Code Fictura get_pull_request_status

client:VS Code transport:streamable-http tool:get_pull_request_status

Add Fictura to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.fictura.co/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something get_pull_request_status does. VS Code lists the server's tools on connect and calls get_pull_request_status itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Fictura's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

Fictura will not start until these are set, so get_pull_request_status never becomes available.

  • FICTURA_MCP_KEY
  • FICTURA_API_BASE

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.