API Key

API keys are being deprecated

API key authentication is being replaced by OAuth. Existing keys will continue to work, but we recommend setting up OAuth for new connections. See the OAuth setup guide for Claude Code to get started.

Generate an API key

Sign in and open Settings
Under API Keys, click Create new key
Give it a name (e.g. "Claude Code", "Codex", "Copilot")
Copy the key immediately — it won't be shown again

Your key looks like this:

tj_a1b2c3d4e5f6...

The tj_ prefix identifies it as a TaskJunky API key.

How authentication works

Your API key identifies you to the hosted TaskJunky MCP server when you use legacy API-key authentication over HTTP.

HTTP transport (remote)

The key is sent as a header with each request. Both formats are supported:

x-api-key: tj_your_key_here

or as a Bearer token:

Authorization: Bearer tj_your_key_here

Key management

Create multiple keys — one per tool (Claude, Codex, etc.) so you can revoke individually
Keys never expire — but you can delete them anytime from Settings
Last used tracking — the dashboard shows when each key was last used
Prefix only — after creation, only the first 10 characters are shown in the UI

Changing your API key

If you need to rotate your key, generate a new one from Settings, then update any clients still using legacy Bearer-token configuration.

Security

Never commit your API key to version control
Use environment variables or your tool's secrets management
If a key is compromised, delete it immediately from Settings and create a new one