scriptoriumadmin/supermemory
1
0
Fork 0
mirror of https://github.com/supermemoryai/supermemory.git synced 2026-09-13 23:11:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix(mcp): default container to authenticated userId when x-sm-project is absent

Browse source 
Fixes #792
This commit is contained in:
Teddy Oweh 2026-04-17 07:16:45 -04:00
parent 5493455f69
commit c96c3117ff
1 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
apps/mcp/src/index.ts
View file

@ -113,7 +113,7 @@ const mcpHandler = SupermemoryMCP.serve("/mcp", {
const handleMcpRequest = async (c: Context<{ Bindings: Bindings }>) => {
const authHeader = c.req.header("Authorization")
const token = authHeader?.replace(/^Bearer\s+/i, "")
const containerTag = c.req.header("x-sm-project")
const headerContainerTag = c.req.header("x-sm-project")
const apiUrl = c.env.API_URL || DEFAULT_API_URL
const reqHost = c.req.header("x-forwarded-host") || c.req.header("host") || ""
@ -174,6 +174,14 @@ const handleMcpRequest = async (c: Context<{ Bindings: Bindings }>) => {
)
}
// Default to the authenticated user's id when no explicit project header is
// provided. Without this fallback all MCP sessions share the hard-coded
// `sm_project_default` container inside SupermemoryClient, which is not the
// container the user's direct /v3 and /v4 API calls query — causing writes
// via MCP to be invisible to reads via the REST API and MCP `recall` when
// the client doesn't forward x-sm-project. See issue #792.
const containerTag = headerContainerTag || authUser.userId
// Create execution context with authenticated user props
const ctx = {
...c.executionCtx,