René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[vscode] Error loading MCP App: MPC -32002: Resource not found","articleBody":"### Describe the bug\n\nWhen using the `github-pull-request_create_pull_request` tool from the VS Code GitHub Pull Requests extension (which internally calls the GitHub MCP Server), the operation succeeds and returns the created PR data, but immediately after, an error dialog appears:\n\n`Error loading MCP App: MPC -32002: Resource not found`\n\nThe PR is actually created successfully (confirmed by visiting the returned URL), but the MCP server throws a JSON-RPC error (-32002) when attempting to load or resolve a resource after the creation call completes.\n\n### Affected version\n\nEnvironment:\n- VS Code Insiders (May 2026)\n- OS: Windows\n- MCP integration: VS Code built-in MCP support\n- The MCP server version is managed by VS Code — not running via Docker\n- Docker version check failed with exit code 1 (image not available locally)\n\n### Steps to reproduce the behavior\n\n1. Open a VS Code workspace connected to a GitHub repository (e.g., `microsoft/testfx`)\n2. Push a branch to GitHub\n3. Use an AI agent tool that calls `github-pull-request_create_pull_request` (or the equivalent `mcp_io_github_git_create_pull_request`) to create a pull request\n4. The PR is created successfully and the tool returns `{\"id\":\"...\",\"url\":\"https://github.com/...\"}`\n5. An error dialog appears: `Error loading MCP App: MPC -32002: Resource not found`\n\n### Expected vs actual behavior\n\n**Expected:** The PR creation completes without errors. No error dialog should appear.\n\n**Actual:** The PR is created successfully, but a `MPC -32002: Resource not found` error dialog is shown immediately after. This suggests the MCP server is trying to resolve a resource (possibly a notification or follow-up resource lookup) that doesn't exist or isn't registered.\n\n### Logs\n\nError loading MCP App: MPC -32002: Resource not found\n\nNo additional stack trace was surfaced in the VS Code UI. ","author":{"url":"https://github.com/Evangelink","@type":"Person","name":"Evangelink"},"datePublished":"2026-05-13T10:51:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/2467/github-mcp-server/issues/2467"}