Fix Democruit MCP Errors and Revoke Access
Identify Democruit MCP permission, quota, rate-limit, and expired-session errors, then recover the connection or revoke client access.
To recover a failed Democruit MCP task, first identify whether the problem is authorization, permissions, tool input, a product quota, or request frequency. Each needs a different fix. Reconnecting does not add a plan allowance, and upgrading does not correct a missing permission. To stop a client's access, open Democruit settings, find Connected agents, and select Revoke access.
Step 1: Read the error before retrying
Note the client, requested tool, error message, and whether the task had already returned a result. Avoid repeating a write request while its outcome is unclear. Check the affected document or action status first so you do not mistake a delayed response for a failed change.
Use this table to choose the next step:
| What you see | Likely category | Next action |
|---|---|---|
| Authorization required or expired | Connection credentials | Sign in or reauthorize as described below |
FORBIDDEN | Tool unavailable for granted scopes | Review the connection's permissions |
INVALID_ARGUMENTS | Missing or invalid input | Supply the required document reference or facts |
| A plan-limit message with a pricing link | Feature allowance | Check the allowance and current plans |
| A rate-limit message | Request frequency | Reduce requests and polling |
| A dashboard confirmation link | Pending approval | Review the action in Democruit |
| An expired upload or confirmation | Temporary workflow expired | Start a fresh request if still needed |
TOOL_EXECUTION_FAILED | Tool operation failed | Read the message and check the task state before retrying |
Match the recovery step to the returned error before retrying.
Step 2: Restore authorization or correct permissions
If authorization is missing, complete the client's OAuth sign-in and consent flow. Verify the endpoint is https://mcp.democruit.com/mcp and that you are connecting the intended account. The Claude, ChatGPT, and Gemini connection guide covers setup for each client. In Gemini CLI, use /mcp auth democruit when the server needs authorization, then complete the browser sign-in.
Access tokens last one hour. A client can refresh access while its refresh token is valid, so a one-hour access lifetime does not necessarily require signing in every hour. Refresh tokens last 30 days sliding and 90 days absolute with offline_access, or seven days sliding and 30 days absolute without it.
If refresh has expired or the connection was revoked, authorize again. Authorization codes last five minutes; restart sign-in if an unfinished code exchange expires. Do not paste tokens into a chat to work around an authorization error.
For FORBIDDEN, inspect the tool's required permissions and the scopes granted to the client. Read and write scopes are separate by product area. A combined application-kit workflow requires resume write, cover letter write, and ATS write permissions; a connection for a smaller task may not have them all. Request only the access needed for the work you intend.
Step 3: Correct the tool input
For INVALID_ARGUMENTS, ask the assistant to inspect the tool's input requirements and identify what is missing. Provide the selected document reference, job description, or other requested facts. Do not let the assistant invent experience or choose a document based only on an uncertain title.
A missing input is not a billing problem. Complete that input before considering plan changes. For TOOL_EXECUTION_FAILED, read the returned explanation and verify whether a document or pending action exists before trying another write.
Step 4: Check a product quota and the upgrade link
A product quota limits feature use under your Democruit plan. MCP uses the same plan allowances as the app. If a tool reports a plan limit, check the affected feature's usage in your account. Review Democruit pricing to compare the available allowances before deciding whether to upgrade.
Feature availability and allowances depend on your current plan. Do not assume every app feature has an MCP tool, or that reconnecting, deleting a document, or waiting a minute restores a consumed AI allowance.
For example, reconnecting Claude does not reset an exhausted ATS check allowance. Review your ATS usage and the current plans before choosing how to proceed. After upgrading, check account usage and retry the intended operation once; if it remains blocked, contact support with the returned error.
Step 5: Reduce requests when rate-limited
The standard API rate limit is 500 requests per minute, the same default used by the Democruit app. OAuth registration and token endpoints have their own tighter limits, so the 500-request figure is not an allowance for rapid sign-in retries. Reduce repeated requests, especially rapid polling while a task is waiting. An HTTP 429 means too many requests. Follow a returned retry delay when available and slow down before retrying. A quota or rate-limit failure can also appear inside TOOL_EXECUTION_FAILED, so read the explanation rather than relying only on that broad code.
Waiting for a rate-limit window does not replenish an exhausted product quota. A connection can have feature allowance remaining and still make requests too quickly. Check which limit the error actually describes.
A shortened response is another separate case. Large responses are paged in groups of 20 items or summarized unless detail=true. Continue using the returned pagination information, or request detail when the task needs full content. A short page alone is not evidence of a quota error.
Step 6: Resolve a pending confirmation or expired upload
Destructive tools wait for confirmation in the Democruit dashboard. Open the returned link and review the exact action. The assistant can check get_action_status; it should not report a deletion as completed while approval is still pending.
A pending confirmation is not an error. The returned approval link opens the action in Democruit; review the target before approving. A denied action reports DENIED, and an undecided action eventually reports EXPIRED.
The confirmation expires after ten minutes. If you still want the action after expiry, start a new confirmation request and review it again. Uploads also have a ten-minute validity window and a 10 MB maximum. Resume import and ATS upload purposes accept PDF only. Create a fresh upload if the previous one expires, and use the requested type and exact file size.
Step 7: Disconnect and revoke access
- Open Democruit account settings.
- Find the client under Connected agents and review its listed scopes.
- Select Revoke access for the connection you want to stop.
- Wait for the successful revocation result; if the settings page reports an error, retry there or contact support.
- Remove or disable the Democruit server in your AI client if you also want to stop it offering tools or prompting for sign-in.
- If you connect that client again later, complete authorization and review the requested scopes again.
Revoke credentials in Democruit, then remove the server from your client if you no longer use it.
Revocation disables the client's authorization grant, access tokens, and refresh tokens for your account. Removing a server entry from the client is a separate configuration step; use Democruit's Revoke access control to invalidate its credentials.
Revoking access leaves your Democruit account and documents in place. It stops future authorized requests using those credentials. For content already received by the AI client, review that client's history and data controls; this revocation does not establish a deletion or retention rule for another service. See the Privacy Policy for Democruit's published data practices.
If the task is still blocked
Contact [email protected] with your client name, tool name, and error message. Describe whether you were signing in, reading a document, saving a change, or waiting for confirmation. Leave passwords, tokens, and private document content out of the support message.