What your AI assistant can do via MCP, and troubleshooting

What AI tools connected to fynk can read and change, what still needs fynk itself, and how to fix common problems.

Written By Sebastian

Last updated About 1 hour ago

Your AI tool works with the information stored in fynk and with your fynk permissions. This article shows what it can do, where you still need fynk, and what to check when something doesn't work.

Available on Essential, Business and Pro · Requires MCP

What your assistant can do

Area	Your assistant can
Find and report	Search and filter documents by stage, tags, teams, parties, document type and metadata, including archived documents. Read summaries, dates, values and signing status.
Create documents	Create documents from templates or from scratch, add parties and signatories, fill in fields, upload PDFs, and move documents to review, signing or done.
Check blockers	Tell you what's blocking a document from moving on, for example a missing signatory or signature block.
Build templates	Create templates with parties, fields and signature blocks, and check existing templates.
Manage settings	Create and edit metadata fields, document types, tags and teams, if your role allows it.

What still needs fynk

Task	What to do instead
Questions about the exact wording of a clause	Use the AI Assistant in fynk. Via MCP, your assistant sees metadata and summaries, not the full contract text.
Sending an uploaded PDF for signature	Place the signature blocks in fynk, then ask your assistant to start signing. Signature blocks can be added to templates via MCP, but not to uploaded PDFs.
Running a playbook	Run it in fynk. Your assistant can list playbooks, but not run them.
Approving a checkpoint	Approve it in fynk. Your assistant can tell you who still needs to approve.
Tasks, reminders and comments	Manage them in fynk. Your assistant can't read or create them yet.
Changing a document's owner	Change it in fynk. See Invite, manage and remove users.

Troubleshooting

My assistant doesn't use fynk

Check that the fynk connection is turned on in your AI tool, for example under Connectors in Claude.
Mention fynk in your prompt: "Using fynk, …".
If it still doesn't work, disconnect and connect again. See Connect AI tools with MCP.

Ask an Owner to check that Enable MCP for this organization is turned on in Account settings → MCP.
An admin may have disconnected your tool. Connect it again.
Adding a connector may need admin rights in the AI tool itself.

A document is missing from the results

Your assistant only sees documents you can see in fynk. Check your access in fynk.
Archived documents are left out unless you ask for them: add "including archived documents".
Use the names your account uses for tags, document types and teams.
For long lists, ask your assistant to go through all pages of results.

A date or value is empty or wrong

Your assistant uses the values stored in fynk. If the AI analysis hasn't filled a field or the value wasn't confirmed, the field stays empty. See AI analysis didn't find a value.

I can't upload a PDF from Claude

Turn on network access in Claude's capability settings, then try again.

My assistant can't start signing

Ask: What's blocking [document] from signing? Your assistant lists everything that's missing, for example signatories, signature blocks or mandatory fields.

"You don't have permission"

Your assistant has the same rights as you in fynk. Ask an Owner or Admin for the role you need.

Was this helpful?

Still need help? Ask the team