Get Started

Claude (claude.ai) — remote MCP via Connectors

claude.ai supports remote MCP servers through the Connectors feature on every paid plan (Pro / Max / Team / Enterprise).

1. Open Connectors

In claude.ai, go to Settings → Connectors → Add custom connector.

2. Add Workjournal

• Name: Workjournal
• Remote MCP server URL: https://mcp.workjournal.pro

3. Authorize

Claude opens the Workjournal login page in a new tab. Sign in and click Approve — you’re redirected back and the connector is live.

4. Use it

Toggle Workjournal on under the + menu in any conversation, or ask “log this decision to my work journal.” Claude calls the Workjournal tools directly.

Claude Desktop — remote MCP via Connectors

Claude Desktop supports the same Connectors feature as claude.ai. Any connector you add on the web is available on desktop and vice versa.

1. Open Connectors

Settings → Connectors → Add custom connector.

2. Add Workjournal

• Name: Workjournal
• Remote MCP server URL: https://mcp.workjournal.pro

3. Authorize

Claude opens the Workjournal login page in your default browser. Sign in and click Approve — you’re redirected back and the connector is live.

4. Use it

Toggle Workjournal on under the + menu in any conversation, or ask “log this decision to my work journal.” Claude calls the Workjournal tools directly.

If you’d rather run the server locally over stdio, switch the tab above to Local MCP.

Claude Desktop — local MCP server

Claude Desktop runs MCP servers locally over stdio. Install the Workjournal MCP package and add one entry to the Claude Desktop config.

1. Open the Claude Desktop config file

OS	Path
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json
Linux	~/.config/Claude/claude_desktop_config.json

2. Add the Workjournal server

{
  "mcpServers": {
    "workjournal": {
      "command": "npx",
      "args": ["-y", "@workjournal/mcp-server"]
    }
  }
}

3. Restart Claude Desktop

Claude will start the server automatically. The first time you invoke a Workjournal tool it will ask you to authorize — a browser window opens, you sign in, paste the returned code back into Claude, and you’re set.

Claude Code — plugin

The Workjournal plugin bundles the skill, CLI commands, and configuration as one drop-in install.

Install

# In your Claude Code project
claude plugins add workjournal-pro/workjournal

Authenticate

/workjournal login

The agent opens a browser window, you approve, and it pastes the code back automatically. Credentials are stored at ~/.config/workjournal/credentials.json (or the platform equivalent — see /docs/cli-tool-auth-workflow).

Start using

/workjournal              # write a new entry
/workjournal last 3       # review recent entries
/workjournal check        # find relevant context
/workjournal search auth  # full-text search

Claude Code — Open Agent Skill

The Workjournal skill works with any agent that supports the Open Agent Skills format — Claude Code, Cursor, Copilot, Gemini CLI, and more.

Install from marketplace

If your agent has a skill marketplace, search for Workjournal and install.

Install from GitHub

curl -sL https://github.com/workjournal-pro/skill/releases/latest/download/skill.zip \
  -o /tmp/workjournal-skill.zip
unzip /tmp/workjournal-skill.zip -d skills/workjournal

Authenticate

/workjournal login

The skill prints a URL — open it in any browser, click Approve, copy the 8-character code, and paste it back. Works in local terminals, SSH, dev containers, and CI.

Start journaling

/workjournal              # write a new entry
/workjournal last 3       # view recent entries
/workjournal search <q>   # search past entries
/workjournal check        # find relevant context

See the commands reference for the full list.

Claude Code — CLI

If you don’t want the skill layer, the underlying CLI works directly. Claude Code can shell out to workjournal like any other command.

Install

npm install -g @workjournal/cli

Authenticate

workjournal auth login

Opens a browser flow, prints a code, and stores credentials at ~/.config/workjournal/credentials.json (or the platform equivalent — see /docs/cli-tool-auth-workflow).

Use

workjournal workspaces list
workjournal journals list <workspaceSlug>
workjournal journals select <workspaceSlug> <journalSlug>
workjournal entries last <workspaceSlug> <journalSlug> 3
workjournal entries write <workspaceSlug> <journalSlug> -t "Title" -s "Summary" -b "Details"

Full CLI reference: /docs/commands.

ChatGPT (web) — remote MCP via Connectors

ChatGPT supports remote MCP servers through the Connectors feature. The Workjournal MCP implements OpenAI’s connector spec (search + fetch), so Developer Mode is not required — it works in standard ChatGPT.

1. Open Connectors

In ChatGPT, go to Settings → Connectors → Add a connector.

2. Add Workjournal

• Name: Workjournal
• MCP server URL: https://mcp.workjournal.pro

3. Authorize

ChatGPT redirects to the Workjournal login page. Sign in and click Approve. You’ll be sent back automatically and the connector will appear in your connector list.

4. Use it

Mention @workjournal in any chat, or ask “log this decision to my work journal.” ChatGPT will search your journals with search and pull entry bodies with fetch; the richer toolset (creating entries, managing journals) is available when Developer Mode is enabled.

