Democruit MCP Guide: Workflows and Example Prompts

Use the Democruit MCP server by connecting your AI assistant, choosing the saved document or application you want to work on, and describing the result you need. You can build a resume, prepare an application kit, check an ATS report, practice a written interview, or organize your job search through a conversation. Review the result and verify any saved changes in Democruit.

This guide gives you repeatable workflows and prompts for an already connected assistant. Replace the text in square brackets with your own details. Use each prompt's copy button, review the response, and use the follow-up when you are ready. If you have not connected yet, follow the Democruit MCP setup guide. The server address is https://mcp.democruit.com/mcp.

Choose a workflow by the result you need

• Starting from scratch: build a resume with guided questions or import the text of an existing resume.
• Preparing an application: improve bullets, tailor a separate resume, write a cover letter, and review ATS findings.
• Managing opportunities: save a job, attach documents, record conversations, and plan your week.
• Preparing for interviews: research the correct company, practice written answers, and revisit weak answers.
• Updating your public presence: draft LinkedIn copy or turn a resume into a personal website draft.

The assistant needs the relevant account permissions, and some features use your plan allowance. A prompt cannot grant missing access. Use the MCP access help if a task is unavailable, and check current plan details when an allowance is reached.

Write prompts that produce checkable results

A useful prompt explicitly names Democruit, identifies the source, describes the task, preserves the facts, and defines the stopping point. Include Democruit in follow-up prompts too, so the assistant knows which service to use. For example: "Use my Customer Support resume in Democruit, suggest three clearer bullets using only its existing facts, and show the suggestions before saving."

Ask the assistant to list documents when the title is unclear. You can choose by the displayed title rather than finding technical IDs yourself. If there are more results, ask it to continue the list. Before a detailed edit, ask it to read the complete selected document.

Weak prompt: "Fix my application in Democruit."

This leaves the document, target role, and expected changes unclear. It also gives you no specific result to verify.

Improved prompt:

Suggestions and saved edits are different outcomes. New documents and ordinary edits can be saved with the necessary permissions. Actions such as deleting records, replacing generated content, applying ATS fixes, or changing website visibility require the assistant to explain the effect and obtain explicit confirmation in the conversation. Confirm the specific action after reviewing it.

Name the source, define the change, preserve the facts, and check the result before asking to save.

Workflow 1: Build a resume through guided questions

Use this when: you know your experience but do not have a complete resume. The guided flow collects real information one question at a time and allows optional settings to use defaults.

1. State your target role and ask for guided creation.
2. Answer the returned questions about experience, education, projects, and skills.
3. Review the collected facts before saving and open the resulting resume.

If you already have notes, paste them as a block and ask the assistant to use them to prefill the draft. It should ask about missing or invalid details rather than making you repeat everything.

Check the result: the sections represent what you actually did. A student project should not become a job, and a course should not become a certification. The resume guide for limited experience helps you choose credible evidence.

Workflow 2: Import an existing resume without replacing it

Use this when: your resume is in a file or another editor. Text import creates a new resume by default. Replacing a saved resume is a separate action requiring explicit confirmation.

If your AI app can extract text from an attached file, you can ask it to import that complete extraction. File-reading and direct-upload support vary by client. If it cannot read or transfer the file, paste the text or use the Democruit editor.

Check the result: compare contact details, dates, headings, bullets, and links with the original. Text import can reorganize content into builder sections; it is not a promise to reproduce the original visual layout.

Workflow 3: Improve bullets without inventing achievements

Use this when: a resume describes duties but leaves your contribution unclear. The bullet-drafting tool returns suggestions without saving them.

For example, Priya's original bullet says "Helped with support tickets." She confirms that she answered billing questions and documented recurring issues for the product team. A defensible revision is "Answered customer billing questions and documented recurring issues for the product team." Adding "reduced tickets by 40%" would require evidence she has not provided.

Check the result: the revised bullet makes the work easier to understand without expanding its meaning. Use the guide to showing impact without metrics when you have useful outcomes but no reliable numbers.

Workflow 4: Create an application kit for one posting

