Get your free AI plan
Docs / How Maplith works

How Maplith works

The red thread in five steps, from sources to work, with the app’s menu and the MCP’s tools beside each step.

Maplith reads the systems your company already runs, builds a map of the business from them, finds where the data does not work as it should, and hands the work that follows to your agents under rules you control. That is one thread in five steps. Each step has a place in the app and a group of tools over MCP, and the two are named alike.

1. Sources

Maplith starts from what your company already runs. An admin or an agent connects a system, or uploads an export file, and a scan reads it once, without changing anything in the source. The map keeps descriptions of the data, not copies of its records.

In the app.

  • Sources. What Maplith reads and learns from. Maplith only reads your systems. It never writes to them. Pages: Sources › Integrations, Sources › Scans, Sources › Agents, Sources › Fieldwork.

Over MCP. correct_source_system, answer_question, list_sources, submit_sources, build_map.

2. Map

From each scan Maplith builds a map of the business: the objects and their fields, how they relate, the processes that run through them and the metrics worth tracking. The map says where something lives, by which key, and how far to trust each connection between systems. People correct what is wrong, and an agent reads it before it acts.

In the app.

  • Map. How your company fits together: its systems, its data and how work flows. Pages: Map › Systems, Map › Atlas, Map › Processes, Map › Metrics, Map › Terms, Map › Personal data.

Over MCP. configure_metric, state_relationships, join_review, get_map_overview, get_object, search, fetch, get_process, get_metric, route, ask.

3. Findings

Every scan documents where the company’s data does not work as it should: a reference left blank, two systems that disagree, a copy nobody maintains. A finding carries its evidence, and a person decides what it is. When a person approves a fix, the fix becomes work for an agent.

In the app.

  • Findings. What Maplith found that does not work as your company intends.

Over MCP. update_finding_status, list_findings.

4. Workflows

A workflow is how work is meant to run. Rules say what must always hold and what you want to be told about, and a rule can be checked live in your own systems. Playbooks describe how your people handle a kind of case: an admin approves one before agents are handed it, and a playbook guides the work without granting permission.

In the app.

  • Workflows. What is set up to be handled from now on, and how. Pages: Workflows › The chain, Workflows › All workflows, Workflows › Playbooks.
  • Rules. What Maplith watches for, and what must always hold. Pages: Rules › Watch for, Rules › Must hold.

Over MCP. register_automation, draft_playbook, report_observation, list_automations, get_rule.

5. Work

Work is what is done now. A scan or a rule raises a signal when something needs doing; the app shows it as a task. An agent reads the task’s context, takes it, asks before it acts in your systems, does the work with its own access and records what it did. Maplith never acts in your systems itself.

In the app.

  • Work. What is being done, who has it, and what waits for you. Pages: Work › Board, Work › List, Work › Results.

Over MCP. take_signal, record_action, list_requests, request_action, redeem_action_grant, list_signals, get_task_context, get_value_summary.

Beside every step

Some tools belong to no step, because they are about the connection itself: whether the setup is complete, how to be woken, and how to tell Maplith what its server lacks. They are in the group About the connection: suggest_feature, check_setup, set_wake_subscription, remove_wake_subscription, wake_subscription.

Where to go next

  • Words: what each name means, and what it was called before.
  • Key shapes: which tools a connection is listed, and which may change something.
  • Work the loop: an agent’s main path, from a task to a record of the work.
  • Workflows and departments: what a workflow is, what is derived from it, and how departments apply.
  • The MCP reference: every tool, with its inputs, an example and its refusals.
  • Migration: which tools are being merged, in which order and until when.
  • Changelog: what each release changed in a tool, a field or a page name.

← All docs · Markdown version