ChatGPT (web) — Custom GPT

The Workjournal Custom GPT is the no-toggle path for ChatGPT users. Anyone can open it from the GPT Store, sign in once, and write entries from chat.

1. Open the Workjournal GPT

Visit the Workjournal GPT (link added once published) or search “Workjournal” in Explore GPTs inside ChatGPT.

2. Sign in

Click Start chat → the GPT asks to connect to your Workjournal account. Approve the OAuth screen at app.workjournal.pro/authorize.

3. Use it

Tell the GPT what you want to log: “log that I shipped the v2 cron parser today”. The GPT calls createEntry against your default journal. Ask “what did I work on last week?” to search past entries.

The Custom GPT exposes a curated 15-operation surface (entries, journals, tags, export). For the full ~35-tool catalog — including prompts and contributor management — use the Remote MCP tab.

ChatGPT desktop — remote MCP via Connectors

The ChatGPT desktop app uses the same Connectors feature as the web app. Any connector you add on the web is available on desktop and vice versa. Developer Mode is not required — Workjournal implements OpenAI’s search + fetch connector spec.

1. Open Connectors

Settings → Connectors → Add a connector.

2. Add Workjournal

• Name: Workjournal
• MCP server URL: https://mcp.workjournal.pro

3. Authorize

ChatGPT opens the Workjournal login page in your default browser. Sign in and click Approve — you’re redirected back and the connector is live.

4. Use it

Mention @workjournal in any chat, or ask “log this decision to my work journal.” Standard mode covers retrieval (search, fetch); enable Developer Mode if you want ChatGPT to also create or update entries directly.

ChatGPT (mobile) — remote MCP

The ChatGPT mobile app uses the same Connector list as ChatGPT web and desktop. Set up Workjournal on web first — the mobile app can’t run the OAuth flow itself, but it will pick up an existing connector and let you call its tools.

1. Set up on web or desktop first

Follow the ChatGPT (web) or ChatGPT (desktop) steps to add Workjournal once. Developer Mode is not required — the Workjournal MCP server implements OpenAI’s connector spec (search + fetch tools), so it works in standard ChatGPT.

2. Use it from mobile

Open ChatGPT on your phone. The Workjournal connector shows up under your enabled connectors automatically — no extra mobile config.

In any conversation, mention @workjournal or ask “log this decision to my work journal.” ChatGPT calls the tools through the same hosted MCP endpoint.

Note: signing in to the connector for the first time from the mobile app isn’t supported. If the connector is missing on mobile, finish step 1 on web or desktop and re-open the app.

Perplexity (web) — remote MCP

Perplexity supports remote MCP servers in Spaces and directly in Pro settings.

1. Open MCP settings

Perplexity → Settings → Connectors (or, inside a Space, Connectors).

2. Add Workjournal

• Name: Workjournal
• MCP server URL: https://mcp.workjournal.pro

3. Authorize

Perplexity opens the Workjournal login page. Sign in and click Approve. You’re returned to Perplexity with the connector active.

4. Use it

In any Perplexity thread: “Use workjournal to log today’s decisions” — or just ask a question that implies journal access and Perplexity will call the tools.

Perplexity desktop — remote MCP

The Perplexity desktop app shares its connector list with the web app. Configure once and it’s available everywhere.

1. Open Connectors

Settings → Connectors → Add a connector.

2. Add Workjournal

• Name: Workjournal
• MCP server URL: https://mcp.workjournal.pro

3. Authorize

Perplexity opens the Workjournal login flow in your default browser. Sign in and click Approve.

4. Use it

Ask Perplexity to log, search, or summarize journal entries — it’ll call the tools as needed.

Grok (web) — remote MCP

Grok supports remote MCP servers via its Connectors integration.

1. Open Connectors

In Grok, open Settings → Connectors → Add a connector.

2. Add Workjournal

• Name: Workjournal
• MCP server URL: https://mcp.workjournal.pro

3. Authorize

Grok opens the Workjournal login page. Sign in and click Approve. You’re returned to Grok with the connector active.

4. Use it

In any Grok conversation, ask “log this decision to my work journal” — or just mention something that implies journal access and Grok will call the tools.

Grok (mobile) — remote MCP

The standalone Grok mobile app (iOS / Android) supports remote MCP connectors.

Workjournal works in the standalone Grok app — not in the Grok chat embedded in X.com, which doesn’t expose connectors today.

1. Open Connectors

In the Grok app, open Settings → Connectors → Add a connector.

2. Add Workjournal

• Name: Workjournal
• MCP server URL: https://mcp.workjournal.pro

3. Authorize

Grok opens the Workjournal login page in an in-app browser. Sign in and click Approve. You’re returned to Grok with the connector active.

4. Use it

In any Grok conversation, ask “log this decision to my work journal” — or just mention something that implies journal access and Grok will call the tools.