Use this when: you have an accurate base resume and a specific opportunity. An application kit creates a separate tailored resume, matching cover letter, and ATS report using the selected resume's facts. It needs access to all three product areas.

Read the posting first and confirm the company, role, location, and essential requirements. Paste the full text when the assistant cannot access a link. A job posting URL alone may be unavailable to your client or may have expired.

Example: Mateo has a general operations resume and finds a customer onboarding role. His resume already describes training new users and documenting handovers. Tailoring can emphasize those activities and use the posting's terminology where accurate. It should not add experience with a named CRM that Mateo has never used.

Check the result: both documents tell the same story, preserve dates, and name the correct employer. An ATS score is diagnostic feedback, not a hiring prediction. The resume-tailoring guide explains how to prioritize relevant evidence.

Workflow 5: Write a cover letter from a selected resume

Use this when: you need a letter without creating the whole application kit. Supplying a resume and job description can generate a new letter. You can also create a blank draft and work on its wording yourself.

Read the greeting, employer name, evidence, and closing. Tell the assistant about a real reason for your interest if you want a more personal opening; it cannot infer one from your resume.

Check the result: a generated replacement of existing letter text requires confirmation. Name the letter and the replacement you approve. You can compare designs in the cover letter templates after the message is accurate.

Workflow 6: Check ATS findings and choose a supported fix

Use this when: you want to inspect an existing resume before applying. ATS means applicant tracking system. The check returns a report you should read before requesting repairs.

1. Verify that the report uses the intended resume and posting.
2. Separate formatting issues, unclear evidence, and genuinely missing qualifications.
3. Ask for a preview of a supported fix and approve only the changes you understand.

Check the result: reopen the resume and compare the affected section. Do not add a skill merely to raise a score. A PDF-upload check is available only when the client can transfer the actual file bytes; otherwise check a saved resume. The ATS Resume Checker provides a product entry point for the same task.

Workflow 7: Save an opportunity and attach the right documents

Use this when: you want one record containing the role, company, stage, and materials. A tracker record organizes your search; creating one does not apply to the employer.

If you have already submitted, give the real application date and current stage. Avoid telling the assistant to mark something submitted because the documents are ready.

Check the result: company, role, stage, dates, and attached versions are correct. See the Job Tracker to inspect the record and the application-tracking fields guide to decide which details matter.

Preparing documents, submitting to the employer, and recording the submission are separate steps.

Workflow 8: Research the correct company before an interview

Use this when: you need background on an employer and questions to investigate. A company name can refer to several organizations, so supply its official website when known.

If confirmation is requested, verify the website and organization before agreeing. Research can continue in the background; a queued response is not a finished report. Let the assistant check status at the returned interval rather than starting another request.

Check the result: dates and sources support the claims. Research may contain uncertainty or outdated information. Use the report as preparation, and verify important claims against current employer materials.

Workflow 9: Practice a written interview one answer at a time

Use this when: you want structured practice grounded in your resume and target role. MCP supports written interview sessions; live interview requests open the dashboard experience.

Answer with a real situation, your task, the action you took, and the outcome. If you do not know a number, describe an observable result accurately. The interview-story preparation guide helps you select examples before practice.

The completed session generates a review after all questions have answers. Asking the assistant to finish early cannot produce a completed session with missing responses.

Check the result: feedback relates to what you actually said. A review session uses the written-interview allowance too. Keep a successful answer structure, but avoid memorizing invented wording as your own experience.

Workflow 10: Draft a follow-up and record the conversation

Use this when: you have a real reason to contact an employer, such as thanking an interviewer or checking a stated timeline. Email tools prepare text; you send it through your own email app.

Review the recipient, tone, and facts, then send it yourself. The Email Template Builder is another place to prepare the message. Timing should reflect the employer's instructions and your actual conversation, not a universal schedule.

Check the result: the tracker records an action you completed. A draft should not become a sent message, and silence should not become an inferred rejection.

Workflow 11: Plan the week from your saved applications

Use this when: you need to decide what deserves attention today. The workspace agenda summarizes application progress, upcoming interviews, and missing follow-up or thank-you records.

The agenda reflects recorded information. If you sent a message outside Democruit but never logged it, the assistant may see a missing note. Correct the record before treating the reminder as a new task.

