FreelanceOS

Server Details

Freelance business manager — clients, proposals, invoices, time tracking, scope, and follow-ups.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
Last Tested: 2026-09-06 10:33
Transport: Streamable HTTP
URL

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesApr 25, 2026

Changedinvoices.records.create8 fields changed

changedInput schema / properties / invoice_number / description

Previous value: -"Unique human-readable invoice identifier shown on the document, e.g. INV-001"New value: +"Optional. Human-readable invoice identifier (e.g. INV-001). Auto-generated as INV-NNNN based on existing invoice count when omitted."

removedInput schema / properties / subtotal / default
```
Removed value: -0
```

changedInput schema / properties / subtotal / description

Previous value: -"Sum of all line item amounts before tax is applied, in the invoice currency"New value: +"Optional. Sum of line item amounts before tax. Auto-computed from line_items when omitted."

removedInput schema / properties / tax_amount / default
```
Removed value: -0
```

changedInput schema / properties / tax_amount / description

Previous value: -"Calculated tax value derived from subtotal × tax_rate, in the invoice currency"New value: +"Optional. Tax value. Auto-computed as subtotal × tax_rate when omitted."

removedInput schema / properties / total / default
```
Removed value: -0
```

changedInput schema / properties / total / description

Previous value: -"Final amount due including subtotal and tax, in the invoice currency"New value: +"Optional. Final amount due. Auto-computed as subtotal + tax_amount when omitted."

changedInput schema / required

Previous value: -[
-  "client_id",
-  "project_id",
-  "invoice_number"
-]New value: +[
+  "client_id",
+  "project_id"
+]

Changedproposals.records.create2 fields changed

changedInput schema / properties / client_id / description

Previous value: -"UUID of the client this proposal is being created for"New value: +"UUID of the client this proposal is for. Optional — derived from the project when omitted."

changedInput schema / required

Previous value: -[
-  "client_id",
-  "project_id",
-  "title"
-]New value: +[
+  "project_id",
+  "title"
+]

37 tool updatesApr 13, 2026
- First observedclients.records.archive
- First observedclients.records.create
- First observedclients.records.get
- First observedclients.records.list
- First observedclients.records.update
- First observedfollowups.context.get
- First observedfollowups.messages.create
- First observedfollowups.messages.get
- First observedfollowups.messages.list
- First observedfollowups.messages.update
- First observedfollowups.sent.mark
- First observedinvoices.records.create
- First observedinvoices.records.get
- First observedinvoices.records.list
- First observedinvoices.records.update
- First observedprojects.records.archive
- First observedprojects.records.create
- First observedprojects.records.get
- First observedprojects.records.list
- First observedprojects.records.update
- First observedproposals.records.accept
- First observedproposals.records.create
- First observedproposals.records.get
- First observedproposals.records.list
- First observedproposals.records.update
- First observedscope.changes.list
- First observedscope.changes.log
- First observedscope.definition.check
- First observedscope.definition.create
- First observedscope.definition.get
- First observedscope.definition.update
- First observedtime.entries.aggregate
- First observedtime.entries.archive
- First observedtime.entries.create
- First observedtime.entries.get
- First observedtime.entries.list
- First observedtime.entries.update

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

EZ@WorkOAuth
io.github.eranfinish
Manage clients, projects, time, and invoices in EZ@Work — business management for freelancers.
Project Management CRM Finance
2
IMW InvoiceOAuth
management.independent
Invoicing, time tracking, and billing for freelancers and small firms, run in plain language.
Finance Payments & Billing
1
pleroOAuth
ai.plero
Operating system for creative companies: clients, projects, estimates, contracts, invoices, talent
CRM Project Management Payments & Billing
1
Timix.AI B
ai.timix
Time tracking, live project budgets, and billing exports for service firms.
Project Management Payments & Billing
1142

Related MCP Servers

FreelanceOS
Project Management Finance Developer Tools
Sohlin2
A
license
A
quality
C
maintenance
AI-powered freelance business manager for Claude Code. Proposals, invoices, time tracking, scope management, and follow-ups - 37 tools, 5 coaching skills.
Updated 4 months ago (2026-04-25 15:51 UTC)
37
22
MIT
Frihet MCP Server
ERP Systems Finance App Automation
Frihet-io
A
license
B
quality
A
maintenance
AI-native business management — invoices, expenses, clients, products, quotes, and webhooks. 31 tools for Claude, Cursor, Windsurf, and Cline.
Updated 2 days ago (2026-09-04 21:07 UTC)
100
329
9
MIT
ProposalCraft
Communication Workplace & Productivity
jabbawocky
A
license
A
quality
A
maintenance
An MCP server for freelancers and agencies that drafts client proposals and business emails — quotes, invoices, follow-ups, scope changes, and more — in your own voice, running locally with no API key or cloud.
Updated 2 months ago (2026-06-22 20:24 UTC)
100
2
MIT
businys
Project Management ERP Systems App Automation
hiatys
A
license
Not graded
quality
D
maintenance
Multi-practice operations platform for independent professionals — 221 MCP tools across 26 practices including clients, invoices, contracts, bookings, and more.
Updated 5 months ago (2026-04-07 16:00 UTC)
48
MIT

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity, as each is scoped to a specific resource (e.g., clients, invoices, projects) and action (e.g., create, get, list, update). The descriptions explicitly differentiate tools, such as 'clients.records.archive' for soft-deletion versus 'clients.records.update' for modifications, ensuring agents can accurately select the right tool.

Naming Consistency5/5

Tool names follow a highly consistent pattern throughout, using a structured 'resource.action' format (e.g., 'clients.records.create', 'invoices.records.list'). This uniform verb_noun style across all 37 tools makes the set predictable and easy for agents to navigate without confusion.

Tool Count3/5

With 37 tools, the count feels heavy for a freelance management system, potentially overwhelming for agents. While the tools cover comprehensive CRUD operations across multiple domains (clients, projects, invoices, etc.), a more streamlined set might improve usability without sacrificing functionality.

Completeness5/5

The tool surface is complete, offering full CRUD/lifecycle coverage for all core domains (clients, projects, invoices, proposals, scope, time entries, follow-ups). There are no obvious gaps; tools like 'proposals.records.accept' and 'scope.definition.check' handle edge cases, ensuring agents can manage the entire freelance workflow without dead ends.

Resources

Need Help?