Boloforms
BoloForms is an eSignature platform designed for small businesses, offering unlimited signatures, templates, forms, and team members at a fixed price.
Verdict
Common use cases
- Audit submitted onboarding documents weekly
- Check which clients sent compliance forms
- Triage intake requests by document status
- Generate weekly submission reports for ops
- Cross-reference form IDs during support calls
Integration
- Vendor
- Boloforms
- Category
- other
- Auth
- API_KEY
- Tools
- 1
- Composio slug
boloforms
Tools
- Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Search for Boloforms in the MCP directory and click Connect. 3. You'll be prompted to enter your Boloforms API key—find this in your Boloforms account under Settings > API Access or Developer Settings. 4. Paste the key into Switchy and click Authorize. 5. Switchy will confirm the connection and show Boloforms as active in your integrations list. 6. To test it, open any Space and type '@Boloforms get my documents' in the chat. 7. The MCP should return a list of documents from your account within a few seconds. 8. If you see an authentication error, double-check that the API key has read permissions enabled in Boloforms.
What teammates see: by default, memories from Boloforms are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Recent Documents
@Boloforms get the list of all documents in my account. Show me the most recent 10 submissions with their titles and submission dates.Open in a Space →
Weekly Submission Summary
@Boloforms retrieve all documents submitted in the last 7 days. Summarize the count by document type and highlight any gaps in expected submissions.Open in a Space →
Onboarding Status Check
@Boloforms list all documents tagged with 'onboarding' or 'new client'. Tell me which ones are still pending and which were completed this month.Open in a Space →
Compliance Audit Prep
@Boloforms get the complete list of documents in my account. Export the titles, submission dates, and any associated metadata so I can prepare for our quarterly audit.Open in a Space →
Support Ticket Lookup
@Boloforms search my documents for anything matching 'invoice' or 'receipt' submitted in the last 30 days. Return the document IDs and submission timestamps.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Boloforms show me all the documents in my account organized by creation date
Retrieved 12 documents from your Boloforms account. Most recent: 'Q4 Budget Approval Form' (created Dec 15, 2024), 'Employee Onboarding Checklist' (Dec 12), 'Client Intake Survey' (Dec 8). Older documents include feedback forms from November and a vendor registration template from October. Each entry includes document ID, title, creation timestamp, and current status (published/draft).
This example shows the primary read capability. The MCP returns metadata only — you won't see form fields or submission data in this response. Requires a valid API key with read permissions. Useful for auditing what forms exist before diving into specific documents.
@Boloforms find any documents created in the last 7 days and tell me which ones have 'survey' in the title
Filtered your Boloforms documents by the past week and title keyword. Found 2 matches: 'Customer Satisfaction Survey' (created 3 days ago, status: published) and 'Post-Event Feedback Survey' (created 5 days ago, status: draft). No other documents from the last 7 days contain 'survey' in their titles. The account has 4 other recent documents that don't match this filter.
Demonstrates combining the list tool with AI reasoning to filter results. The MCP itself doesn't offer advanced search parameters — the AI parses the full document list and applies your criteria. Performance depends on total document count; accounts with hundreds of forms may see slower response times.
@Boloforms what's the oldest document in my account and when was it created?
The oldest document in your Boloforms account is 'Initial Contact Form', created on March 22, 2023. This predates your next-oldest document by 8 months. The form is currently published and appears to be a legacy intake template. If you're auditing old forms for cleanup, this would be a candidate to review for relevance.
Shows how the AI can analyze the document list to answer specific questions about your form inventory. The MCP provides raw creation timestamps; the AI handles date comparison and context. This is a read-only operation — you'd need Boloforms' web interface to archive or delete outdated documents.
Use-case deep-dives
Use Boloforms when you need a single-source document inventory
A 6-person remote ops team runs quarterly audits of onboarding docs spread across Google Drive, Notion, and a legacy wiki. They need a single API call to pull the canonical list of what's actually in Boloforms without opening the web app. The MCP works here because the team already stores signed offer letters and compliance forms in Boloforms, and the Get Documents List tool returns metadata fast enough for a Slack workflow to ping the audit owner. The trade-off: this MCP only lists documents—it doesn't fetch content or let you search inside PDFs. If your audit needs to verify what's in each doc, you'll still open the Boloforms UI. Use this MCP when your workflow is 'show me what exists' not 'show me what it says.'
Skip this MCP if you need to read or update documents
A 3-person customer success team tracks signed SOWs and change orders in Boloforms. They want an AI agent to check if a new client's paperwork is complete before the kickoff call. The MCP falls short here because Get Documents List only returns filenames and IDs—it can't tell you if a specific client's SOW is signed, expired, or missing fields. The team ends up opening Boloforms manually anyway. This MCP is a metadata play, not a workflow automation play. If your process depends on document status, approval chains, or content inside the file, the single-tool scope won't close the loop. Wait for Boloforms to ship a richer MCP or use their web API directly.
When one read-only tool is enough for reporting
A solo finance lead at a 12-person startup runs a Friday compliance check: are this week's vendor agreements uploaded to Boloforms? The MCP is the right call because the workflow is a yes-no gate, not a deep inspection. The finance lead connects the MCP to a Claude Project, asks 'list all documents uploaded this week,' and cross-references the output against a Notion database of expected contracts. The single Get Documents List tool handles the entire use case in under 10 seconds. The limitation: if a document is mislabeled or lives in a subfolder the API doesn't surface, the snapshot is incomplete. Use this MCP when your compliance bar is 'did it land' not 'is it correct.'
Frequently asked
What does the Boloforms MCP do in Switchy?
It connects your Boloforms account so AI agents can retrieve your document list on demand. When an agent needs to reference or check what forms exist in your account, it calls the Get Documents List tool. This is useful for workflows that need to verify form availability or pull metadata before linking to a specific document.
Do I need admin access to connect Boloforms?
You need an API key from your Boloforms account. Boloforms doesn't publish granular permission requirements for API keys, so assume you need account-level access to generate one. If your team restricts API key creation to admins, you'll need their help to set this up in Switchy.
Can the Boloforms MCP submit or edit forms?
No. It only retrieves the list of documents in your account. If you need to create, update, or submit form responses, you'll have to do that directly in Boloforms or via their full API outside of this MCP. This integration is read-only for document metadata.
Why use this instead of just opening Boloforms?
Use this when an AI agent needs to check which forms exist without you manually copying names or URLs. For example, a workflow that routes users to the right form based on their request can query the list programmatically. If you're just filling out a form yourself, open Boloforms directly.
Who on the team should connect Boloforms to Switchy?
Whoever owns the Boloforms account and can generate an API key. Since the MCP only lists documents, it won't expose sensitive form submissions, but the person connecting it should understand which forms are visible to the AI. One connection per workspace is usually enough.