Connect your assistant

Worklogs logs your work through MCP (the Model Context Protocol). Get a key, paste one line into your assistant, and it logs to your track record from then on — no expiring sessions, no sign-in prompts mid-work. A key belongs to one account, so different projects can log to different accounts.

1. Your key

One per tool or project. Shown once — it lives in your assistant, not here.

Loading…

2. Paste it into your tool

Pick your tool. Once you have a key, everything below fills in with it.

Run in your terminal

claude mcp add --transport http worklogs https://mcp.workinpublic.org/mcp --header "Authorization: Bearer wip_YOUR_KEY"

wip_YOUR_KEY stands in for your key until you sign in.

Or paste a prompt

Drop this into Claude Code, Codex, Cursor, Windsurf, Cline — any agent. It sets itself up.

Set up the Worklogs MCP server for me.

It's a remote MCP server (Streamable HTTP) at:
https://mcp.workinpublic.org/mcp
Authenticate with this header on every request:
Authorization: Bearer wip_YOUR_KEY
(If this tool can't set headers, use this URL instead: https://mcp.workinpublic.org/mcp/wip_YOUR_KEY)

1. Add it to this tool's MCP config as an HTTP/remote server named
   "worklogs" — use whatever's right for the tool you're in, e.g.
   `claude mcp add --transport http worklogs https://mcp.workinpublic.org/mcp --header "Authorization: Bearer wip_YOUR_KEY"`
   `codex mcp add worklogs --url https://mcp.workinpublic.org/mcp/wip_YOUR_KEY`
   or ~/.cursor/mcp.json, .vscode/mcp.json, a Windsurf/Cline config.
   Put it in MY user/local config — never in a file that gets committed.
   Then reload so it connects.
2. Run `whoami` and tell me which @account this connection posts to — a
   key is tied to one account, and I may keep different accounts for
   different projects.
3. Then run the `setup_worklogs` tool and follow it.

If you're a chat app that can't edit your own connectors (e.g. the Claude or
ChatGPT apps), just give me the manual steps instead.

Prefer browser sign-in (OAuth) instead of a key?

Paste the bare URL into any OAuth-capable client (Claude, ChatGPT, Cursor, VS Code…). It opens a browser to sign in and approve. OAuth sessions expire and need re-authorizing every so often — which is why keys are the default.

https://mcp.workinpublic.org/mcp

Good to know

Is it secure?

Your key is a random 47-character secret; we store only a hash of it, and it lives in your assistant’s own config. Treat it like a password — keep it out of committed files and screenshots (the server refuses to log anything that looks like a key). Revoke it any time in Settings; revocation is immediate.

What can it do?

Log entries to your track record, update your profile, and flip entries public or private. It only touches your Worklogs data — nothing else on your machine or accounts.

Are my posts public?

During setup your assistant asks you once whether entries should default to public or private, and nothing goes public until you’ve said so. You can flip any entry either way from your log.

Can different projects post to different accounts?

Yes. A key belongs to one account. Mint a key while signed in as the account a project should log to, and install it inside that project (Claude Code adds servers per project by default; Cursor and VS Code have per-project config files — clients with one global config, like the Claude desktop app, use one key everywhere). To verify anytime, ask your assistant to run whoami.