Fergus MCP server

What the model can do

Fergus (job management for trades businesses): jobs with status, customer, site and active quote, a job's costs, charges, billed amounts and hours, quotes across all jobs, customer invoices with status and amounts, customers, sites, staff and tasks; can add notes, create, complete, reopen or delete tasks, add customers and enquiries, create, edit, finalise, hold, resume or archive jobs, schedule calendar events, and publish, accept, decline or void quotes.

Reads

• fergus_list_jobsJobs in Fergus: job number, type (Quote, Estimate, Charge Up), status, title, customer, site id, active quote, on hold and archived.
• fergus_get_jobOne Fergus job in full, with its financial summary: costs incurred, chargeable amount and amount billed (labour and materials)…
• fergus_list_quotesQuotes across all Fergus jobs: job, version, title, status (draft, published, accepted, declined, voided, superseded), whether sent, totals and dates.
• fergus_list_invoicesCustomer invoices in Fergus: number, job, customer id, status (unpaid, paid, draft, voided, disputed), subtotal, tax, amount paid…
• fergus_list_customersCustomers in Fergus by name: id, name, source, pricing tier and when added (contact details and addresses are never returned).
• fergus_list_sitesSites (job locations) in Fergus: id, name, city and whether archived; street addresses and contacts are never returned.
• fergus_list_staffStaff (users) in Fergus: id, name, role and status, for assigning tasks and calendar events.
• fergus_list_tasksTasks in Fergus: description, due date, job, status (pending or completed), assigned staff ids and when completed.

Acts, when you ask

These change something in Fergus. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• fergus_add_noteAdd a note to a Fergus job, customer, quote, customer invoice, site, task, enquiry or job phase…
• fergus_create_taskCreate a task in Fergus, optionally on a job, with a due date and assigned staff (from fergus_list_staff), who may be notified in Fergus.
• fergus_set_task_statusMark a Fergus task complete, or reopen a completed one.
• fergus_delete_taskDelete a Fergus task.
• fergus_create_customerAdd a customer to Fergus with a main contact (first name required) and, if given, their email and phone and a physical address.
• fergus_create_enquiryLog a new enquiry (a lead) in Fergus with the enquirer's name, what they want and where it came from, plus an email or a phone number…
• fergus_create_jobCreate a job in Fergus.
• fergus_update_draft_jobChange a draft Fergus job's title, description, customer, site or customer order number (Fergus only allows this on drafts)…
• fergus_finalise_jobFinalise a draft Fergus job, which gives it a job number, puts it in the job list…
• fergus_hold_jobPut a Fergus job on hold until a date, with a note saying why.
• fergus_resume_jobTake a Fergus job off hold.
• fergus_archive_jobArchive a Fergus job (drafts too).
• fergus_schedule_eventAdd an event to the Fergus calendar (start and end in 15-minute steps), assigned to the staff given (they see it in their schedule), or unassigned.
• fergus_publish_quotePublish a Fergus quote so it is final and ready for the customer (the spec does not say whether Fergus emails it; assume the customer may see it).
• fergus_accept_quoteAccept a Fergus quote, which commits the job to the quoted work.
• fergus_decline_quoteMark a Fergus quote as declined, with the reason and who declined it.
• fergus_void_quoteVoid a Fergus quote so it can no longer be accepted (the API offers no way to un-void it).

Connect it

First connect Fergus on Dashboard → Connections, then add Memtro to your client once. The Fergus tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Fergus connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which quotes are published and still waiting on the customer?
• › How many billable hours have gone on job 1187?
• › Which customer invoices are unpaid and past their due date?
• › Which tasks are overdue, and who are they assigned to?
• › Put job 1187 on hold until Monday because the parts are delayed.

Questions

Is this an official Fergus MCP server?

No. It is Memtro's MCP server with Memtro's Fergus connector behind it: the connector reads Fergus through its API with the credentials you connect on Dashboard → Connections, and Fergus publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Fergus?

Only when you ask, and only what it has been granted: add a note to a job, customer, quote, invoice, site, task or enquiry; create a task, optionally on a job and assigned to staff (they may be notified); mark a task complete, or reopen it; delete a task; add a customer with a main contact; log a new enquiry (lead); create a job (draft, active or a variation of another job); change a draft job's title, description, customer, site or order number; finalise a draft job so it gets a job number; put a job on hold until a date; resume a job that is on hold; archive a job (removes its schedule entries); schedule a calendar event for staff, optionally for a job; publish a quote (may reach the customer); accept a quote on the customer's behalf (can notify the customer); decline a quote; void a quote. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server