Folio and Kit MCP server

Create a new brand deal in the creator's deal tracker. Only call this when the user is clearly asking to create/add/log a deal. Never invent a brand name — if it's missing, ask the user for it in plain text instead of calling this tool.

Asks before running: Usually (host decides)

Move an existing deal to a new pipeline stage (e.g. mark it as won, negotiating, etc). The deal must already exist — never use this to create one.

Asks before running: Usually (host decides)

Archive an existing deal (hides it from the active pipeline; reversible, not a delete).

Asks before running: Usually (host decides)

Update one or more fields on an existing deal (contact details, platform, content type, value, deadlines, notes). Only include fields the user actually mentioned changing.

Asks before running: Usually (host decides)

List the creator's brand deals — optionally filtered by pipeline stage. Use when the user asks what deals they have, which brands they're working with, what's in their pipeline, or anything about deal status or deadlines.

Asks before running: No (read-only)

Get full details of a specific deal — stage, value, platforms, deadlines, contact, brief, notes, linked contracts and invoices. Use when the user asks about a specific brand deal.

Asks before running: No (read-only)

Add a deliverable (a piece of content the creator owes) to an existing deal's checklist, e.g. "1× Instagram Reel".

Asks before running: Usually (host decides)

Mark a deal deliverable as done (or not done). Use get_deal first to find the deliverableId.

Asks before running: Usually (host decides)

Assess whether a specific deal's rate is fair — returns a below/at/above-market verdict, a suggested fair range, reasoning, and a counter-offer line if the rate is low. Use whenever the user asks if a deal's rate is good, fair, too low, or how it compares to the market. Requires Creator or Pro plan — a Free-plan user gets an upgrade message instead of a verdict.

Asks before running: Usually (host decides)

Score 1–10 how well a deal's brand fits the creator's audience and niche, with reasons and red flags. Saves the score to the deal.

Asks before running: Usually (host decides)

Write a negotiation email to a deal's brand contact and save it as a draft on the deal (nothing is sent). Types: counter_offer, scope_creep_pushback, follow_up_after_silence, kill_fee_request, content_feedback_pushback, firm_follow_up. Returns a draftId for send_deal_email.

Asks before running: Usually (host decides)

