Flexisign

@Flexisign show me all the document templates I have available in my account

Here are your Flexisign templates: 1. **Employee NDA** (ID: tpl_8x9k2) — Standard non-disclosure agreement for new hires 2. **Contractor Agreement** (ID: tpl_4m7n1) — Independent contractor services agreement 3. **Sales Quote** (ID: tpl_2p5q8) — Customer quote template with payment terms 4. **Vendor MSA** (ID: tpl_6r3t9) — Master services agreement for suppliers Each template includes pre-configured signature fields and can be sent for e-signature directly from Flexisign.

This example shows the MCP's single read capability: listing templates. The response format depends on what templates exist in your Flexisign account. This MCP currently offers only template retrieval — you'll need to use Flexisign's web interface or API directly to send documents for signature or manage signing workflows.

@Flexisign what templates do I have that mention 'contractor' or 'freelance' in the name?

Searching your Flexisign templates for 'contractor' or 'freelance': **Contractor Agreement** (ID: tpl_4m7n1) — Independent contractor services agreement This is the only template in your account matching those terms. The template includes sections for scope of work, payment schedule, and intellectual property assignment. It's configured with three signature fields: contractor, company representative, and witness.

This demonstrates pairing the MCP's template list with AI filtering and summarization. The MCP retrieves all templates; the AI narrows results based on your search criteria. Useful when you have many templates and need to find specific ones quickly, though the MCP doesn't support server-side search — all filtering happens after retrieval.

@Flexisign I need to send an NDA to a new hire — which template should I use and what fields does it require?

Based on your Flexisign templates, use **Employee NDA** (template ID: tpl_8x9k2). This template is specifically designed for new hires and includes: **Required signature fields:** - Employee signature and date - Company representative signature and date **Standard clauses:** Confidential information definition, non-disclosure obligations, term duration (typically 2 years post-employment), and return of materials provisions. To send this for signature, you'll need to initiate the signing workflow through Flexisign's web dashboard or API — the MCP currently supports template discovery only, not document sending.

This shows the AI recommending a template based on your stated need, then explaining its structure. The MCP provides the template list; the AI interprets which fits your use case. Note the limitation: this MCP doesn't create or send signature requests, so you'll complete the workflow outside Switchy. Consider this a discovery tool rather than a full document management integration.

When Flexisign works for quarterly template reviews

A 3-person legal ops team at a 40-employee SaaS company runs quarterly audits of their contract templates. They need to confirm which templates exist in Flexisign, compare naming conventions against their internal tracker, and flag any orphaned or outdated versions. The List Templates tool gives them a programmatic snapshot they can diff against their spreadsheet without logging into the Flexisign UI. This works if your template count stays under 50 and you're not modifying templates through the MCP—just inventorying them. If you need to actually read template content or trigger signature workflows, this MCP won't help; you're stuck in the web app. For teams that treat Flexisign as a black box and just need periodic visibility into what templates are live, this is a low-friction compliance check.

Why this MCP falls short for onboarding workflows

A 6-person HR team wants to automate new-hire document assignment: when someone joins, the system should check which Flexisign templates apply to their role and queue them for signature. The List Templates tool can fetch the template inventory, but it can't send documents, check signature status, or pull completed PDFs. You'd need separate API calls outside the MCP to actually execute the workflow. This makes the integration a dead end for anything beyond discovery. If your onboarding process is manual and you just want a quick way to remind yourself which templates exist before you log in and send them by hand, this works. If you're building an automated pipeline, you'll need Flexisign's full API or a different e-signature platform with a richer MCP.

When this MCP helps remote sales teams stay aligned

A 10-person sales team spread across 4 time zones uses Flexisign for NDAs, MSAs, and SOWs. They've had issues with reps using outdated template names or forgetting which version is current. The List Templates tool lets a sales ops lead pull the canonical list into a shared Switchy workspace every Monday, so the team can reference it during deal prep without context-switching to Flexisign. This works because the team isn't creating or editing templates—they're just consuming the list to stay consistent. If your template library changes weekly or you need to preview template content, the single-tool limitation becomes a blocker. For teams that treat the template list as a reference artifact and update it on a slow cadence, this is a lightweight alignment play.