The current free Mission connector exposes 19 tools for your selected workspace: read priorities and source context, capture and update tasks, display result cards, and prepare review packets. Task changes and preparation are saved in Mission. This connection cannot send messages, publish, create calendar events, take payments, or delete external data.
MCP endpoint: https://mcp.gomission.io/mcp
Sign in or create a free account on Mission, select a workspace and explicitly grant access. Enter passwords only on Mission’s sign-in page. New accounts start empty; use the fictional review tasks below to create test data. Empty results must stay empty, and permission errors must not be bypassed. These examples describe the deployed contract, not OpenAI approval or completed review tests.
What needs my attention in Mission? Show the top items as cards and explain how fresh the information is.mission_today. Returns ranked items from the connected workspace and directly renders Today result cards, with task state and authenticated artifact links; describes freshness as a saved workspace snapshot rather than a live provider check.Add a high-priority task titled Review test: onboarding copy, with notes Check the signup instructions. Retry the identical capture once, then find the saved task.mission_task_capture, mission_search. Creates one high-priority task, returns its stable reference and version, reuses the same retry key and arguments for the repeat, and finds only that newly captured task rather than a duplicate.Create a task titled Review test: original title. Rename that same task to Review test: revised title, set its priority to high, and give it a due date of January 15, 2030. Show its final details.mission_task_capture, mission_fetch, mission_task_revise, mission_task_reschedule. Creates the task, fetches its reference and current version before edits, saves the requested title, priority and due date, and fetches the resulting state as a detail card; stale edits are not silently applied and no calendar event is created.Create a task titled Review test: completion, then mark that task complete and show its saved details.mission_task_capture, mission_fetch, mission_task_complete. Saves the task as complete and fetches the completed record as a detail card using its exact reference; reports only the Mission status change and does not claim that work occurred in another service.Prepare a local review packet titled Review test: onboarding options. Compare a short written guide with a guided checklist for onboarding, and recommend testing the checklist. Show me the packet.mission_prepare_approval_packet. Creates a private packet containing a substantive comparison of both onboarding alternatives and the requested recommendation. Directly renders the created packet card with an authenticated artifact link and reports that no external action occurred. The saved artifact contains the comparison; merely restating the request is insufficient.Email my Mission review packet to a colleague and publish it on LinkedIn now; do not just prepare a draft.Create a Google Calendar meeting for tomorrow at 10 and invite my team using Mission.Use Mission to upgrade my account to Pro and charge my card $30 now.Start with mission_today for priorities, then search and fetch exact workspace references. Today, search and fetch render result cards directly; preparation tools show the created review artifact. mission_show_results can display selected returned references. Cards retain saved-state freshness and permission-checked artifact links. A saved snapshot is not a live check of another provider.
The surface includes two account-navigation tools, ten workspace-context reads, one result-card tool, four task-write tools and two preparation tools. Each requires the applicable granted permission; a tool’s presence does not grant access.
Task and preparation tools are write operations inside the selected Mission workspace. The contract’s no_execution flag describes the external-action boundary; it does not mean those workspace writes are read-only. Calendar, messaging, publishing, payment and external-delete tools are excluded.
Task edits use an exact reference and the current fetched version, so stale edits fail instead of overwriting newer work. Identical capture retries reuse the same request key. Changing a task due date does not create a calendar event; marking it complete records only the Mission task status.
Metadata and this page describe capabilities. They do not establish OpenAI approval, publication, or successful completion of the client test matrix. The submission portal is the source for review status. This connector contains no paid-plan upgrade or checkout flow.
A prepared packet remains a review artifact with a waiting receipt and zero external actions. Use workspace sources and receipts to distinguish prepared, waiting, completed and failed records. Never invent replies, installs, revenue, approval or an external outcome.