"A system for enhanced thinking processes and task management" matching MCP tools:

• create_project_tokenA

  EchoRelayA

  Mint a PROJECT-scoped management token (`er_mcp_`) for MCP and REST; it cannot authenticate relay traffic. Use it after create_project to configure a fresh project, or for any project you already own. Attenuated by design: the scopes must be a subset of THIS management token's own grant (`read` is always included), expiry is mandatory (1–90 days, default 30, never "never"), and the minted management token (being project-scoped) can never mint management tokens itself. `spend` is human-granted only: no management token, of any scope, can mint one carrying it. Mint a spend-scoped token from the project's panel instead. Requires an ACCOUNT-scoped management token and the `config` scope. Returns the plaintext exactly once; only its hash is stored.

  ConnectorNo auth

• submit_responseA

  Ansvar: EU Compliance & Legal IntelligenceA

  Provide an answer to the current step in a compliance workflow. Use this when someone provides information requested by the workflow, such as 'our system processes health data' or 'we use AES-256 encryption'. The workflow engine validates the response and advances to the next step. Pass user_acknowledged=true only after the user has supplied the fields listed in user_provided_fields. evidence_references accepts document UUIDs, doc:// segment URIs, or regulatory URLs. For an unattended gate, pass approved_by='auto' and leave user_acknowledged=false so the report does not misrepresent automation as human review. approved_by accepts only 'auto'; human review is asserted via user_acknowledged, never by naming an approver.

  ConnectorOAuth

• commands_manageA

  9botA

  Reads and manages custom or system commands triggered by explicit user text. Use automations_configure for continuous reactions without a command and workflows_design for multi-step processes. Create, update, toggle, reorder, credential, and delete operations change persisted state; test_api also calls an external endpoint. After an uncertain write, read the command by identifier or trigger before retrying. For a preview, set input.preview=true; preview never applies the mutation. When confirmation is required, repeat the same operation and parameters with the returned input.confirmation_id.

  Connector

  Destructive

  OAuth

• flow_recording_saveA

  Robot Actions — Remote Device ControlA

  Save a completed recording to the database. Waits for any pending background captures (page source + screenshots) to finish before persisting. When the user has a test-management system connected (TestRail, Jira/Xray, Azure DevOps), saving a test REQUIRES tmsLink: the TMS case this automates. Find it with testrail_find_cases, jira_search or azdo_search_work_items. If you omit it the save is rejected and the recording is kept, so you can retry with the link.

  ConnectorOAuth

• scale_serviceA

  ValetA

  Set how many processes of one type an app or agent runs. For an app, give process_type, such as web, and a count from 0 up to the organization's cap. For an agent, count is 0 (paused) or 1 (running). Scaling down stops running processes, and scaling web to 0 takes an app's URL offline, so confirm with the user first. Setting the count it already has changes nothing. Websites run no process and are refused. Changing an agent's model is not offered here. Requires connecting a Valet account.

  Connector

  Destructive

  No auth

• get_eval_itemsA

  aioA

  Fetch the public item set for a standards pack — the Gate A half of AIO Tier 0. Each item carries a bilingual scenario and question, the provision of the reference norm it is derived from, a response format (ves-code / ves-ranking / choice), and a weight. Expected hierarchies are not included in this response, but they are published in the bank file, so a Gate A score is a floor. Use this to practise or to score Gate A alone. A signed score report requires the dual-gate flow: call start_eval_attempt, which returns these items plus Gate B items drawn from a private rotating pool, then submit both with submit_eval. Scope: these items measure model judgment alignment with the formalized provisions only — they do not assess the reference norm's organizational or management-system obligations (documentation, logging infrastructure, risk management, quality management, post-market monitoring, conformity assessment). CC BY 4.0.

  ConnectorNo auth

• update_my_profileA

  Vibe ManufacturingB

  For a manufacturer's agent (needs the supplier token): change processes, materials, certs, formats, industries, signals, machines, lead_time_days, min_order_qty, notes or notify_email. Fields you leave out keep their value; a field you send replaces it whole (a processes list replaces the stored list, so send the complete list, not only additions). Name, domain, country and address cannot be changed here. Set authorised: true only after the manufacturer confirmed the change.

  Connector

  Destructive

  No auth