Check the result: the plan fits your time and uses actual dates. The weekly job-search system guide explains how to balance applications, preparation, conversations, and review.

Workflow 12: Draft LinkedIn copy from your resume

Use this when: your profile needs a clearer professional focus. The MCP tools draft a headline or About section without saving to Democruit or posting to LinkedIn.

Check the result: the copy is consistent with the resume and appropriate for a public audience. Review and paste the chosen version into LinkedIn yourself. The LinkedIn headline guide helps you compare the options.

Workflow 13: Turn a resume into a private website draft

Use this when: you want a personal website based on existing career information. Creating a draft and publishing it are separate actions.

Inspect the hero, experience, projects, contact information, and links. Some resume details may be useful to a recruiter but unnecessary on a public website. Adjust the draft before changing visibility.

Check the result: the website's saved visibility matches your decision. Taking it offline also requires confirmation. A custom domain needs a separate connection and DNS checks; creating the website does not complete that setup. Browse personal website templates when choosing a design.

Workflow 14: Preview and export the finished documents

Use this when: you have approved the content and need files for an employer. PDF exports return download links and require both read and write access for the selected document type.

Check the result: open each PDF and inspect page breaks, clipped text, spacing, links, and contact details. A correct chat summary cannot verify the rendered file. Compare resume templates if the content needs a different layout, and follow the employer's requested file format.

Common mistakes and how to fix them

1. Using an ambiguous document name. Similar titles make it easy to choose the wrong version. Ask for the saved list, select the displayed item, and keep referring to it throughout the flow.
2. Letting the assistant invent missing facts. Generic requests can encourage plausible but unsupported achievements. Set a factual boundary and answer questions about missing evidence; remove any claim you cannot defend.
3. Confusing a draft with a saved or sent result. A useful response may contain only proposed text. Ask for a saved edit when intended, check the document, and record emails only after you send them yourself.
4. Overwriting the base resume accidentally. A request to tailor "my resume" can leave the destination unclear. Request a new version or application kit and explicitly retain the original.
5. Retrying a slow creation without checking. A timeout does not prove that nothing was saved. Ask the assistant to inspect existing results and resume the original operation before creating another kit or report.
6. Treating a score or research claim as certainty. Reports provide findings, sources, and warnings, not guaranteed outcomes. Read the evidence, verify important claims, and distinguish a missing qualification from a wording issue.
7. Assuming every client can process files. A file in chat is not necessarily available to the server. Use complete extracted text for import or a saved resume for ATS when the client cannot transfer bytes.
8. Confirming an action without reviewing its scope. Deletion or publication can affect the wrong item if the selection is unclear. Check the named record and exact effect before confirming; ask for a new preview if your request changes.

Best practices for longer flows

Work through one opportunity at a time and keep its base resume, tailored documents, tracker record, and interview context connected. Use the same saved records across steps rather than recreating them. When a result is incomplete or still running, continue that operation before beginning another.

Ask for concrete outputs: a comparison of original and revised bullets, a requirement-to-evidence review, a saved record link, or a labeled PDF download. These make it easier to check that the task succeeded. Give missing facts yourself and keep recommendations separate from changes you have approved.

Remember that connected assistants can receive the account information you authorize them to read. Avoid including unnecessary sensitive details in prompts or public website copy. Review Democruit's privacy policy and your AI app's controls, and revoke the connection under Connected agents in Democruit settings when you stop using it.

Final workflow checklist

• I selected the intended saved document or job and checked the complete relevant content.
• I provided the actual posting, dates, and career facts needed for this task.
• I stated whether I wanted suggestions, a new document, or an edit to an existing record.
• I reviewed any requested confirmation against the exact action and selected item.
• I verified saved changes in Democruit and opened exported files to check their layout.
• I submitted applications and sent messages through the appropriate external service myself.
• I recorded actual completed actions rather than treating drafts as submissions or sent messages.
• I checked existing results before retrying a slow creation or starting duplicate research.

Frequently asked questions

Last updated: November 3, 2026. Examples were checked against Democruit's current MCP tool contracts and workflows. Available tools depend on granted permissions and client capabilities.