A
licenseNot graded
qualityB
maintenanceEnables freelancers and small agencies to manage client operations through voice, with daily briefings, call preparation, invoice tracking, stale-client alerts, and persistent memory across sessions.
MIT
Mycel
by com.mycelhq
Server Details
Run your service firm from your AI: client work to review, clients, deliverables, invoices.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 23.8% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
B3.3/5.0
Scored across 24 tools
Disambiguation4/5
Most tools target distinct resources and actions, with clear separation between clients, deliverables, invoices, approvals, recurring work, and firm files. There is some potential overlap between approve_and_send and decide_approval, and between what_needs_me and the specific list tools, but the descriptions make the intended boundaries reasonably clear.
Naming Consistency4/5
The set predominantly uses snake_case verb_noun names such as list_clients, get_client, send_invoice, and edit_firm_file. A few deviations like firm_files, firm_history, what_needs_me, and what_the_firm_knows are readable but less consistent with the dominant pattern.
Tool Count3/5
The 24 tools cover a broad firm-operations domain, so many are justified, but the count sits in the heavy 16–25 range and increases selection burden. It is borderline rather than clearly well-scoped.
Completeness4/5
Core workflows are well covered: client management, deliverables, approvals, invoicing, recurring work, firm knowledge, and file history. Some lifecycle operations are not explicit, such as invoice creation/editing or client update/delete, but call_mycel provides a workaround for uncovered API routes.
Available Tools
24 toolsadd_clientBInspect
Add a client. Adding one can open their engagement if the firm has a live service; nothing is sent to them without the owner's OK.
Inputs: name (required), email.
approve_and_sendCInspect
The owner's OK: send a deliverable that is waiting for review to its client.
Inputs: deliverable_id (required).
call_mycelBInspect
Any Mycel API route not covered above. method GET or POST (or PATCH/DELETE), path under /v1/, optional JSON body. See https://docs.mycelai.dev for the routes.
Inputs: path (required), method (required), body.
change_timingAInspect
Change when a recurring job runs, in plain words: 'push it to the 15th', 'skip October', 'quarterly from now on'. Unclear requests are refused with a question.
Inputs: job_id (required), instruction (required).
chase_invoiceAInspect
Chase an overdue invoice now, politely, from the firm's inbox.
Inputs: invoice_id (required).
decide_approvalCInspect
Approve or reject one pending approval.
Inputs: decision (required), approval_id (required).
decide_firm_changeAInspect
Merge, dismiss, or undo a change to how the firm works that its agents proposed (see firm_history and what_needs_me). Undo reverses a merged change and records it.
Inputs: index (required), decision (required), consolidation_id (required).
edit_firm_fileAInspect
Edit a file the owner may edit (gtm/icp.md, gtm/playbook.md's 'Your angles' and 'Your opener', practice/*.md, a service's SKILL.md, a client's card.md). The change is a commit; every later run reads it.
Inputs: body (required), path (required), message.
firm_filesAInspect
List the firm's repository: a folder (path, default the root) or a search across it (q). The repo is how the firm works: practice/, rules/, clients//, gtm/ (icp.md, playbook.md, pipeline.md, deals.md), analytics/, site/.
Inputs: q, path.
firm_historyBInspect
The repository's history: every commit to how the firm works, the proposed versions waiting, merged, declined or switched off.
Inputs: no named parameters.
get_clientBInspect
What the firm knows about one client: their work, history, rules learned from corrections, and context.
Inputs: client_id (required).
get_deliverableBInspect
One deliverable: its versions, files, what was checked, and its timeline.
Inputs: deliverable_id (required).
list_approvalsBInspect
Actions waiting for the owner's approval (emails, changes in client systems, spend).
Inputs: no named parameters.
list_client_requestsAInspect
What the firm is waiting on from clients (documents, answers, decisions), and how long each has been open.
Inputs: no named parameters.
list_clientsBInspect
Every client of the firm, with their ids.
Inputs: no named parameters.
list_deliverablesBInspect
Client work produced by Mycel. Filter by status: in_review (waiting for the owner), with_client, accepted, drafting.
Inputs: status, client_id.
list_invoicesBInspect
The firm's invoices, with status (draft, sent, overdue, paid) and amounts.
Inputs: status.
list_recurring_workAInspect
The recurring jobs per client (what runs, for whom, and when it is next due).
Inputs: no named parameters.
read_firm_fileAInspect
Read one file in the firm's repository, e.g. gtm/playbook.md (which angle earns replies per buying moment) or rules/house.md.
Inputs: path (required).
send_back_for_changesAInspect
Send a deliverable back to be redone, with what is wrong. The note is kept as a correction the firm learns from.
Inputs: note (required), deliverable_id (required).
send_invoiceBInspect
Send a drafted invoice to its client (moves it to sent and emails it).
Inputs: invoice_id (required).
start_workCInspect
Start a piece of work on a client engagement (a case) — e.g. this month's report.
Inputs: case_id (required), task_type (required), instructions.
what_needs_meAInspect
The owner's ranked to-do list right now: work waiting for sign-off, clients who have not answered, overdue invoices, and why each matters.
Inputs: no named parameters.
what_the_firm_knowsBInspect
The firm's brain: what it sells, to whom, its clients and kinds of work, learned from its own mail and files.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Quotes, contracts and invoices per client. Your AI drafts, sends and follows up.
1Run a service business from your AI agent: CRM, leads, scheduling, invoicing, jobs and more.
AI account manager and client portal: requests, approvals, clients, files, and handing work over.
AI employees that run your CRM, invoicing, email, documents, dashboards and agents
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to serve as the only interface for consultant and small-agency billing, recording clients, billable work, expenses and payments, and drafting and issuing invoices. It enforces billing rules server-side, numbering invoices, calculating totals, requiring exact-total approval before issue, and never rewriting an issued invoice.12 npm1MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI assistants to a business workspace so they can read and manage clients, leads, projects, tasks, tickets, invoices, proposals, and related records, including sending client emails.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables agencies to generate deterministic, ranked operational briefs by combining delivery status, financial performance, and recent client communication from ClickUp, QuickBooks, and Gmail.-
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.