
Tallied
com.withtalliedPublished by withtallied.comOfficial publisherv0.1.0Updated Oct 24, 2026
Log hours and invoice clients from your AI chat. Time tracking and invoicing for freelancers.
Overview
Tallied is a remote time-tracking and invoicing server that lets an AI assistant log work hours, review unbilled time and draft client invoices.
- What you can do
- Log time entries by telling the assistant what you worked on, with duration parsing and rates applied per workspace settings and defaults (R2, R10). Review unbilled work and draft invoices for clients, with invoice PDFs generated in-process (R2, R10). Run catch-up and month-close style workflows, plus weekly reports and client invoicing, exposed as bundled skills and MCP prompts (R10). Handle account settings, CSV import from Toggl, Harvest or Clockify, and billing through a small web app rather than chat (R3, R10).
- When to use it
- Useful for freelancers and small service businesses that want to record billable hours and turn them into invoices conversationally, without switching to a separate time-tracking app. Best when the assistant is the main interface and you only occasionally need the web app for settings, imports or billing.
- Requirements
- A remote MCP endpoint over Streamable HTTP with OAuth 2.1 authentication, which is required. Sign-in is by Google OIDC or an emailed magic link, with no passwords; a first-time user creates a workspace on the consent screen. Self-hosting needs Node.js, Postgres, and optionally SMTP or Resend for email and Stripe for billing and payment links.
Installation
In SourceWeft
- Open Tallied in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.withtallied%2Ftallied/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"tallied": {
"type": "http",
"url": "https://withtallied.com/mcp"
}
}
}README
Tallied
Tallied is a time-tracking and invoicing MCP server. It's connector-first: Claude and ChatGPT (or any MCP client) are the primary UI — you tell an assistant what you worked on and it logs the hours, ask what's unbilled and it drafts the invoice. A minimal web app handles the things chat is bad at: account settings, CSV import, and billing. Clients pay invoices through a Stripe payment link on a public, tokenized page.
Quick start
Then connect with the MCP Inspector:
Choose Streamable HTTP, point it at http://localhost:3000/mcp, and connect. The inspector will hit the OAuth flow and open the login page in your browser. Without SMTP_URL or RESEND_API_KEY set, magic-link sign-in doesn't send an email — the link is printed to the server log and also shown directly on the "check your email" page, so local dev never needs a real mailbox.
Project layout
Environment variables
See .env.example for the same list with inline comments.
OAuth notes
- The
@modelcontextprotocol/sdkrouter (mcpAuthRouter) provides the protocol surface: dynamic client registration, PKCE (S256), a form-encoded token endpoint, and RFC 8414 + RFC 9728 discovery metadata.src/http/app.tsmounts it atAUTH_ISSUER_URLand wires it toTallyOAuthProvider(src/auth/provider.ts), which persists clients, codes, and tokens in Postgres. - Identity is Google OIDC or an emailed magic link — no passwords. See
src/auth/routes.ts. - The OAuth consent screen is signup. A user with no workspace yet gets an onboarding card (business name, default rate, currency, timezone) inline on the consent page; clicking Allow creates the workspace and completes the authorization in one step.
- Tokens are opaque and hashed at rest (never stored in plain text). Access tokens last 1 hour; refresh tokens last 30 days and rotate on every use, with reuse detection (a reused, already-rotated refresh token revokes the whole token family).
- To swap in a hosted identity/OAuth provider (Clerk, WorkOS, Stytch) instead of
TallyOAuthProvider, replace it with the SDK'sProxyOAuthServerProvider, which delegates the same protocol surface to an upstream authorization server.
Deployment
Tallied runs on any host that gives you a stable HTTPS origin — Fly.io, Railway, Render, or similar.
- Set
BASE_URLto your public origin. SetMCP_URL,AUTH_ISSUER_URL, and/orAPP_URLonly if you're splitting those surfaces across subdomains. npm run build(runsbuild:appthentsc), thennpm start.- Point your Postgres at
DATABASE_URLand runnpm run db:migrate. - If using Stripe, register a webhook endpoint at
${BASE_URL}/webhooks/stripesubscribed tocheckout.session.completed,payment_intent.succeeded,customer.subscription.updated, andcustomer.subscription.deleted. - If using Google sign-in, add
${BASE_URL}/oauth/google/callbackas an authorized redirect URI in the Google OAuth client.
Testing
npm test— unit tests (vitest).test/golden-prompts.json— a hand-curated set of prompts and expected tool-call behavior. It's run manually, in both Claude and ChatGPT, before any change to tool names, descriptions, or input schemas — those are effectively a public API for the model and regressions there don't show up in unit tests.
Submission checklists
Before submitting to a connector directory, see docs/listing.md for store-listing copy and screenshots, and the product spec's submission checklist for the full requirements. Note that Claude's connector directory requires the submitting organization to be on a Team (or Enterprise) plan.
Source: README.md at commit 8ecfec8
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.