Skip to main content
Glama
matthewbergvinson

Fathom MCP Server

create_webhook

Configure webhooks to automatically send Fathom meeting data to your URL when recordings occur. Choose which recordings trigger events and customize payload content like transcripts, summaries, and action items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destination_urlYesURL to receive webhook events
include_transcriptNoInclude transcript in webhook payload
include_summaryNoInclude summary in webhook payload
include_action_itemsNoInclude action items in webhook payload
include_crm_matchesNoInclude CRM matches in webhook payload
triggered_forNoWhich recordings trigger the webhook

Implementation Reference

  • MCP tool handler function for 'create_webhook'. Calls the Fathom client to create the webhook and returns a formatted markdown response with the webhook details including ID, URL, secret, and configuration.
    async ({ destination_url, include_transcript, include_summary, include_action_items, include_crm_matches, triggered_for }) => {
      console.error(`Creating webhook for ${destination_url}...`);
      
      const webhook = await fathom.createWebhook({
        destination_url,
        include_transcript,
        include_summary,
        include_action_items,
        include_crm_matches,
        triggered_for,
      });
    
      const markdown = `# Webhook Created Successfully\n\n| Field | Value |\n|-------|-------|\n| **ID** | ${webhook.id} |\n| **URL** | ${webhook.url} |\n| **Secret** | \`${webhook.secret}\` |\n| **Include Transcript** | ${webhook.include_transcript} |\n| **Include Summary** | ${webhook.include_summary} |\n| **Include Action Items** | ${webhook.include_action_items} |\n| **Include CRM Matches** | ${webhook.include_crm_matches} |\n| **Triggered For** | ${webhook.triggered_for.join(', ')} |\n\n**Important:** Save the webhook secret securely - you'll need it to verify incoming webhooks.`;
    
      console.error(`Webhook created: ${webhook.id}`);
      return {
        content: [{ type: 'text', text: markdown }],
      };
    }
  • src/index.ts:388-417 (registration)
    Registers the 'create_webhook' tool with the MCP server using server.tool(), including Zod input schema and inline handler function.
    server.tool(
      'create_webhook',
      {
        destination_url: z.string().describe('URL to receive webhook events'),
        include_transcript: z.boolean().optional().describe('Include transcript in webhook payload'),
        include_summary: z.boolean().optional().describe('Include summary in webhook payload'),
        include_action_items: z.boolean().optional().describe('Include action items in webhook payload'),
        include_crm_matches: z.boolean().optional().describe('Include CRM matches in webhook payload'),
        triggered_for: z.array(z.enum(['my_recordings', 'shared_external_recordings', 'my_shared_with_team_recordings', 'shared_team_recordings'])).optional().describe('Which recordings trigger the webhook'),
      },
      async ({ destination_url, include_transcript, include_summary, include_action_items, include_crm_matches, triggered_for }) => {
        console.error(`Creating webhook for ${destination_url}...`);
        
        const webhook = await fathom.createWebhook({
          destination_url,
          include_transcript,
          include_summary,
          include_action_items,
          include_crm_matches,
          triggered_for,
        });
    
        const markdown = `# Webhook Created Successfully\n\n| Field | Value |\n|-------|-------|\n| **ID** | ${webhook.id} |\n| **URL** | ${webhook.url} |\n| **Secret** | \`${webhook.secret}\` |\n| **Include Transcript** | ${webhook.include_transcript} |\n| **Include Summary** | ${webhook.include_summary} |\n| **Include Action Items** | ${webhook.include_action_items} |\n| **Include CRM Matches** | ${webhook.include_crm_matches} |\n| **Triggered For** | ${webhook.triggered_for.join(', ')} |\n\n**Important:** Save the webhook secret securely - you'll need it to verify incoming webhooks.`;
    
        console.error(`Webhook created: ${webhook.id}`);
        return {
          content: [{ type: 'text', text: markdown }],
        };
      }
    );
  • TypeScript interface defining input parameters for creating a webhook, matching the MCP tool schema.
    export interface CreateWebhookParams {
      destination_url: string;
      include_transcript?: boolean;
      include_summary?: boolean;
      include_action_items?: boolean;
      include_crm_matches?: boolean;
      triggered_for?: ('my_recordings' | 'shared_external_recordings' | 'my_shared_with_team_recordings' | 'shared_team_recordings')[];
    }
  • FathomClient method that performs the actual API POST request to /webhooks to create the webhook, used by the MCP handler.
    async createWebhook(params: CreateWebhookParams): Promise<Webhook> {
      return this.request<Webhook>('/webhooks', {
        method: 'POST',
        body: JSON.stringify(params),
      });
    }
  • Zod schema for input validation of the 'create_webhook' MCP tool parameters.
    {
      destination_url: z.string().describe('URL to receive webhook events'),
      include_transcript: z.boolean().optional().describe('Include transcript in webhook payload'),
      include_summary: z.boolean().optional().describe('Include summary in webhook payload'),
      include_action_items: z.boolean().optional().describe('Include action items in webhook payload'),
      include_crm_matches: z.boolean().optional().describe('Include CRM matches in webhook payload'),
      triggered_for: z.array(z.enum(['my_recordings', 'shared_external_recordings', 'my_shared_with_team_recordings', 'shared_team_recordings'])).optional().describe('Which recordings trigger the webhook'),
    },
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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/matthewbergvinson/fathom-mcp'

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