Find your symptom below. If none of these resolve the issue, contact support.

Cannot connect to the MCP server

Likely cause

The URL or transport is wrong, the client cannot complete OAuth, or client/workspace settings block remote MCP connections.

Recommended action

Use https://api.achievator.com/mcp with remote Streamable HTTP and OAuth. Confirm your client permits custom MCP connections. In managed AI workspaces, check with the administrator if adding or using the connector is disabled.

OAuth login page does not appear

Likely cause

A pop-up blocker, redirect restriction or client setting is preventing authorization.

Recommended action

Allow the authorization window, try another browser and reconnect from the client. Sign in directly on the Achievator page, then select an active workspace. If you have no active workspace membership, there is no workspace to authorize.

Authorization fails with Unknown client or invalid_client

Likely cause

The client identity is not recognized by Achievator's authorization server.

Recommended action

Remove and add the connection again using the exact server URL so the client can repeat discovery and registration. Use automatic registration if your client supports it, rather than inventing a client ID or secret. If it continues, contact support with the client name and error.

The assistant uses the wrong workspace

Likely cause

A different workspace was selected during authorization, or the conversation is using another connection.

Recommended action

Check the workspace returned by a search and the connection in Settings → Security → Connected apps. Disconnect the incorrect connection, reconnect and select the intended workspace. A prompt or tool argument cannot switch an existing connection's workspace.

Notes, ideas, documents or planning tools are missing

Likely cause

The connection lacks required scopes, the tool list is cached, or a tool is disabled in the AI client.

Recommended action

Refresh tools and enable the relevant actions if your client supports those settings. Older grants do not gain new scopes on refresh. Reconnect to approve missing permissions. Weekly context and preview need tasks.read plus productivity.read; saving also needs tasks.write. Each content family has separate read and write scopes, all prefixed achievator.

401 Unauthorized or a connection that stops working

Likely cause

The access token expired or was revoked, refresh failed, or active workspace membership is no longer available.

Recommended action

Let the client refresh its token or reconnect. Confirm you still have active access to the selected workspace. If the connection was intentionally disconnected, authorize it again only when you want to restore access.

403 Forbidden, insufficient_scope or permission denied

Likely cause

The connection lacks a required scope, your role cannot perform the operation, or the MCP request comes from a disallowed origin.

Recommended action

For insufficient_scope, reconnect with the required permissions. For a resource or role denial, check that you can perform the same action in Achievator; reconnecting does not expand your role. Notes and ideas can use scope personal to search your own personal items without workspace list permission. Report persistent connection-level 403 errors to support.

Search cannot find an item I can see in Achievator

Likely cause

The title/query, connected workspace, permissions or search limits do not match the item. Search tools do not all scan the same fields.

Recommended action

Use a distinctive title and inspect the returned location and scope. Projects search names; tasks search titles/descriptions; ideas search titles; notes search titles/legacy text; documents search titles/summaries/page titles. Content search does not scan current rich-text or page bodies. Narrow capped task/project searches. For content, request the next page while hasMore is true. Personal note search excludes notes attached to personal tasks.

The assistant proposes a duplicate task or content item

Likely cause

The item was not searched before creation, or a capped search did not reveal it.

Recommended action

Ask it to search first, show possible matches, read the matching item and update it if appropriate. Retry a failed write with the same clientRequestId only for that same operation. A deduplicated result means the earlier write succeeded and was not repeated; retry protection is not a substitute for searching.

A description or page rewrite is refused

Likely cause

The expectedRevision is missing or stale, or replacement would lose images, tables or unsupported formatting.

Recommended action

Read the matching context again and use its current revision to rebuild the requested edit. Task rewrites use descriptionRevision; notes, ideas and pages use contentRevision. Append to preserve existing content, or edit complex content directly in Achievator. Do not bypass a conflict by retrying an old revision.

Weekly plan cannot be applied

Likely cause

The plan has blocking issues, lacks approval or an exact preview, or changed after previewing.

Recommended action

Read get_weekly_planning_context and check preview_weekly_plan. Resolve issues such as completed or delegated tasks and decide what to do with unresolved previous-week work. WEEKLY_PLAN_PREVIEW_REQUIRED means a substantial plan needs a preview; WEEKLY_PLAN_STALE or requiresRefresh means read and preview again. Review changes and explicitly approve the exact plan before applying it with the unchanged previewToken.

A productivity review has missing data or unexplained gaps

Likely cause

The review covers only your own recorded activity. Historical Daily Wins or sufficient estimate samples may be unavailable, and individual entries can be capped.

Recommended action

Confirm the requested period and tracking history. Use totals for the full period and do not treat missing entries as proof that no work happened. Ask the assistant to distinguish recorded facts from inference. Untracked gaps are not evidence of sleep or wasted time.

Connection times out or shows a network/Cloudflare error

Likely cause

The client cannot reach api.achievator.com, or a service/network policy rejects the request.

Recommended action

Retry later and check the AI provider's status. A successful browser visit does not prove the provider can reach the MCP endpoint; remote requests may originate from the provider's servers. Contact support with the client, approximate time and error details if it persists.