# Spondyr — MCP server on mcp.ai
> Connect your Spondyr account and use 21 tools for documents straight from your AI agent. Connect with your own API key. Spondyr is a correspondence template management and distribution platform that enables developers to quickly integrate template-driven content delivery via API, supporting email, SMS, fax, and postal mail.

By: mcp.ai · official
Page: https://mcp.ai/spondyr

## Connect (MCP protocol)
Remote MCP endpoint (HTTP, streamable): https://api.mcp.ai/p_spondyr?ms=1787293560000
Add it as a custom/remote MCP connector, then authenticate when prompted.

## REST API (no MCP client required)
Every tool is also a REST endpoint, authed with a workspace API key.
Discover: GET https://api.mcp.ai/api/spondyr/_endpoints   # public; lists every endpoint
Call:     POST https://api.mcp.ai/api/spondyr/<endpoint>
  Authorization: Bearer sk_live_…   # create one at https://mcp.ai/settings/api-keys
  Content-Type: application/json
  Body: { …args }   →   { "ok": true, "tool": "<id>", "result": { … } }

## Developer docs
How to use (MCP or REST), markdown: https://mcp.ai/spondyr/skill.md
Postman collection (v2.1): https://mcp.ai/spondyr/postman.json

## Tools
- spondyr_conditions_list(TransactionType: string) — Tool to list all conditions for a transaction type. Use when you need to discover existing condition rules before creating templates or generating correspondence. Conditions define criteria for select
- spondyr_create_condition(Name: string, FieldName: string, PossibleValues?: string, TransactionType: string) — Create a condition rule for template selection in Spondyr. Conditions define matching criteria on transaction data fields that determine which document template to use. For example, create a condition
- spondyr_create_transaction_type(Name: string, TemplateJSON: string) — Tool to create a new transaction type. Use after defining the JSON schema for your data to register it in Spondyr.
- spondyr_deliver_spondyr(Template?: string, ReferenceID: string, NewRecipients?: object[], OriginalRecipients?: string) — Trigger delivery of previously generated correspondence to recipients. Use this action after generating correspondence (via POST /Spondyr with IsGenerateOnly=true) to actually deliver the documents vi
- spondyr_event_type_update(Name: string, EventType: string, TransactionType: string) — Tool to update an existing event type name within a transaction type. Use when you need to rename an Event Type. Example: Rename the 'OrderShipped' event to 'OrderDelivered' within the 'CustomerOrders
- spondyr_get_event_types(TransactionType: string) — Retrieves all event types associated with a specific transaction type in Spondyr. Event types define the kinds of events that can occur for a transaction type (e.g., "Created", "Updated", "Cancelled" 
- spondyr_get_spondyr_status(LastName?: string, FirstName?: string, IncludeData?: boolean, ReferenceID: string, ApplicationUserID?: string) — Tool to retrieve the status of a previously generated correspondence. Use after generating correspondence to check its processing and delivery status.
- spondyr_get_transaction_types() — Tool to retrieve a list of available transaction types. Use after authentication to discover data schemas.
- spondyr_recipient_delete(Recipient: string, TransactionType: string) — Deletes a recipient configuration from a transaction type in Spondyr. Recipients are configured delivery endpoints (email addresses, fax numbers, physical addresses) that determine where correspondenc
- spondyr_recipient_get(Recipient: string, TransactionType: string) — Tool to retrieve details of a specific recipient. Use when you need to fetch recipient configuration for a given transaction type. Example: "Retrieve recipient 'Customer' for transaction type 'OrderPl
- spondyr_recipients_list(TransactionType: string) — Tool to list all recipients for a transaction type. Use when you need to discover or verify all configured recipients before sending or managing correspondence.
- spondyr_search_filter_create(Tag: string, Name: string, TransactionType: string) — Create a new search filter for a transaction type in Spondyr. Search filters enable you to define searchable fields within your transaction data. Once created, these filters allow you to quickly searc
- spondyr_search_filter_delete(Search: string, TransactionType: string) — Deletes a specific search filter from the Spondyr system. Use this when you need to remove a search filter that is no longer needed. Both the filter name and transaction type must exactly match the va
- spondyr_search_filter_get(Search: string, TransactionType: string) — Retrieves details of a specific search filter in Spondyr by name and transaction type. Returns the filter's name, tag value, and associated transaction type. Use this when you need to look up an exist
- spondyr_search_filters_list(TransactionType: string) — Tool to list all search filters for a transaction type. Use when you need to discover available filters before searching correspondence.
- spondyr_search_spondyrs(Page?: integer, PageSize?: integer, EventType?: string, SortOrder?: string, SearchName?: string, SortColumn?: string, SearchValue?: string, BatchReferenceID?: string) — Search for generated correspondence (spondyrs) by multiple criteria including batch ID, event type, and custom search filters. Returns paginated results with delivery status, recipient information, an
- spondyr_sso_stub(Role: string, LastName: string, TimeZone?: string, FirstName: string, TenantToken?: string, ApplicationUserID: string) — Tool to create a one-time SSO user stub in Spondyr. Use after application authentication to generate a temporary SSO token for embedding or redirecting users.
- spondyr_template_get(Template: string, TransactionType: string) — Retrieve detailed configuration for a specific correspondence template. Returns template content reference ID, event type, recipients, delivery methods, conditions, and search filters. Use this action
- spondyr_templates_list(TransactionType: string) — List all templates configured for a transaction type. Use this to discover available templates before generating correspondence or to audit template configurations. Returns template metadata including
- spondyr_transaction_type_get(TransactionType: string) — Tool to retrieve details of a specific transaction type. Use when inspecting a transaction type schema. Returns the schema definition including JSON structure and CSV field mappings. Example: "Get tra
- spondyr_transaction_type_update(Name: string, TemplateJSON: string, TransactionType: string) — Updates an existing transaction type's name and/or JSON schema in Spondyr. Use this tool to: - Modify the JSON schema/template of a transaction type to add, remove, or change data fields - Rename an e

## Example prompts
- "What can I do in Spondyr?"
- "Show me a summary of my Spondyr account"

## Links
Docs: https://mcp.ai/docs/mcps/spondyr
Website: https://mcp.ai/mcps/spondyr