> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usefini.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Claude Plugin
> Query your Fini agents, conversations, knowledge, and rules from Claude, and draft changes for your review without opening the dashboard.
The Fini plugin links Claude to your Fini workspace. Once it's installed, you can ask Claude about your agents, [conversations](/en/testing/inbox), [knowledge](/en/knowledge/overview), [sources](/en/knowledge/sources), [prompts](/en/configuration/prompts), [rules](/en/automations/rulebook), and [tags](/en/configuration/tags), and have it draft changes for you to approve, without opening the Fini dashboard for every question.
The plugin carries two things. The **connector** gives Claude the Fini tools over MCP. The **skills** teach Claude which tool to reach for in each Fini workflow. Both arrive in one install — there's no separate download and no OAuth details to paste.
The plugin reads freely and proposes changes; it does not publish on its own. When you ask Claude to draft knowledge, it creates a draft that lands in [Review](/en/knowledge/review) for you to approve, the same path every other knowledge input takes. Prompt, rule, and tag changes are write actions that wait for your approval before anything is applied.
## Before you start
* A paid Claude plan. Plugins are available on Pro, Max, Team, and Enterprise.
* A Fini account with access to the workspace you want Claude to reach. You sign in with it during setup, and that account decides which workspace the plugin sees.
* A few minutes in Claude's settings.
* Optional: a handful of real customer questions you want to test.
On Team and Enterprise plans your admin can restrict which marketplaces you're allowed to add. If the Fini marketplace won't add, that's the first thing to check.
## Install the plugin
Plugins sits under *Customize* in the settings sidebar, next to *Skills* and *Connectors*.
The *Add* menu also offers *Upload plugin* and *Create with Claude*. You want *Add marketplace*.
The other option, *Browse Anthropic sources*, lists marketplaces Anthropic curates. Fini isn't one of them.
`https://github.com/ask-fini/fini-skills`
*Sync automatically* keeps plugins up to date when the repository changes on GitHub, so new and updated Fini skills reach you without a reinstall.
Fini appears under the *fini-skills* marketplace in the *Personal* tab. Its page lists what you're about to install: seven skills and one connector.
Installing the plugin loads its skills but leaves its connector unconnected. Open the installed plugin, switch to *Connectors*, and click *Install* on the `fini` row.
Claude opens *Add custom connector* with the name and MCP server URL already filled in. Leave *OAuth Client ID* and *OAuth Client Secret* blank — the plugin supplies them — and click *Add*. Sign in to Fini and approve access.
If Claude shows a banner reading *Auto-sync requires the Claude GitHub App to have access to this repository*, follow its *Grant access* link. Without it, auto-sync won't run and you'll need to sync the marketplace by hand to pick up skill updates.
## Connect the connector
The skills and the connector install separately, and the plugin works only when both are in place. A plugin with skills but no connector is the most common half-finished setup: Claude sounds like it knows Fini, describes the right workflow, and then has no tools to call.
Claude opens the *Add custom connector* dialog with `fini` and `https://mcp.usefini.com/mcp` already filled in. The *OAuth Client ID* and *OAuth Client Secret* fields under *Advanced settings* are optional and stay blank.
Installed, the plugin brings seven skills: `fini-api-coordinator`, `fini-api-agent-configuration`, `fini-api-knowledge`, `fini-api-sources`, `fini-api-conversations`, `fini-api-generate-answer`, and `fini-api-slack-onboarding`. Each maps to a Fini workflow: routing a request to the right workflow, configuring an agent, managing knowledge and sources, pulling conversations, generating answers, and onboarding a [Slack](/en/deploy/slack) deployment. Invoke one by typing `/` in chat, or let Claude pick for itself. The tools work without the skills, but Claude won't know the Fini-specific order of operations.
## If you set up Fini in Claude before
Earlier setups added Fini as a custom connector, with a Remote MCP server URL and an *OAuth Client ID* you typed in yourself. Remove it before you install the plugin. The plugin carries its own connector, and leaving the old one in place means Claude sees two sets of Fini tools and picks between them at random — and two entries named `fini` in your connector list.
Open *Settings → Connectors*, find the older Fini entry, and click *Disconnect*. If it still shows after that, remove it from the *•••* menu. You don't need the skills `.zip` either — the plugin replaces it.
## Set tool permissions
The Fini connector ships two groups of tools: read-only tools that inspect your workspace, and write/delete tools that can change it. Set the permissions so Claude can look around freely but has to ask before it changes anything.
Open *Settings → Connectors* and click `fini` to reach its *Tool permissions* panel.
Set *Read-only tools* to *Always allow* and keep *Write/delete tools* on *Needs approval*. With that split, Claude can read, inspect, and summarize without interruption, and every action that publishes, updates, moves, or deletes surfaces an approval prompt first. Review the exact plan before you approve it.
## First thing to try
Ask: *"Can you list my Fini agents?"* Claude uses the plugin and returns your agents by name, along with their IDs and creation dates. From there, follow up on one of them. Asking *"Show the knowledge folders for this agent"* confirms the connection works end to end.
## What you can do day to day
Check what's configured without digging through the dashboard. *"What agents do we have?"* · *"What knowledge folders are attached to this bot?"* · *"List our rulebooks."*
Point Claude at recent activity to find what's going wrong. *"Show recent escalations and tell me what happened."* · *"Find conversations where the agent probably needs better knowledge."*
Draft changes without shipping them. *"Draft a knowledge article from this doc, but don't publish it."* · *"Suggest prompt or rule changes, but ask before applying anything."*
Sanity-check answers before customers see them. *"Run these five questions against the bot and tell me whether the answers look right."*
Drafted knowledge lands in [Review](/en/knowledge/review), and proposed prompt or rule edits wait behind an approval prompt, so you don't have to opt into safety on each request. For a structured way to run questions against a bot before launch, see the [Test Suite](/en/testing/test-suite).
## Stay safe
Approve publish, update, move, and delete actions only when you recognize the agent, article, folder, rule, or tag the action names. If you don't recognize the ID an action references, stop and check before approving.
A few habits keep the plugin low-risk:
* Don't paste API keys into chats. The plugin doesn't need one.
* Start knowledge changes as drafts and approve them in [Review](/en/knowledge/review).
* Test live behavior changes (prompts, rules) against a few real customer questions before they go out.
* Keep write/delete tools on *Needs approval* so nothing changes without your sign-off.
## Why the plugin isn't working
Check the URL was pasted exactly, with no trailing characters: `https://github.com/ask-fini/fini-skills`. If it still fails and you're on a Team or Enterprise plan, your admin may have restricted which marketplaces you can add — ask them to allow this one.
Look under the *Personal* tab, in the *fini-skills* marketplace. If it's missing, sync the marketplace by hand — auto-sync stays idle until the Claude GitHub App has access to the repository.
The plugin is installed but its connector isn't. Open the plugin, switch to *Connectors*, click *Install* on the `fini` row, and finish the Fini sign-in. Skills load without the connector, so Claude can describe the right Fini workflow while having nothing to call.
Usually a pop-up blocker. Allow pop-ups for Claude and retry. If the window opens but never returns, close it and start the connector install again, completing sign-in in one pass.
The session has expired, or the Fini account you signed in with doesn't have access to the workspace you're asking about. Disconnect the connector, reconnect, and sign in with an account that has access. If it persists, send the Fini team the exact error message Claude shows — it names the failing tool and the reason.
The older custom connector is still installed alongside the plugin. Remove it in *Settings → Connectors* — disconnect, then delete it from the *•••* menu if it lingers.
Expected. Write/delete tools are on *Needs approval*, so changes surface a prompt before they run. Approve the action to continue. If you never see a prompt, check that the write tools weren't set to *Never allow*.
Open the plugin and confirm its skills are listed under the *Skills* tab. If they are, click *Update* on the plugin — an older copy of a skill can send Claude down the wrong sequence.
## Related topics
- [Coding agents](/en/api-reference/coding-agents.md)
- [API overview](/en/api-reference/overview.md)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.