Skip to content

Scoped servers:write token is rejected by mcp publish for an existing namespace #796

Description

@nimatime

Summary

smithery mcp publish rejects both the logged-in OAuth token and a freshly minted short-lived servers:write token when updating an existing external server in the authenticated namespace.

Reproduction

smithery auth whoami
# Namespace: agenticempire

smithery auth token --policy '{"resources":"servers","operations":"write","ttl":"10m"}'
# token is returned successfully

SMITHERY_API_KEY="$SCOPED_TOKEN" smithery mcp publish \
  https://mcp.axint.ai/mcp \
  -n agenticempire/axint

Actual result:

Permission denied: 403 Missing required permission: servers:write

The same result occurs when adding "namespaces":"agenticempire" to the policy. No token values are included here.

Expected

A token minted with resources=servers, operations=write, and a short TTL should satisfy servers:write for a server in the authenticated namespace.

Context

The public endpoint is healthy and serves a current MCP server card at https://mcp.axint.ai/server.json. The existing Smithery listing is stale at 34 tools while the endpoint exposes 36 tools and 5 prompts, so this blocks a normal maintainer refresh.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions