Achievator's MCP (Model Context Protocol) server lets supported AI assistants securely access and work with your Achievator data. Ask it to find work, capture tasks, plan a week, review recorded time, and create or update notes, ideas, documents and pages. You describe the outcome in ordinary language; the assistant chooses the tools available to your connection.

MCP server URL

MCP server URL
https://api.achievator.com/mcp

Use remote MCP over Streamable HTTP with OAuth authentication. Sign in on Achievator's authorization page and select your workspace; no API key is needed.

Connect and get started

  1. 1

    Add Achievator to your AI client

    Use an available Achievator connector or add the server URL above as a remote MCP connection with OAuth. Follow the Claude setup guide or the ChatGPT setup guide. For the current ChatGPT custom-server flow, see OpenAI's official guide.
  2. 2

    Sign in and authorize the right workspace

    Sign in directly with Achievator, select the workspace and review the requested permissions. The connection uses your existing permissions in that workspace and can also access your own personal items supported by its tools. You need an active workspace membership to connect.
  3. 3

    Enable Achievator in the conversation

    Return to your AI client and select or enable Achievator for the conversation if required. In ChatGPT, install the resulting plugin, then type @ in the prompt box and select it. Tool availability depends on the permissions approved for this connection and your client's settings.
  4. 4

    Start with a read-only request

    Try: “Use Achievator to find my project named [your project name]. Show matching projects and the connected workspace.” Check the returned workspace and choose the correct match. If you have no projects, try: “Use Achievator to list my recent tasks.” An empty result can be valid; see troubleshooting if expected items are missing.
  5. 5

    Use a walkthrough and review the result

    Choose a tool walkthrough below, replace example names with your own and state whether you want a draft or a saved change. After a write, ask for the changes and the Achievator link so you can inspect the saved result.

What you can do

  • Projects and tasks — Find projects and tasks, capture a discussion as a task, and update descriptions, dates and checklists.
  • Weekly planning — Review unfinished work and capacity, preview a Weekly Focus and Weekly Wins, then save the plan after approval.
  • Productivity reviews — Review recorded time, compare plans with actual activity, and ground future estimates in your history.
  • Notes — Find, read, create and update personal notes or notes attached to existing work.
  • Ideas — Capture and develop personal ideas or ideas linked to an existing supported parent.
  • Documents and pages — Find documents, read their pages, create a document with its first page, and add or update pages and subpages.

Achievator currently offers 25 MCP tools. Your connection exposes the tools allowed by its approved permissions. See the MCP Tools Reference for full details.

Tool walkthroughs

Start with the prompt for your goal, then follow the steps. Replace example names with your own. You do not need to call tools yourself; the tool links explain what the assistant uses at each stage. Availability depends on your connection's scopes and your existing resource permissions.

Turn a conversation into a task

Try this prompt:

Use Achievator to save our release checklist as a task in the Website Launch project. Search first and reuse an existing task if it covers the same work. Keep our decisions in the description, put implementation steps in the checklist with estimates in minutes, and set the start date to today. Show me the proposed task before saving it.

Tools used: search_projects, search_tasks, get_task_context, create_task, update_task

  1. 1

    Identify the project and existing work

    Replace Website Launch with your project name. The assistant finds the project, searches for existing work and asks you to choose if several results match. It reads any task it intends to reuse.
  2. 2

    Review the draft

    Check the destination, title, dates, context and checklist. Say whether this should be personal or belong to the project. Checklist estimates are whole minutes; these task tools do not set a whole-task estimate.
  3. 3

    Save and open the result

    When the draft is right, ask the assistant to save it. It creates the missing task or updates the existing one, reports the changes and gives you an Achievator link. Keep decisions and requirements in the description, rather than a chat transcript.

What to expect: A task you can understand later without rereading the conversation. Omitting the project creates a personal task. Task drafts appear in conversation; there is no separate task-preview tool.

Update a task and preserve its context

Try this prompt:

Find the task about preparing the launch email in Website Launch and read it first. Add our new decision to the description, move its due date to next Friday, and add a checklist step to review the final copy. Keep the existing description and checklist. Tell me exactly what changed.

Tools used: search_projects, search_tasks, get_task_context, update_task, rewrite_task_description

  1. 1

    Choose the exact task

    The assistant searches and reads the current fields, description and checklist. Use a result's real task identity rather than a made-up task number. Ask to see matches if the title is ambiguous.
  2. 2

    Specify an addition or a rewrite

    New information uses appendToDescription. Checklist changes use existing item IDs. For replacement, explicitly ask to rewrite a named section or the whole description; the assistant uses rewrite_task_description with the latest descriptionRevision.
  3. 3

    Handle conflicts and review the changes

    If the description changed after it was read, read again and rebuild the rewrite. Images or embeds can block replacement; append or edit in Achievator. The result lists what changed. Marking a task completed uses COMPLETED.

What to expect: Only the requested fields change. Dates use YYYY-MM-DD in your calendar. Ask to clear a date when you want it removed; startDate and dueDate can be cleared explicitly.

Plan your current or next week

Try this prompt:

Use Achievator to plan next week. Review my Current Focus, this week's unfinished work, existing commitments and capacity. Prefer existing tasks. Propose one Weekly Focus and around five Weekly Wins, explain estimates and warnings, and preview the plan. Wait for my approval before saving anything.

Tools used: get_weekly_planning_context, preview_weekly_plan, apply_weekly_plan

  1. 1

    Read the week and decide what carries forward

    Choose this week or next week. The assistant reads strategy, execution, commitments and candidates together. If unfinished work needs a decision, choose to continue the focus, carry only selected unfinished tasks or start fresh. Nothing rolls forward or is deleted automatically.
  2. 2

    Set an outcome and realistic capacity

    A Weekly Focus states what you intend to achieve; Weekly Wins are the few tasks that determine success. If capacity is missing or partial, tell the assistant roughly how much focused time you expect. Unestimated tasks are unknown effort. Only your own tasks belong in your personal week.
  3. 3

    Review the preview

    Check the focus, final wins, new tasks, tasks moving into the week, estimated time and every warning. Resolve blocking issues first. Current Focus guides planning; you can intentionally include other obligations. Existing wins stay unless you ask to replace or remove them.
  4. 4

    Approve the exact plan and save

    Once the preview is right, explicitly approve it. The assistant applies that same plan with its unchanged previewToken and userApproved set to true. All changes save together. A stale or changed plan needs fresh context, a new preview and approval of changed details.

What to expect: A saved Weekly Focus, Weekly Wins and task schedule. A direct small request such as “Make this task a Weekly Win” can be applied without a substantial preview. Removing a win leaves its task scheduled in the week.

Review time and improve estimates

Try this prompt:

Use Achievator to review last week. Compare my recorded time with planned tasks and Weekly Wins, show where the time went and whether my estimates were realistic, and give me three practical adjustments. Separate tracked facts from your interpretation.

Tools used: get_productivity_review_context

  1. 1

    Choose a period

    Ask about today, yesterday, this week, last week or this month. For another period, give inclusive start and end dates spanning at most 62 days. Achievator resolves day boundaries in your time zone; weeks start Monday.
  2. 2

    Compare recorded facts

    The assistant uses tracked minutes, project and task distributions, available Daily Win and Weekly Win alignment, and estimated versus actual time. It should state when data is missing. An untracked gap does not prove sleep, wasted time or procrastination.
  3. 3

    Use history carefully

    Ask for a few specific adjustments. If estimateCalibration has enough data, its median ratio can inform future estimates. A small sample is only a rough hint; this tool does not match similar task descriptions.

What to expect: A read-only review of your own recorded activity. Individual entries may be capped while totals cover the full period. Use weekly planning to change your plan.

Save decisions as a note

Try this prompt:

Use Achievator to find a note titled Launch decisions in Website Launch. Read it if it exists and append today's agreed decisions. Otherwise create it in that project. Preserve existing content and show me what was saved.

Tools used: search_projects, search_notes, get_note_context, create_note, update_note

  1. 1

    Choose the note and destination

    Search by title and inspect the location. Notes can be personal or attached to a project, goal, target, milestone, endeavor or task. Name one existing parent; for a personal note, leave location out.
  2. 2

    Read before adding decisions

    Read an existing note with get_note_context, then append Markdown to preserve text and media. Creating a note requires a title and nonempty content. You can also ask to pin it.
  3. 3

    Rewrite only when requested

    Full replacement uses content.mode replace_all with the current contentRevision as expectedRevision. If the note changed, read again. If media or formatting would be lost, append or edit in Achievator. Updates cannot move a note or change its owner.

What to expect: One note with the agreed decisions. Search does not scan current rich-text bodies. Personal note search covers standalone notes, not notes attached to personal tasks.

Capture and develop an idea

Try this prompt:

Use Achievator to find an idea called Customer onboarding experiments. If it exists, read it and append the experiment we discussed. Otherwise create a personal idea with that title and a concise description. Keep existing text.

Tools used: search_ideas, get_idea_context, create_idea, update_idea

  1. 1

    Search the title and choose the location

    Idea search matches titles. Choose personal or name an existing project, goal, target, milestone or endeavor. Omit location for a personal idea; task attachment is not supported.
  2. 2

    Capture or develop the idea

    Creating an idea accepts a title and optional Markdown description. Updating reads its context first and uses content.mode append for new text. A requested full rewrite requires the current revision.
  3. 3

    Review what changed

    The assistant reports the saved title and changes. Updates preserve location and ownership. If you want executable work, explicitly ask to create or update a task through the task workflow.

