openclaw/mcporter
openclaw/mcporter
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases 9 Wiki Activity
fix/error-code-auth-detection
mcporter/docs/known-issues.md
Peter Steinberger d9bcd4421a docs: note sdk regression and pagination
2025-11-22 02:31:35 +01:00

2.7 KiB
Raw Permalink Blame History

summary read_when
Living list of mcporter limitations, hosted MCP quirks, and upstream gaps.
Triaging a bug that might already be documented

Known Issues

This file tracks limitations that users regularly run into. Most of these require upstream cooperation or larger refactors—feel free to reference this when triaging bugs.

Hosted OAuth servers (Supabase, GitHub MCP, etc.)

  • Supabase’s hosted MCP server rejects the standard mcp:tools scope and only accepts Supabase-specific scopes (projects:read, database:write, ...). Because they do not expose OAuth discovery metadata or scope negotiation, mcporter cannot auto-register or complete the flow. Workarounds:
    • Use Supabase’s supported clients (Cursor, Windsurf).
    • Self-host their MCP server and configure PAT headers / custom OAuth.
    • Ask Supabase to accept the MCP scope or publish their scope list.
  • GitHub’s MCP endpoint (https://api.githubcopilot.com/mcp/) returns “does not support dynamic client registration” when mcporter attempts to connect. Copilot’s backend expects pre-registered client credentials. Until GitHub publishes a dynamic-registration API (or client secrets), mcporter cannot interact with their hosted server.

Output schemas missing/buggy on many servers

  • The MCP spec allows servers to omit outputSchema. In practice, many hosted MCPs return empty or inconsistent schemas, so features that rely on return types (TypeScript signatures, generated CLIs, createServerProxy return helpers) may degrade to unknown.
  • Workarounds: inspect the server’s README / manual docs for output details, or wrap the tool via createServerProxy and handle the raw envelope manually.
  • Potential improvement: allow user-provided schema overrides (e.g., mcporter config patch, CLI flag to load schema JSON) so we can fill gaps on a per-tool basis.

MCP SDK 1.22.0 inline-stdio regression

  • Upgrading @modelcontextprotocol/sdk to 1.22.0 causes mcporter generate-cli --compile (and direct runtime listTools) to fail against inline STDIO servers with MCP error -32603: Cannot read properties of undefined (reading 'typeName').
  • Repro: pnpm mcporter generate-cli "node mock-stdio.mjs" --compile /tmp/inline-cli --runtime bun using the inline stdio harness in tests/cli-generate-cli.integration.test.ts.
  • Status: reproduced locally; pinned the SDK to ~1.21.2 until upstream ships a fix.

Next Steps

  • Implement true scope negotiation (read discovery metadata, allow --oauth-scope).
  • Keep lobbying providers for spec-compliant OAuth behavior.
  • Consider adding schema override hooks or auto-caching schema snapshots per tool.

If you run into other recurring pain points, append them here so we can prioritize fixes.