---
name: nexplora
description: Work in the user's Nexplora account — their connected apps, MY (CRM, Support, Analytics and the rest), memory, conversations, departments, skills and the tools they built — through the connected Nexplora MCP server. Use it when the user says $nexplora or Nexplora, or asks about their apps, CRM, deals, memory or earlier work.
---

# Nexplora

The user's Nexplora account is connected as the MCP server `nexplora` (https://nexplora.ai/api/mcp). Everything below runs in THEIR account,
with their apps and their approval rules.

## How to work

- Anything in plain words, or work across several apps: call `nexplora` with the request. It does the work and returns the answer and what ran.
- One precise action in any app: `search_actions` (say it naturally, e.g. "list my linear issues"), then `run_action` with its id and args.
- Nothing does it yet: `build_tool` with what the tool should do. Nexplora makes it, checks and tests it, saves it for the user and returns its action_id for `run_action`.
- Something in MY: use that app's own tool below (plain words find the right action; or pass `action` + `args`).
- What Nexplora remembers: `memory_search`. Something new to remember: `memory_save`.
- Earlier work: `sessions_list`, `session_read`, and `session_continue` to pick a Chat up where it stopped.
- A department on a job: `departments_list`, then `department_run`. One of its specialists: `specialists_list`, then `specialist_ask`.
- The user's own models: `models_list`, then `model_ask` for one model, or `council_ask` to put several on one request together (they only think; to act in the apps use `nexplora`).
- Which apps the user has, and whether they're working: `apps_list`.
- Which account and workspace this connection is signed in as: `whoami`.

## Rules

- Any change to the user's apps through `run_action` (and anything that sends, posts, publishes, deploys, spends money or deletes) waits
  for the user's OK in Nexplora: `search_actions` says which with `needs_your_ok`. You get an `approval_id`
  and a link: tell the user to approve it in Nexplora under Approvals, then call `approval_status` with that id. You can never approve it yourself.
- Never say something ran unless the tool result says so. Report names, counts and links from the result.
- If a tool says an app isn't connected, give the user the link it returns; don't work around it.

## MY apps

- `crm` — MY · CRM: your companies, contacts, deals, notes and tasks.
- `support` — MY · Support: your support inbox: conversations, replies, contacts, labels and automations.
- `analytics` — MY · Analytics: your website traffic: visitors, pages, sources, events, funnels and goals.
- `projects` — MY · Projects: your projects, work items, cycles and comments.
- `erp` — MY · ERP: your books: customers, suppliers, items, quotes, orders, invoices and payments.
- `email` — MY · Email: your email marketing: contacts, segments, emails, campaigns and forms.
- `experiments` — MY · Experiments: your feature flags and A/B experiments.
- `social` — MY · Social: your social accounts, scheduled posts, comments and post results.

## All tools

- `nexplora` — Ask Nexplora: Ask Nexplora to do anything in your Nexplora account, in plain words: work in your connected apps, MY (CRM, Support, Analytics, Projects, ERP, Email, Experiments, Social), your memory, skills and the actions you built.
- `build_tool` — Build a tool: Have Nexplora make you a tool for something none of your actions does yet, in plain words ("post every new deal over 10k to #sales", "list my open GitHub issues labelled bug").
- `search_actions` — Find actions: Find precise actions across everything Nexplora can do for you: every connected app, MY (CRM, Support, Analytics and the rest), your own account, and the actions you built.
- `run_action` — Run an action: Run one action by its id from search_actions, with its parameters.
- `approval_status` — Check an approval: Where something waiting for your OK stands.
- `memory_search` — Search memory: Recall what Nexplora remembers about you and your work.
- `memory_save` — Remember something: Save a fact to your Nexplora memory, so Nexplora knows it everywhere you use it.
- `sessions_list` — Your conversations: Your recent Nexplora conversations (Chat and CodeChat): title, when it was last active, and its session_id.
- `session_read` — Read a conversation: The last messages of one of your Nexplora conversations.
- `session_continue` — Continue a conversation: Send a message into one of your Nexplora Chat conversations and get Nexplora's answer, picking up where you left off.
- `skills_list` — Skills: Every Nexplora skill: the ones installed on your account, and the whole certified catalog marked available — ready to use with skill_run, or which app it needs connected first.
- `skill_run` — Use a skill: Have Nexplora use a skill on a task.
- `departments_list` — Departments: Nexplora's departments (marketing, sales, SEO, finance, support, legal and more) and where your own team in each really stands: switched on or not, whether it had any runs this week, and how many task specialists you switched on.
- `department_run` — Run a department: Have one of Nexplora's departments take on an objective (it plans and does the work with your apps).
- `nxd_use_secret` — Use a sealed secret: Make one request that needs a secret you sealed in Nexplora's vault, by its handle (nxd:sec_…).
- `whoami` — Who am I signed in as: Which Nexplora account this connection is signed in as: the account's email and name, the workspace and company it works in, and what this connection was allowed to do.
- `apps_list` — Your apps: Everything you can work in through Nexplora: MY (CRM, Support, Analytics, Projects, ERP, Email, Experiments, Social) and your connected apps, each with whether it's working, how many actions it has and a few of them.
- `specialists_list` — Specialists: Your specialists and board: how many specialists you have, which department teams are working (each run by its head, plus the specialists the operator switched on), the board partners who lead them, and who is in each department (marketing, sales, SEO, finance, support, legal and more).
- `specialist_ask` — Ask a specialist: Put a department's specialist on a request: they plan it and do the work with your apps.
- `models_list` — Your models: The models you can use through Nexplora, by provider (NX, Claude, GPT, Gemini, …) and model, with whether each is ready: NX is included, any other provider is ready once you've added your own key in Nexplora.
- `model_ask` — Ask a model: Ask ONE model you choose (models_list shows the names).
- `council_ask` — Ask the council: Put several of your models on ONE request together, as your Nexplora council does: the lead model assigns roles (planner, researcher, builder, reviewer), they work, one builds the answer and another checks it.

