Skip to main content
Glama

insert_smime_info

Upload and configure S/MIME settings for a specific send-as email alias using PKCS#12 format, ensuring secure email communication via the Gmail MCP server.

Instructions

Insert (upload) the given S/MIME config for the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
encryptedKeyPasswordYesEncrypted key password
pkcs12YesPKCS#12 format containing a single private/public key pair and certificate chain
sendAsEmailYesThe email address that appears in the 'From:' header

Implementation Reference

  • src/index.ts:1261-1274 (registration)
    Registration of the 'insert_smime_info' tool, including input schema and handler function that uses the Gmail API to insert S/MIME configuration for a send-as alias.
    server.tool("insert_smime_info", "Insert (upload) the given S/MIME config for the specified send-as alias", { sendAsEmail: z.string().describe("The email address that appears in the 'From:' header"), encryptedKeyPassword: z.string().describe("Encrypted key password"), pkcs12: z.string().describe("PKCS#12 format containing a single private/public key pair and certificate chain") }, async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.smimeInfo.insert({ userId: 'me', sendAsEmail: params.sendAsEmail, requestBody: params }) return formatResponse(data) }) } )
  • Input schema (Zod validation) for the 'insert_smime_info' tool parameters.
    { sendAsEmail: z.string().describe("The email address that appears in the 'From:' header"), encryptedKeyPassword: z.string().describe("Encrypted key password"), pkcs12: z.string().describe("PKCS#12 format containing a single private/public key pair and certificate chain") },
  • Handler function for 'insert_smime_info' tool that calls Gmail API's smimeInfo.insert method.
    async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.smimeInfo.insert({ userId: 'me', sendAsEmail: params.sendAsEmail, requestBody: params }) return formatResponse(data) }) }
  • Shared 'handleTool' helper function used by the 'insert_smime_info' handler to manage OAuth authentication and Gmail API calls.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => { try { const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials') const credentialsAreValid = await validateCredentials(oauth2Client) if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate') const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials') const result = await apiCall(gmailClient) return result } catch (error: any) { // Check for specific authentication errors if ( error.message?.includes("invalid_grant") || error.message?.includes("refresh_token") || error.message?.includes("invalid_client") || error.message?.includes("unauthorized_client") || error.code === 401 || error.code === 403 ) { return formatResponse({ error: `Authentication failed: ${error.message}. Please re-authenticate by running: npx @shinzolabs/gmail-mcp auth`, }); } return formatResponse({ error: `Tool execution failed: ${error.message}` }); } }

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/shinzo-labs/gmail-mcp'

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