MCP Connector Quickstart

Connect WebWork to your AI assistant in a few minutes.

• Connector URL: https://mcp.webwork-tracker.com/mcp

There are two ways to connect:

1. Connector directory - if WebWork appears in your AI client's connector directory, click Connect there, sign in with your WebWork account, and you are done. The directory uses WebWork's official credentials, so there is nothing to configure. The rest of this page is not needed.
2. Custom connector (connect by URL) - add WebWork by URL together with OAuth credentials that you create yourself in WebWork. Use this if WebWork is not in your client's directory yet. The steps below cover Claude, ChatGPT, and other MCP clients.

Every custom connection authenticates with an OAuth2 app that you create in your WebWork settings:

1. Sign in to WebWork as a workspace Owner or Executive Manager. Your email address must be verified.

2. Go to Settings > REST API.

3. In the OAuth2 Apps section, click Create App.

4. Fill in the two fields:

   • App Name - a label for you, for example Claude or ChatGPT.
   • Redirect URI - the callback URL of the AI client you are connecting. Copy it exactly from this table:

   AI client	Redirect URI to enter
   Claude (web, desktop, mobile)	https://claude.ai/api/mcp/auth_callback
   ChatGPT	https://chatgpt.com/connector_platform_oauth_redirect
   Other MCP clients	The callback URL from that client's documentation

5. Click Create App and confirm your identity with the verification code WebWork emails you.

6. A window shows your Client ID (it starts with ww_) and your App Secret. Copy both now. The secret is shown only this once. If you lose it, revoke the app and create a new one.

An app holds exactly one Redirect URI, so create a separate app for each AI client you connect (one for Claude, another for ChatGPT, and so on).

1. In Claude, open Settings > Connectors and click Add custom connector.
2. Enter a name (for example WebWork) and the URL https://mcp.webwork-tracker.com/mcp.
3. Open Advanced settings and paste your Client ID into the OAuth Client ID field and your App Secret into the OAuth Client Secret field. This step is required: WebWork does not support automatic client registration, so a connection without credentials will fail.
4. Click Add, then Connect. Sign in with your WebWork account and approve the requested permissions (read, write and admin access).

On Claude Team and Enterprise plans, an organization Owner first adds the connector the same way under Organization settings > Connectors; members then connect it from their own Settings > Connectors.

Custom connectors in ChatGPT require developer mode, available on plans that include it.

1. In ChatGPT, open Settings > Connectors, and under Advanced enable Developer mode.
2. Click Create (add a custom connector).
3. Enter a name (for example WebWork) and the MCP server URL https://mcp.webwork-tracker.com/mcp.
4. Choose OAuth as the authentication method and paste your Client ID and App Secret into the OAuth client fields.
5. Save, then connect: sign in with your WebWork account and approve the requested permissions.

Remember: the app you created in Step 1 for ChatGPT must use the ChatGPT redirect URI, not the Claude one.

Any MCP client can connect if all of the following are true:

• it connects to a remote server by URL (Streamable HTTP),
• it lets you enter an OAuth client id and secret, and
• it has a fixed https:// callback URL, which you enter as the app's Redirect URI in Step 1.

If your client also asks you to enter OAuth scopes, separate them with spaces, not commas: read write admin. A comma-separated value such as read,write,admin is rejected with an invalid_scope error.

Clients that only support Dynamic Client Registration, or that use localhost callback URLs (some IDE and command-line clients), cannot connect yet. If your client is one of these, contact support.

Ask your assistant:

• "List my WebWork workspaces."
• "List the projects in my workspace."
• "What are the open tasks in my project?"
• "Start the timer for Alex."
• "Give me the tracked-hours report for last week."

The assistant calls list_workspaces first to find your workspace, then list_members to resolve a person by name, and so on. You do not need to provide ids yourself.

• Redirect or callback mismatch error during sign-in - the Redirect URI saved in your WebWork app does not exactly match your AI client's callback URL. Compare it character by character with the table in Step 1. To change it, revoke the app and create a new one with the correct value.
• Invalid client error - check that you pasted the Client ID that starts with ww_, that the secret is correct, and that the app has not been revoked in Settings > REST API.
• Lost the App Secret - it is shown only once. Revoke the app, create a new one, and update the credentials in your AI client.
• Authorization failed - confirm your account is a workspace Owner or Executive Manager and your email is verified.
• "Not connected" again after a while - your session token expired or was revoked. Reconnect to continue.
• A tool returns a permission error - that action is outside your role or outside the permissions you approved. Reconnect to grant more scopes, or ask your workspace Owner.

• Introduction - what the connector is and what it can do.
• Authorization - the full OAuth2 reference for the REST API.
• Privacy Policy
• Support: support.webwork-tracker.com