• list_glossaryA

  raumnebenanA

  Lists published glossary entries covering product management, agile delivery, user research, and product thinking terminology, including term names, comprehensive definitions, and metadata. Returns all glossary entries in one unpaginated response. Use it for term definition questions ("what is X?"). For articles explaining or applying a method, prefer search_articles.

  ConnectorNo auth

• continue_jobA

  CatchAll (by NewsCatcher)B

  Expand a job by processing more records beyond the initial limit. This increases the number of records the system processes (which costs additional credits). Only use this when the user wants MORE data processed. This only applies to jobs originally submitted with `limit`. If a job was submitted without `limit`, there is nothing to continue. The new_limit must be greater than the previous limit when provided. If omitted, API defaults to your plan maximum.

  ConnectorNo auth

• continue_jobA

  CatchAllB

  Expand a job by processing more records beyond the initial limit. This increases the number of records the system processes (which costs additional credits). Only use this when the user wants MORE data processed. This only applies to jobs originally submitted with `limit`. If a job was submitted without `limit`, there is nothing to continue. The new_limit must be greater than the previous limit when provided. If omitted, API defaults to your plan maximum.

  ConnectorNo auth

• get_process_mapA

  Enhanciar — company brainA

  Map how the company works: procedures, the tools they use, their docs. Use it for the big picture ("which processes touch Jira?", "what do we run through Slack?"); for the steps of one procedure use ``get_skill``, and for the topic graph use ``get_graph``. It takes no arguments and rebuilds the map from the compiled skills on each call. Returns ``{nodes, edges}``: nodes have ``{id, label, kind}`` with kind process, system, doc or team, and edges have ``{from, to, rel}`` with rel such as derived_from, uses or references. With no skills compiled the lists are empty and a ``message`` says why.

  ConnectorAPI key

• get_management_key_activityA

  past.devA

  What the organization's management key called in the last 30 days: each route with its method, call count and last call, busiest first; a route nobody called is absent. Mirrors Settings › Management key › Recent activity; needs Owner or Admin.

  ConnectorOAuth

• strategic-mindsetA

  ClairvoyanceA

  Assesses whether code reflects strategic or tactical thinking, including the 10-20% investment rule and tactical-tornado patterns. Use when evaluating design investment, when code was written under time pressure, or when working code consistently degrades the system. Not for judging whether a specific diff looks designed-in or bolted-on (use code-evolution).

  ConnectorNo auth

• awareness_get_agent_promptA

  Awareness — Memory, Knowledge & Agent MarketsA

  Fetch the full activation prompt for a specific agent role (sub-agent spawning). Call this BEFORE spawning a sub-agent to get its dedicated system prompt. Use the returned activation_prompt as the sub-agent's system prompt so that the main agent context stays clean and each sub-agent has an isolated, focused prompt. Typical usage: 1. awareness_init returns agent_profiles with slim summaries (agent_role, title, when_to_use). 2. When a task matches a role, call awareness_get_agent_prompt(agent_role="<role>"). 3. Spawn a sub-agent with the returned activation_prompt as its system prompt. 4. The sub-agent passes agent_role="<role>" to all awareness_* calls for memory isolation. Args: agent_role: The agent role to fetch (e.g. "developer_agent", "reviewer_agent"). memory_id: Target memory id (auto-read from X-Awareness-Memory-Id header if omitted). api_key: Bearer token for authentication.

  ConnectorNo auth

