Skip to main content
Glama

create_send_as

Create custom email aliases for Gmail accounts to send messages from different addresses while managing reply-to settings and signatures.

Instructions

Creates a custom send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe email address that appears in the 'From:' header
displayNameNoA name that appears in the 'From:' header
replyToAddressNoAn optional email address that is included in a 'Reply-To:' header
signatureNoAn optional HTML signature
isPrimaryNoWhether this address is the primary address
treatAsAliasNoWhether Gmail should treat this address as an alias

Implementation Reference

  • The handler function that executes the create_send_as tool logic by invoking the Gmail API to create a new send-as alias using the provided parameters.
    async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.create({ userId: 'me', requestBody: params }) return formatResponse(data) }) }
  • Input schema using Zod validators for the parameters required to create a send-as alias.
    { sendAsEmail: z.string().describe("The email address that appears in the 'From:' header"), displayName: z.string().optional().describe("A name that appears in the 'From:' header"), replyToAddress: z.string().optional().describe("An optional email address that is included in a 'Reply-To:' header"), signature: z.string().optional().describe("An optional HTML signature"), isPrimary: z.boolean().optional().describe("Whether this address is the primary address"), treatAsAlias: z.boolean().optional().describe("Whether Gmail should treat this address as an alias") },
  • src/index.ts:1127-1143 (registration)
    Registration of the create_send_as MCP tool on the server, including name, description, input schema, and inline handler.
    server.tool("create_send_as", "Creates a custom send-as alias", { sendAsEmail: z.string().describe("The email address that appears in the 'From:' header"), displayName: z.string().optional().describe("A name that appears in the 'From:' header"), replyToAddress: z.string().optional().describe("An optional email address that is included in a 'Reply-To:' header"), signature: z.string().optional().describe("An optional HTML signature"), isPrimary: z.boolean().optional().describe("Whether this address is the primary address"), treatAsAlias: z.boolean().optional().describe("Whether Gmail should treat this address as an alias") }, async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.create({ userId: 'me', requestBody: params }) return formatResponse(data) }) } )
  • Shared helper function used by the create_send_as handler (and other tools) to manage OAuth2 authentication, Gmail client creation, API execution, and error handling.
    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/faithk7/gmail-mcp'

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