## Workers (only when switched on for the user's account)

- Workers are the user's own hired helpers. When `workers_list` is offered, you can become one: call `worker_start` with its handle, follow the
  `how_to_work` it returns exactly, do the work with Nexplora's tools passing the `run_id`, and end with `worker_finish`.
- In an app that shows slash commands, each of the user's workers is also listed as its own command (named by its handle).
- On an account with workers switched on, departments and specialists are workers: the department and specialist tools only
  point to them. Bring back one of the user's old departments as a worker with `worker_create` and `from_department`; ready-made
  workers are in Nexplora's marketplace.

- `workers_list` — Your workers: each one's name, handle, whether it's on, its level (Light, Standard or Max), its job, the apps it uses and when it runs.
- `worker_run` — Run a worker: Have one of your workers do its job, or a task you give it, on Nexplora with your apps.
- `worker_result` — A worker's run: The result of one of your workers' runs, by run_id: its status, what it did, what waits for your OK, links and tokens used.
- `worker_ask` — Talk to a worker: Talk to one of your workers in plain words, in its own thread in Nexplora: ask what it knows, what it found, have it do something now, or correct how it does its job (a correction becomes its learning, which its next runs follow).
- `worker_create` — Hire a worker: Hire a new worker: a name, its job, and optionally its instructions, apps, level (light, standard or max), finished work, when it runs and its department.
- `worker_update` — Change a worker: Change one of your workers: its name, job, instructions (add one line with add_instruction), apps, finished work, when it runs, department, on/off or level.
- `worker_start` — Run a worker yourself: Run one of your workers yourself, start to finish, with Nexplora as its tools, data, memory and approvals.
- `worker_step` — Record a step: Record one step of a run you started with worker_start: what you did, in which app, and how it ended (done, failed, held or skipped).
- `worker_finish` — Finish a run: Close a run you started with worker_start: the result in plain words with real numbers, links to what you made, what waits for the OK and tokens used.

## Slash commands (in apps that show them)

- `/nexplora` — Ask Nexplora
- `/crm` — MY · CRM
- `/support` — MY · Support
- `/analytics` — MY · Analytics
- `/projects` — MY · Projects
- `/erp` — MY · ERP
- `/email` — MY · Email
- `/experiments` — MY · Experiments
- `/social` — MY · Social
- `/departments` — Call up a department
- `/memory` — What Nexplora remembers
- `/continue` — Continue where I left off
- `/build-tool` — Build a tool
- `/nx` — Ask NX
- `/claude` — Ask Claude
- `/gpt` — Ask OpenAI
- `/gemini` — Ask Gemini
- `/grok` — Ask Grok
- `/deepseek` — Ask DeepSeek
- `/kimi` — Ask Kimi
- `/qwen` — Ask Qwen
- `/groq` — Ask Groq
- `/mistral` — Ask Mistral
- `/cohere` — Ask Cohere
- `/perplexity` — Ask Perplexity
- `/openrouter` — Ask OpenRouter
- `/council` — Ask the council

## If the `nexplora` server isn't connected

- In a compatible app, add Nexplora as an MCP server:

  ```toml
  [mcp_servers.nexplora]
  url = "https://nexplora.ai/api/mcp"
  ```

- Use your app's MCP sign-in flow to authorize Nexplora.
- Anything else: https://nexplora.ai/mcp