• assign_taskA

  OnplanaB

  Assign or unassign one task. Pass assigneeId=null to unassign. Alternatively pass assigneeEmail to resolve by org-member email (useful when the agent only knows the user's email and would otherwise need a separate list to find their id). Mutually exclusive with assigneeId. Optional expectedAssigneeRevision (integer): if supplied, the call fails with a CONFLICT error when another caller has assigned the task since you last read it. Returns the assignee's id and name (assigneeName), and the new claimRevision so you can chain consecutive assigns under optimistic concurrency. Caller must have task.assign on the project. Target must be an active member of the organization. On plans with resource management the result also carries `load`: the assignee's capacity for the week the task lands in, the hours already committed to their other open work, this task's share, whether that projection exceeds capacity (`over`, `overBy`), and the competing work that week (`otherWork`). Null when the task has no dates.

  Connector

  Destructive

  OAuth

• compile_xml_agent_promptA

  Diogenes Autonomous Microservice GatewayA

  Compiles a raw task description into a structured XML system prompt (<role>, <context>, <objective>, <constraints>, <workflow>, <output_format>) engineered to prevent instruction drift. Use when authoring or upgrading a system prompt for an autonomous agent or sub-agent workflow; for mapping a task objective to a concrete sequence of MCP tool calls, use route_mcp_workflow_plan instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'task' ('prompt_style' defaults to 'anthropic_xml_tags'), supports '?demo=true' or L402 (100 sats), and returns HTTP 400 if invalid.

  ConnectorNo auth

• compile_xml_agent_promptA

  Diogenes Dev & Data Utilities MCPA

  Compiles a raw task description into a structured XML system prompt (<role>, <context>, <objective>, <constraints>, <workflow>, <output_format>) engineered to prevent instruction drift. Use when authoring or upgrading a system prompt for an autonomous agent or sub-agent workflow; for mapping a task objective to a concrete sequence of MCP tool calls, use route_mcp_workflow_plan instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'task' ('prompt_style' defaults to 'anthropic_xml_tags'), supports '?demo=true' or L402 (100 sats), and returns HTTP 400 if invalid.

  ConnectorNo auth

• citation_enhanced_citation_lookupA

  CourtListenerB

  Enhanced citation lookup combining citeurl parsing with CourtListener data. This tool first uses citeurl to parse and validate the citation format, then optionally queries the CourtListener API for additional case information.

  ConnectorNo auth

• listClarityProcessesA

  Duvo MCPB

  List Clarity processes for the current team, most recently updated first. Returns lightweight metadata (capture counts, contributors, status) suitable for building a picker; the per-process read model is available via `GET /v2/teams/:team_id/clarity-v2/processes/:process_id` for v2 rows and `GET /v2/teams/:team_id/clarity/processes/:id` for legacy v1 rows. Both v1 (legacy) and v2 processes are returned by default; use `search`, `status`, and `version` to narrow discovery. Capped at 100 per page.

  ConnectorNo auth

• map_business_processA

  ALM X++ MCP ServerA

  WHEN: mapping the technical D365 objects behind a business process, or understanding which tables/forms implement a flow. Triggers: 'processus métier', 'Order-to-Cash', 'Procure-to-Pay', 'Record-to-Report', 'business process flow', 'qui est impliqué dans', 'map the process', 'flux du processus', 'quels objets dans le flux'. Map a D365 F&O business process to its complete object chain. For known processes (Order-to-Cash, Procure-to-Pay, Record-to-Report, Plan-to-Produce, Inventory-Management, Hire-to-Retire, Project-Accounting, Asset-Lifecycle): shows every step with forms, tables, classes, entities, reports, and security roles involved. For any other object name: traces all dependencies (tables, classes, forms, entities) from that entry point. Produces a Mermaid process flow diagram. Use 'list' to see all known process mappings. NOT for a single object's FK relations only -- use `find_related_objects` for that (faster and more precise).

  ConnectorNo auth

• searchA

  MaplithA

  Start with the task: find the affected objects here, then read their applicable rules with get_object before acting. Search objects and fields, findings, processes, metrics and decision statements, case-insensitively. Decision matches include the rule text, kind, visible anchors, source record, statement status and record status. Rule-text matches rank before citation-only matches; results share a 50-document budget across kinds, with true per-kind counts and truncated when more match. Pass a result id to fetch for full detail, including statement:<id> for a rule in this run. Use get_object for all rules applicable to an affected object; search is discovery, not a complete task context. Relations are not searched: use get_object or route. Use ask for an explanation. Full matching and scope semantics: maplith://docs/mcp.

  ConnectorOAuth