Skip to main content
Glama

updateNamespace

Modify an existing namespace configuration in SourceSync.ai to update storage, embedding, and integration settings for content management.

Instructions

Updates an existing namespace with the provided configuration parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceIdNo
fileStorageConfigNo
vectorStorageConfigNo
embeddingModelConfigNo
webScraperConfigNo
notionConfigNo
googleDriveConfigNo
dropboxConfigNo
onedriveConfigNo
boxConfigNo
sharepointConfigNo
tenantIdNo

Implementation Reference

  • MCP tool registration and handler implementation for 'updateNamespace'. Creates a SourceSync client instance and delegates to its updateNamespace method, wrapped in error handling.
    server.tool(
      'updateNamespace',
      'Updates an existing namespace with the provided configuration parameters.',
      updateNamespaceSchema.shape,
      async (params: UpdateNamespaceParams) => {
        return safeApiCall(async () => {
          const { namespaceId, tenantId, ...updateParams } = params
    
          // Create a client with the provided API key
          const client = createClient({ namespaceId, tenantId })
    
          return await client.updateNamespace(updateParams)
        })
      },
    )
  • Zod schema defining the input parameters for the updateNamespace tool, including optional configs for storage, embedding, and connectors.
    export const updateNamespaceSchema = z.object({
      namespaceId: namespaceIdSchema,
      fileStorageConfig: fileStorageConfigSchema.optional(),
      vectorStorageConfig: vectorStorageConfigSchema.optional(),
      embeddingModelConfig: embeddingModelConfigSchema.optional(),
      webScraperConfig: webScraperConfigSchema.optional(),
      notionConfig: notionConfigSchema.optional(),
      googleDriveConfig: googleDriveConfigSchema.optional(),
      dropboxConfig: dropboxConfigSchema.optional(),
      onedriveConfig: onedriveConfigSchema.optional(),
      boxConfig: boxConfigSchema.optional(),
      sharepointConfig: sharepointConfigSchema.optional(),
      tenantId: tenantIdSchema,
    })
  • SourceSyncApiClient.updateNamespace method, which performs a PATCH request to /v1/namespaces/{namespaceId} with the provided config updates. This is the core API implementation called by the MCP handler.
    public async updateNamespace({
      fileStorageConfig,
      vectorStorageConfig,
      embeddingModelConfig,
      webScraperConfig,
      notionConfig,
      googleDriveConfig,
      dropboxConfig,
      onedriveConfig,
      boxConfig,
      sharepointConfig,
    }: SourceSyncUpdateNamespaceRequest): Promise<SourceSyncUpdateNamespaceResponse> {
      return this.client
        .url(`/v1/namespaces/${this.namespaceId}`)
        .json({
          fileStorageConfig,
          vectorStorageConfig,
          embeddingModelConfig,
          webScraperConfig,
          notionConfig,
          googleDriveConfig,
          dropboxConfig,
          onedriveConfig,
          boxConfig,
          sharepointConfig,
        } satisfies SourceSyncUpdateNamespaceRequest)
        .patch()
        .json<SourceSyncUpdateNamespaceResponse>()
    }
  • TypeScript type inferred from the updateNamespaceSchema for input validation.
    export type UpdateNamespaceParams = z.infer<typeof updateNamespaceSchema>
  • Type definitions for SourceSyncUpdateNamespaceRequest and Response used by the client implementation.
    export type SourceSyncUpdateNamespaceRequest = {
      fileStorageConfig?: SourceSyncFileStorageConfig
      vectorStorageConfig?: SourceSyncVectorStorageConfig
      embeddingModelConfig?: SourceSyncEmbeddingModelConfig
      webScraperConfig?: SourceSyncWebScraperConfig
      notionConfig?: SourceSyncNotionConfig
      googleDriveConfig?: SourceSyncGoogleDriveConfig
      dropboxConfig?: SourceSyncDropboxConfig
      onedriveConfig?: SourceSyncOnedriveConfig
      boxConfig?: SourceSyncBoxConfig
      sharepointConfig?: SourceSyncSharepointConfig
    }
    
    export type SourceSyncUpdateNamespaceResponse =

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pbteja1998/sourcesyncai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server