pitchmachine-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PITCHMACHINE_API_BASE | No | Base URL for the Pitch Machine API. Point at staging if needed. | https://pitchmachine.ai |
| PITCHMACHINE_API_TOKEN | Yes | Supabase session JWT (v0 auth). Grab it from pitchmachine.ai. | |
| PITCHMACHINE_REQUEST_TIMEOUT_MS | No | Per-request HTTP timeout in milliseconds. | 30000 |
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 |
|---|---|
| pitchmachine_create_receiverA | Create a new receiver (a prospect or contact) in Pitch Machine. audience_mode='b2b' requires company_name + contact_email. audience_mode='b2c' requires receiver_email. Returns receiver_id, used as the input to pitchmachine_generate_pitch. |
| pitchmachine_generate_pitchA | Kick off pitch generation for an existing receiver and poll until it completes. Returns the public share URL (pitchmachine.ai/p/?t=) on success. If generation takes longer than poll_timeout_seconds, returns the in-progress status; call pitchmachine_get_pitch_url later with the returned pitch_id. Does NOT send the pitch — that's the agent's job (or a human's). |
| pitchmachine_get_pitch_urlA | Fetch the current state and public share URL for a pitch by pitch_id. Use this to resume after pitchmachine_generate_pitch timed out, to re-share a URL later, or to check the status of any past pitch. |
| pitchmachine_list_pitchesA | List recent pitches for the authenticated Pitch Machine account. Use this to discover pitch_ids for pitches created outside this agent session, or to audit what an agent has already generated. Optional filters: status_filter, since (ISO timestamp), limit. |
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 4 tools
Each tool has a distinct responsibility: creating a receiver, generating a pitch, retrieving a pitch URL/status, and listing pitches. There is no overlap or ambiguity between them.
All tools follow a consistent 'pitchmachine_<verb>_<noun>' pattern (create_receiver, generate_pitch, get_pitch_url, list_pitches). Naming is uniform and predictable.
Four tools is appropriately scoped for a specialized pitch-generation workflow. Each tool is necessary and covers a distinct step in the lifecycle.
The tools cover the entire pitch workflow: creating a receiver, generating a pitch, retrieving the shareable URL (including resuming after timeout), and listing past pitches. No obvious gaps exist for the stated purpose.