One MCP server for your business data

Why one server

A server per vendor means a config entry per vendor, a credential per vendor, and a model that cannot see across them. Memtro keeps the credentials where they were connected, applies the grants an administrator set, and offers the tools of every connected system through one door, so a question about a ticket can read the CRM and the ledger in the same breath, and what the model learns is remembered for the next conversation.

• Memory
  21 tools: search, remember, explore the graph, read it as of a date, and the registers.
• Connectors
  144 systems; every tool that changes something is marked and granted by name.
• As you
  The key identifies a person; the tools offered are the ones that person may use.

Connect it

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Memory tools

• memtro_searchSemantic + keyword search over the organisation/personal knowledge graph: remembered facts, decisions, preferences, people…
• memtro_valuesLook up the recorded VALUES of things — amounts, dates, counts, rates — across entities of one kind, and compare, filter or total them.
• memtro_rememberSave durable knowledge to Memtro's memory so it is available in future conversations.
• memtro_exploreLook up an entity by name (fuzzy, aliases included) and return its neighbourhood in the knowledge graph plus the facts recorded about it.
• memtro_whyWhy a piece of code is the way it is: the pull requests and commits that touched a file, the tickets they closed…
• memtro_commitmentsWho promised what and by when, taken from meeting notes and team chat.
• memtro_update_commitmentChange an entry on the commitment register: mark a promise done, mark it dropped, reopen it, or correct its wording or its due date.
• memtro_record_commitmentPut a promise on the commitment register: a named person or team undertook to do a specific thing.
• memtro_contradictionsThings this organisation believes that cannot both be true, found by reading its memory against itself overnight.
• memtro_answer_contradictionAnswer a contradiction: say which of the two statements stands.
• memtro_raise_contradictionRaise a contradiction nobody had noticed: two things the organisation believes that cannot both be true.
• memtro_glossaryWords this organisation uses in its own way — acronyms, process names, ordinary words used as terms of art…
• memtro_define_termRecord what one of this organisation's words points at, in its own terms.
• memtro_update_termChange a glossary entry: correct or widen what a word points at here, take it out of the glossary, or put it back to be asked about again.
• memtro_timelineHow knowledge changed over time.
• memtro_schedule_onceSchedule a ONE-OFF task at a single future moment: "remind me in a week to…", "on Friday afternoon check whether X landed", "chase this in two days".
• memtro_schedule_jobCreate a scheduled job: a task the assistant will carry out on a cron schedule with the same tools, as this user, saving each run's report to a chat.
• memtro_list_jobsList this user's scheduled jobs and the organisation's shared ones, with schedules, next/last run and status.
• memtro_update_jobChange, pause, resume, run now or delete a scheduled job (by id from memtro_list_jobs).
• memtro_metricsThe organisation's saved metrics: each one's question, latest value, recent values and when it next runs.
• memtro_save_metricSave a question as a metric that is measured on a schedule, so its figure is tracked over time and remembered with its provenance.

A server for every connector

Each page lists that system's tools, the setup, and who may use it. Connect the system on Dashboard → Connections and its tools join the same server.