What to expect: An idea you can return to and develop. Notes and ideas link to their list pages; ask the assistant to identify the saved item by title too.

Create a document and maintain its pages

Try this prompt:

Use Achievator to find the Launch brief document in Website Launch. Read its page list and the Requirements page before editing. Append our agreed requirements. If the document or page is missing, create it. Keep existing content and give me the document link.

Tools used: search_projects, search_documents, get_document_context, get_document_page_context, create_document, update_document, create_document_page, update_document_page

  1. 1

    Find the document and exact page

    Search matches document titles, summaries and page titles. get_document_context returns metadata and the page tree, not page bodies. Use the selected documentId and pageId to read that page with get_document_page_context.
  2. 2

    Create only missing content

    create_document makes a document and its first page. description is a short plain-text summary; content is the first page's Markdown. create_document_page adds another top-level page or one subpage under a top-level page. Read the tree first to avoid duplicates.
  3. 3

    Use the right update

    update_document changes document title, summary or pinned state. update_document_page changes a page title or body. Append preserves text, images and tables. Full replacement needs the page's current contentRevision and is refused if unsupported content would be lost.
  4. 4

    Open the saved document

    The assistant lists what changed and returns a document link. These tools cannot move or delete documents or pages. Pages support only one level of subpages.

What to expect: A document with the intended pages and preserved content. Omit location for a personal document or choose one supported existing parent in the connected workspace.

Supported clients

Claude

Anthropic · Add Achievator as a custom connector via the MCP URL.

ChatGPT

OpenAI · Use a custom MCP plugin with OAuth; installation and workspace settings control access.

Other MCP clients

Standards-compliant · Requires remote Streamable HTTP and support for Achievator's OAuth flow. Local-only or older SSE-only clients are not sufficient.

Security

  • OAuth 2.1 with PKCE — your password is never shared with any AI client.
  • Scoped permissions — the AI can only do what the granted scopes allow.
  • Access follows your permissions in the connected workspace, plus your own supported personal items.
  • Revocable at any time — remove access in Achievator without contacting support.
  • No API keys — the AI client holds scoped OAuth tokens that can be revoked.

Read tools do not save changes. Write tools can create or change content; a rewrite can discard replaced text. Substantial weekly plans require a preview and explicit approval. Other confirmation prompts depend on your AI client, so ask for a draft before saving when you want to review it.

For full technical details see MCP Permissions & Security.

Data access

OAuth scopes control which tools your connection can use. They do not expand your existing permissions. Data is limited to accessible items in the connected workspace and your own supported personal items. Planning and productivity reviews cover your own work. Supported scopes:

achievator.projects.read

Read projects

Search names and read returned project details in the connected workspace, subject to your project access.

achievator.tasks.read

Read tasks

Search accessible workspace tasks and your own personal tasks, and read their fields, descriptions, checklists and links. Combined with productivity.read, enables weekly context and previews.

achievator.tasks.write

Write tasks and weekly plans

Create and update tasks, append or rewrite descriptions, and add or update checklists. With tasks.read and productivity.read, enables saving approved Weekly Focus, Weekly Wins and task schedules.

achievator.productivity.read

Read productivity and time tracking

Read your own recorded time, planning, focus alignment, estimates and estimate calibration. With tasks.read, enables weekly-planning context and previews.

achievator.notes.read

Read notes

Search accessible workspace and personal notes and read current note Markdown, location and revision. Your normal list and resource permissions still apply.

achievator.notes.write

Write notes

Create notes and update accessible note titles, pinned state and content. Notes may be personal or attached to one supported existing parent, including a task.

achievator.ideas.read

Read ideas

Search accessible ideas by title and read their current Markdown descriptions, locations and revisions.

achievator.ideas.write

Write ideas

Create personal or linked ideas and update their titles and rich-text descriptions under your existing permissions.

achievator.documents.read

Read documents and pages

Search accessible documents, read document metadata and page trees, and read selected pages as Markdown with revisions.

achievator.documents.write

Write documents and pages

Create a document and its first page, update document metadata, add pages or one level of subpages, and append or replace accessible page content.

Full scope documentation → Permissions & Security

Revoking access

You can revoke MCP access at any time without contacting support.

  1. 1

    Open Achievator Settings

    Go to Settings → Security → Connected Apps.
  2. 2

    Find the AI connection

    Locate the Claude, ChatGPT, or MCP client entry.
  3. 3

    Disconnect it

    Click Disconnect and confirm. Access and refresh tokens for that connection are immediately invalidated.
  4. 4

    Disconnect from your AI client

    Also remove the connector from your AI client to avoid confusion.

Frequently asked questions