Analyse the campaign brief saved on a deal: deliverables, scope-creep flags, questions to ask the brand and an estimated value. The deal must already have a brief (set one with update_deal's campaignBrief). Saves the analysis to the deal.

Asks before running: Usually (host decides)

Estimate realistic hours for each content deliverable (research, filming, editing, revisions, posting) and in total. If a deal is named, the estimate is saved to that deal.

Asks before running: Usually (host decides)

Check a sponsored post caption for UK ASA/CAP ad-disclosure compliance (is the paid-partnership label present, visible before the fold, not buried in hashtags). If it fails, returns the issues and a compliant rewrite. Saves the check to the deal.

Asks before running: Usually (host decides)

Find patterns across the creator's completed deals — payment speed, content performance, rate trends — plus a monthly revenue forecast. Needs at least 5 completed deals with a value. Saves the latest insights to the dashboard.

Asks before running: Usually (host decides)

No parameters.

Email a saved negotiation draft (draftId from draft_negotiation_email) to the deal's brand contact, from the creator. Optionally override the subject or body. This sends a real email to someone outside the creator's account — show the creator the final text first.

Asks before running: Yes — reaches someone outside your account

List the brands the creator has worked with, each with its known name variants (aliases) and deal count. Use to spot duplicates like "Gymshark" and "Gymshark Ltd" before merge_brands.

Asks before running: No (read-only)

No parameters.

Merge one brand into another when they are the same company: every deal moves to the kept brand, its names become aliases, and the merged brand is deleted. Cannot be undone. Get both brandIds from list_brands.

Asks before running: Yes — deletes or can't be undone

Draft a new contract for a brand deal. Only call this when the user clearly wants a contract drafted, with at minimum the deliverables, fee, payment terms, and usage rights they described — ask in plain text for anything essential that's missing rather than guessing.

Asks before running: Usually (host decides)

Email an existing draft contract to the brand for review and signature.

Asks before running: Yes — reaches someone outside your account

List the creator's drafted contracts — optionally filtered by status. Use when the user asks about contracts, which are signed, which are pending, etc.

Asks before running: No (read-only)

Get full details of a specific contract — deliverables, fee, payment terms, usage rights, exclusivity, status. Use when the user asks about a specific contract's terms. If the user gives a contract number (e.g. "CON-2026-7216"), use contractNumber — it resolves exactly, unlike brandName which can match several contracts for the same brand.

Asks before running: No (read-only)

Return a breakdown of the creator's contracts grouped by brand as a pie chart — how many contracts per brand. Use when the user asks to see their contracts broken down, distributed, or visualized by brand (e.g. "pie chart of contracts by brand", "which brands do I have the most contracts with").

Asks before running: No (read-only)

No parameters.

Archive a Folio-drafted contract: it is hidden from the active contracts list and stops counting toward the plan's contract limit. The record, its signatures and any linked invoice are kept (not a delete). Folio has no un-archive button today.

Asks before running: Usually (host decides)

Run the Contract Red Flag Scanner on a contract drafted in Folio: flags risky or missing terms (payment, usage rights, exclusivity, revisions, kill fee) with a suggestion for each, and saves the result on the contract. Not legal advice. For contracts a brand sent the creator, use get_imported_contract instead.

Asks before running: Usually (host decides)

List contracts brands sent the creator that were uploaded to Folio for a red-flag scan — brand, file name, overall risk and number of open flags. Contracts drafted in Folio are listed by list_contracts instead.

Asks before running: No (read-only)

No parameters.

Get the red-flag scan of an imported (brand-supplied) contract: overall risk, summary, each flag numbered with its risk and suggested fix, the extracted terms, and how it compares with the previous version if one was uploaded.

Asks before running: No (read-only)

Correct the brand name and/or brand contact email on an imported contract (the email is where send_pushback_email sends to). Only include the fields the user wants changed.

Asks before running: Usually (host decides)

Mark one red flag on an imported contract as dismissed (the creator accepts the risk, so it is left out of pushback emails) or restore it. Use get_imported_contract first to find the flagNumber.

Asks before running: Usually (host decides)

Permanently delete an imported contract: the uploaded file, its scan and flags. This cannot be undone. Frees an imported-contract slot.

Asks before running: Yes — deletes or can't be undone

Draft an email to the brand raising the open (not dismissed) red flags on an imported contract. Returns a subject and body for the creator to review; nothing is saved or sent. Send it with send_pushback_email once the creator is happy.

Asks before running: No (read-only)

Email the brand about an imported contract, from the creator (replies go to the creator's account email), and log it on the contract. Sends to the brand contact email stored on the imported contract. Only send text the creator has approved.

Asks before running: Yes — reaches someone outside your account

Create a draft invoice, typically for a deal that already exists. If the brand matches an existing deal, the client's name/email are filled in automatically. If there's no matching deal, a client email must be given.

Asks before running: Usually (host decides)

Email an existing invoice to the client.

Asks before running: Yes — reaches someone outside your account

List the creator's invoices — optionally filtered by status. Use when the user asks about invoices, what's outstanding, what's overdue, or who hasn't paid.

Asks before running: No (read-only)

Get full details of a specific invoice — amount, status, due date, line items, payment history. Use when the user asks about a specific invoice for a brand or client. If the user gives an invoice number (e.g. "INV-2026-0042"), use invoiceNumber — it resolves exactly, unlike brandName which can match several invoices for the same client.

Asks before running: No (read-only)

Return an aggregated financial snapshot: total earned (paid invoices), money outstanding (sent/overdue invoices), pipeline value (in-play deals), and completed deal count. Use when the user asks how much they've earned, what's outstanding, their pipeline value, or how they're tracking financially.

Asks before running: No (read-only)

No parameters.

Issue a draft invoice: assigns the next invoice number in the creator's series, sets the due date from their payment terms, and locks the invoice so it can no longer be edited (corrections then need a credit note). Does not email it — use send_invoice_to_client for that.

Asks before running: Usually (host decides)

Record a payment the creator has received against an issued invoice. Partial payments are fine; the invoice counts as paid once its payments add up to the total. Recording a second or later payment on the same invoice needs the Creator or Pro plan.

Asks before running: Usually (host decides)

Void an issued invoice that has no payments recorded, cancelling it permanently (its number stays used). If payments have been recorded, issue a credit note instead.

Asks before running: Yes — deletes or can't be undone

Issue a credit note that cancels an issued invoice in full (the correct way to fix an issued invoice, or one with payments recorded). Also creates a replacement draft invoice for the same client.

Asks before running: Yes — deletes or can't be undone

Archive an invoice: hides it from the active invoices list without changing its status or payment record.

Asks before running: Usually (host decides)

Delete a draft (not yet issued) invoice. Issued invoices can't be deleted — void them or issue a credit note.

Asks before running: Yes — deletes or can't be undone

Draft a payment-chaser email for an overdue invoice, in a tone matched to how late it is. Returns a subject and body for the creator to review — nothing is saved or sent.

Asks before running: No (read-only)

List the creator's saved rate cards — platform, content type, label, and min/max rate range. Use when the user asks what they charge, or whether they have a rate card set up for a platform. This is their own price list, not a market comparison — use get_rate_intelligence instead when the user asks whether a specific deal's rate is fair, good, or below/above market.

Asks before running: No (read-only)

Estimate what the creator should charge a brand for a piece of sponsored content, using Folio's rate calculator (the same one as the Rate Card screen). Returns a suggested range, a confidence level and a breakdown. If the creator has logged a matching past deal, the minimum is never below what they were actually paid. Nothing is saved — use create_rate_card to save a result.

Asks before running: No (read-only)

Run the rate calculator and save the result as a new entry on the creator's Rate Card (their saved price list, also used by their media kit and deal checks). Rates always come from the calculator — there is no way to type a price in directly.

Asks before running: Usually (host decides)

Change the inputs of a saved rate card and recalculate its range, as editing it on the Rate Card screen does. Only include the fields that change; everything else keeps the card's saved values. Changing the platform resets the content type to that platform's first option unless one is given.

Asks before running: Usually (host decides)

Permanently delete one saved rate card entry. This can't be undone.

Asks before running: Yes — deletes or can't be undone

List the deals the creator has logged as already closed on their Rate Card screen (their deal history). These set a floor under calculate_rate: it never suggests less than they were paid for the same platform and content type. Not the same as the deal tracker — use list_deals for active brand deals.

Asks before running: No (read-only)

No parameters.

Log a deal the creator has already closed to their deal history on the Rate Card screen, so the rate calculator never suggests less than they were actually paid. Use list_deals/create_deal for deals still in progress.

Asks before running: Usually (host decides)

Correct a deal in the creator's deal history. Only include the fields that change.

Asks before running: Usually (host decides)

Permanently remove a deal from the creator's deal history (it stops setting a floor under calculate_rate). This can't be undone.

Asks before running: Yes — deletes or can't be undone

Return the creator's Media Kit — their public shareable page (platforms, rates, brand collabs) — including the link to share with a brand. Use when the user asks for their media kit link, wants to share their media kit, or asks what's on it.

Asks before running: No (read-only)

No parameters.

Edit the text sections of the creator's media kit: name, bio, why-work-with-me, rate justification, rate list, brands worked with, and contact details. Only include fields that change. If the kit is published, the public page shows the change straight away.

Asks before running: Usually (host decides)

Choose which of the creator's platforms (from list_platforms) appear on their media kit. Pass null to show all of them, including any added later.

Asks before running: Usually (host decides)

Change the type, caption or platform tag of images/videos already in the media kit's content showcase (ids from get_media_kit). Only include fields that change. Uploading new items isn't available here — that's done in the Folio app.

Asks before running: Usually (host decides)

Remove an image or video from the media kit's content showcase and delete the uploaded file. This can't be undone.

Asks before running: Yes — deletes or can't be undone

Publish the creator's media kit (anyone with the link can see it: name, bio, audience stats, rates, brands and contact details) or hide it (the link shows a not-found page). Only call this when the user clearly asks to publish/unpublish, show/hide, or make their media kit live.

Asks before running: Yes — reaches someone outside your account

Draft the media kit's "About me", "Why work with me" and rate justification text from the creator's profile, platforms and rate cards. Nothing is saved — show the drafts to the user, and only if they want them, save with update_media_kit (aboutMe goes in bio).

Asks before running: No (read-only)

No parameters.

List the creator's social platforms with handle, follower count, engagement rate and profile link, as set in Folio's settings.

Asks before running: No (read-only)

No parameters.

Add a social platform to the creator's profile. Its follower and engagement figures show in the audience stats of their media kit, including the public page if it's published.

Asks before running: Usually (host decides)

Update a platform's handle, follower count, engagement rate or profile link. Only include fields that change; pass null to clear one. Changes show on the media kit, including the public page if it's published.

Asks before running: Usually (host decides)

Permanently remove a platform from the creator's profile; it also disappears from their media kit. This can't be undone.

Asks before running: Yes — deletes or can't be undone

Draft a cold outreach pitch email to a brand the creator wants to work with, and save it to their Pitch Generator history. Only call this when the user clearly asks for a pitch or outreach email to be written for a specific brand.

Asks before running: Usually (host decides)

List the outreach pitches saved in the creator's Pitch Generator history, newest first, 10 at a time — brand, date, subject and the full email body. Pass offset to fetch older pitches when hasMore is true.

Asks before running: No (read-only)

Permanently delete one saved pitch from the creator's Pitch Generator history. Use list_pitches first to find the pitchId. This cannot be undone.

Asks before running: Yes — deletes or can't be undone

Return the creator's Folio Value (private £ valuation) and Folio Index (0-100 public reliability score shown on their media kit) — current numbers, tier, confidence level, the banked/locked-in/in-play cashflow breakdown, what moved since last month, and the single biggest available opportunity to raise it. Use when the user asks about their Folio Value, Folio Index, Folio Score, their valuation, their reliability score, why it changed, or how to improve it.

Asks before running: No (read-only)

No parameters.

Return the creator's Folio profile — display name, legal name and address used on contracts, email, VAT number, bio, niches, audience location, current plan, and their platforms with follower counts and engagement. Use when the user asks about their profile, account details or which platforms Folio has on file.

Asks before running: No (read-only)

No parameters.

Change fields on the creator's Folio profile (Settings → Profile): display name, bio, and the legal name, address and VAT number used on contracts. Only include fields the user explicitly asked to change. Invoice details live in the business profile (update_business_profile) instead.

Asks before running: Usually (host decides)

Return the business details printed on the creator's invoices — entity type, legal and trading name, company number, business address, VAT registration, payment terms and footer note — plus whether a payment method is on file and what is still missing before invoices can be sent. Bank details are never returned.

Asks before running: No (read-only)

No parameters.

Change the business details printed on the creator's future invoices (already-issued invoices keep the old details). Only include fields the user explicitly asked to change; everything else is kept, and an empty string clears an optional field. Bank details and payment links can only be changed in the Folio app.

Asks before running: Usually (host decides)