@pitchmentor/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PITCHMENTOR_API_KEY | Yes | A team API key (pm_live_…, created in the Pitch Mentor dashboard), sent as Authorization: Bearer pm_live_…. Use a key with only the scopes you want the assistant to have, e.g. read-only scopes (calls:read, analytics:read, …) for an analysis assistant. | |
| PITCHMENTOR_BASE_URL | No | Optionally overrides the API host. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_meC | The team and API key making the request. |
| list_callsA | List calls (newest first). Paginated: pass Requires scope |
| export_callsB | Export calls as CSV or JSON. Requires scope |
| get_callA | Get a call with transcript and coaching log. Requires scope |
| summarize_callA | Generate (or return the existing) AI summary. Generating a new summary uses the team's token quota. Requires scope |
| archive_callA | Archive a call (hidden from history and analytics, not deleted). Requires scope |
| unarchive_callB | Restore an archived call. Requires scope |
| get_analytics_overviewC | Team call analytics. Requires scope |
| get_analytics_by_memberC | Per-member call stats. Requires scope |
| list_leadsA | List leads (newest first). Paginated: pass Requires scope |
| upsert_leadB | Create a lead, or update the one with the same externalId. Requires scope |
| batch_upsert_leadsA | Import up to 100 leads (upsert on externalId; omitted fields are cleared on update). Requires scope |
| get_leadC | Get a lead. Requires scope |
| update_leadB | Update a lead (only provided fields change). Requires scope |
| get_team_configB | Team settings and coaching context. Requires scope |
| update_team_configC | Update team settings. Requires scope |
| list_membersA | List team members. Requires scope |
| remove_memberA | Remove a member from the team. DESTRUCTIVE: this cannot be undone. Only call it when the user explicitly asked for exactly this action. The member keeps their account and calls; managers can't be removed via the API. Requires scope DESTRUCTIVE: cannot be undone. |
| list_invitesA | List pending invites. Requires scope |
| create_inviteA | Create an invite link (counts against the seat limit). Requires scope |
| cancel_inviteB | Cancel a pending invite. DESTRUCTIVE: this cannot be undone. Only call it when the user explicitly asked for exactly this action. Requires scope DESTRUCTIVE: cannot be undone. |
| list_coaching_stylesB | Built-in and team coaching styles. Requires scope |
| create_coaching_styleB | Create a custom coaching style (Premium/Enterprise). Requires scope |
| update_coaching_styleB | Update a custom coaching style. Requires scope |
| get_billing_statusB | Plan and subscription status. Requires scope |
| get_usageA | Token and seat usage for the current period. Requires scope |
| list_member_usageB | Per-member usage for the current period. Requires scope |
| get_referral_statsB | Referral link and stats. Requires scope |
| list_api_keysA | List API keys (including revoked). Paginated: pass Requires scope |
| create_api_keyA | Create an API key (the key is returned once). The result contains a secret that is shown only once; show it to the user and do not repeat it elsewhere. Requires scope |
| rotate_api_keyA | Replace the key's secret (the old secret stops working immediately). DESTRUCTIVE: this cannot be undone. Only call it when the user explicitly asked for exactly this action. Requires scope DESTRUCTIVE: cannot be undone. |
| revoke_api_keyA | Revoke an API key. DESTRUCTIVE: this cannot be undone. Only call it when the user explicitly asked for exactly this action. Requires scope DESTRUCTIVE: cannot be undone. |
| list_webhook_endpointsA | List webhook endpoints. Paginated: pass Requires scope |
| create_webhook_endpointA | Add a webhook endpoint (the signing secret is returned once). The result contains a secret that is shown only once; show it to the user and do not repeat it elsewhere. Requires scope |
| get_webhook_endpointB | Get a webhook endpoint. Requires scope |
| update_webhook_endpointC | Update, disable or re-enable a webhook endpoint. Requires scope |
| delete_webhook_endpointA | Delete a webhook endpoint and its delivery log. DESTRUCTIVE: this cannot be undone. Only call it when the user explicitly asked for exactly this action. Requires scope DESTRUCTIVE: cannot be undone. |
| rotate_webhook_secretA | Replace the signing secret (returned once; takes effect immediately). DESTRUCTIVE: this cannot be undone. Only call it when the user explicitly asked for exactly this action. The result contains a secret that is shown only once; show it to the user and do not repeat it elsewhere. Requires scope DESTRUCTIVE: cannot be undone. |
| test_webhook_endpointA | Send a signed webhook.test event now and return the delivery result. Requires scope |
| list_webhook_deliveriesA | Delivery log for an endpoint (newest first). Paginated: pass Requires scope |
| replay_webhook_deliveryB | Queue the same message again (same webhook-id, new delivery record). Requires scope |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 41 tools
Most tools map to a single resource+action, and descriptions clearly separate similar operations (get_call vs summarize_call, get_webhook_endpoint vs test_webhook_endpoint). Some boundaries blur within analytics/usage (get_analytics_overview, get_analytics_by_member, get_usage, list_member_usage) and lead writing (upsert_lead vs update_lead vs batch_upsert_leads), but scope labels and descriptions help an agent choose correctly.
Every tool follows a strict verb_noun snake_case pattern (list_leads, get_call, create_api_key, rotate_webhook_secret). Voice and noun phrasing are consistent across all domains, making names highly predictable.
41 tools is heavy, though the server covers many distinct domains (calls, leads, webhooks, team, billing, coaching, API keys, analytics). Each tool generally earns its place, but the surface is large enough that it approaches the limit of comfortable scoping for an agent.
Core lifecycle coverage is strong for webhooks, API keys, team/invites, and leads. Minor gaps exist: no delete operation for leads, calls, or custom coaching styles (only archive for calls), and analytics is limited to overview and per-member without time-series granularity.