Solution skill
Apideck MCP: scopes not applied and body consumer_id overrides header
Complete solution
Apideck MCP: scopes not applied and body consumer_id overrides header. All three were fixed in 0.20.1 on npm and on the hosted endpoint. Use when hitting this exact issue with Apideck MCP. Not for unrelated errors or different features.
TL;DR
All three were fixed in 0.20.1 on npm and on the hosted endpoint. Use ?scopes=read (or read,write) on the hosted endpoint, or repeat the --scope flag on the CLI to combine scopes; listtools now hides out-of-scope tools and the header consumerid wins.
Fix
All three were fixed in 0.20.1 on npm and on the hosted endpoint. Expected: You get the expected result; the problem is gone.
Use ?scopes=read (or read,write) on the hosted endpoint, or repeat the --scope flag on the CLI to combine scopes; listtools now hides out-of-scope tools and the header consumerid wins. Expected: You get the expected result; the problem is gone.
When to use
- You are setting up or using this Apideck MCP feature.
- The symptom matches: scopes not applied and body consumer_id overrides header.
When NOT to use
- Unrelated Apideck MCP issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported against Apideck MCP (mentions 0.19.0, 0.20.1).
Variant phrasings
scopes not applied and body consumer_id overrides header
Why it happens
GitHub issue on apideck-libraries/mcp 0.19.0: the scopes query param and CLI scope flag were never applied, listtools did not hide out-of-scope tools, and a consumerid in the request body overrode the one in the header.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- Behavior can change between releases; the linked source reflects the versions above.
- If the fix does not help, capture the full error output and check the source link for updates.
Evidence
GitHub issue on apideck-libraries/mcp 0.19.0: the scopes query param and CLI scope flag were never applied, listtools did not hide out-of-scope tools, and a consumerid in the request body overrode the one in the header. Resolved: All three were fixed in 0.20.1 on npm and on the hosted endpoint. Use ?scopes=read (or read,write) on the hosted endpoint, or repeat the --scope flag on the CLI to combine scopes; listtools now hides out-of-scope tools and the header consumerid wins. Source: https://github.com/apideck-libraries/mcp/issues/62
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_ab-KFWZXF-IWGlpB3IqSHQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Apideck MCP: scopes not applied and body consumer_id overrides header <span>— Vectle</span></a>