Do I need to install anything to use Elicitly?

Yes. Elicitly runs as a local process, so the package has to be installed on the machine where the client runs.

How do I install Elicitly?

Install the npm package elicitly and run it with npx -y elicitly.

Does Elicitly need an API key?

No credentials are declared in the registry entry for Elicitly. Check the source repository before assuming it runs without configuration.

Which transport does Elicitly use?

Stdio. Your client has to support that transport to connect.

Where is the source code for Elicitly?

The publisher lists https://github.com/elicitly/elicitly as the source repository.

Is Elicitly an official server?

It is published under the namespace ai.elicitly, which means the publisher proved control of that domain when registering. That confirms who published it, not that it has been reviewed for quality or security.

Which version of Elicitly is listed here?

Version 0.7.2, taken from the latest registry entry.

Elicitly MCP server

Name: Elicitly
Author: elicitly

Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor.

Install this server Visit publisher site View source

74/100?Number 42 of 661 in Research and Reference

verified publishersource repositorytool list publishedupdated recentlyactive entryno credentials

How this score is calculated

Local VERIFIED Research and Reference

Details

Registry name: ai.elicitly/elicitly
Publisher: elicitly
Version: 0.7.2
Distribution: Local. the server runs as a process on your own machine and talks to the client over stdio. You install the package first, and your data stays on your machine.
Transports: stdio
Source repository: elicitly/elicitly
Website: https://www.elicitly.ai
First published: 2026-09-07
Registry updated: 2026-09-07
Credentials required: None declared
Schema generation: 2025-12-11

Packages

npm elicitly

Version: 0.7.2
Transport: stdio
Runtime: not specified

Install Elicitly

Pick your client. The configuration below is generated from this server's published package and endpoint data.

Claude Code command line

Configuration file: .mcp.json or ~/.claude.json

Local package (npm)

claude mcp add elicitly -- npx -y elicitly

Check it worked: Run claude mcp list and check the server reports connected.

Official Claude Code MCP documentation

Cursor IDE

Configuration file: .cursor/mcp.json or ~/.cursor/mcp.json

Local package (npm)

{
  "mcpServers": {
    "elicitly": {
      "command": "npx",
      "args": ["-y", "elicitly"]
    }
  }
}

Check it worked: The server appears under Settings, then MCP with a green dot.

Official Cursor MCP documentation

Claude Desktop desktop app

Configuration file: ~/Library/Application Support/Claude/claude_desktop_config.json or %APPDATA%\Claude\claude_desktop_config.json

Local package (npm)

{
  "mcpServers": {
    "elicitly": {
      "command": "npx",
      "args": ["-y", "elicitly"]
    }
  }
}

Quit the app completely and reopen it.

Check it worked: Look for the tools icon in the message composer.

Official Claude Desktop MCP documentation

Visual Studio Code IDE

Configuration file: .vscode/mcp.json or user settings.json under mcp

Local package (npm)

{
  "servers": {
    "elicitly": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "elicitly"]
    }
  }
}

Check it worked: Open the Copilot chat tools picker and confirm the server is listed.

Official Visual Studio Code MCP documentation

Codex CLI command line

Configuration file: ~/.codex/config.toml

Local package (npm)

codex mcp add elicitly -- npx -y elicitly

Check it worked: Run codex mcp list and check the server is present.

Official Codex CLI MCP documentation

More clients (9), including automation platforms

Cline IDE

Configuration file: cline_mcp_settings.json, reachable from the MCP Servers pane

Local package (npm)

{
  "mcpServers": {
    "elicitly": {
      "command": "npx",
      "args": ["-y", "elicitly"]
    }
  }
}

Check it worked: The server appears in the MCP Servers pane with its tool count.

Official Cline MCP documentation

Goose desktop app

Configuration file: ~/.config/goose/config.yaml

Local package (npm)

extensions:
  elicitly:
    type: stdio
    cmd: npx
    args: ["-y", "elicitly"]
    enabled: true

Check it worked: Run goose session and confirm the extension loads.

Official Goose MCP documentation

LangChain agent framework

Install the MCP adapter package and construct a client in code

Local package (npm)

client = MultiServerMCPClient({
    "elicitly": {
        "command": "npx",
        "args": ["-y", "elicitly"],
        "transport": "stdio",
    }
})

Check it worked: Print the loaded tool list before running the agent.

Official LangChain MCP documentation

Windsurf IDE

Configuration file: ~/.codeium/windsurf/mcp_config.json

Local package (npm)

{
  "mcpServers": {
    "elicitly": {
      "command": "npx",
      "args": ["-y", "elicitly"]
    }
  }
}

Check it worked: The server appears in the Cascade plugin list.

Official Windsurf MCP documentation

Zed IDE

Configuration file: ~/.config/zed/settings.json

Local package (npm)

{
  "context_servers": {
    "elicitly": {
      "command": {
        "path": "npx",
        "args": ["-y", "elicitly"]
      }
    }
  }
}

Check it worked: The agent panel lists the server under context servers.

Official Zed MCP documentation

Tools

12 tools, from the publisher's manifest. A parameter marked with an asterisk is required. By intent: 5 answer, 2 act and 5 not classified.

Intent says what a tool does with the world. Answer reads and returns information and changes nothing. Act changes state somewhere, by writing, creating, sending or deleting. Transact moves money, buys something or commits to a cost. A value marked declared is the publisher's own annotation on their own tool. A value marked inferred is this catalogue reading the tool name and description, and is not a claim by the publisher. Where neither settles it, the tool is left unclassified rather than guessed at.

Tool	What it does	Intent	Parameters
elicit_approval	Request human approval before proceeding. Async: returns immediately with a pending request that a human decides later on the hosted review page (block with `elicit_await`, fetch the outcome with `elicit_result`); for a synchronous in-session form answered by the connected host, use `elicit_form` instead. Two modes, at least one of `context` / `requestedSchema` is required: (1) json mode — pass `context`, a read-only payload the reviewer approves or declines as-is; optionally also pass `displayTemplate`, a LiquidJS template that customizes how `context` is rendered on the review page (instead of the default raw JSON view); (2) form mode — pass `requestedSchema`, a JSON Schema restricted to the MCP elicitation requestedSchema subset (MCP 2025-11-25): a flat object whose properties are strings, numbers/integers, booleans, or single/multi-select enums (no nested objects, arrays of objects, $ref, or allOf) — the reviewer fills in these fields on the review page and submits them back as the submitted data. Both may be passed together: `context` (optionally rendered via `displayTemplate`) is then displayed as read-only context above the form (it is NOT merged into or used to pre-fill the form fields, which are seeded only from `requestedSchema` defaults). Per the MCP elicitation spec, form mode MUST NOT be used to request secrets, credentials, or other sensitive information from the reviewer.	not classified	labels, context, message, displayTemplate, requestedSchema, expiresInSeconds
elicit_await	Long-poll for a decision on a pending elicitation: blocks until the request is submitted, declined, canceled, or expired — or until the server's polling window closes. Returns `{ status }` (pending \| submitted \| declined \| canceled \| expired \| consumed); a `pending` return means the window elapsed, so call again to keep waiting. Prefer this over polling `elicit_status` in a loop.	not classified	elicitationId
elicit_confirm	Ask the user an OK/Cancel confirmation via elicitation (convenience wrapper over elicit_form), modeled on JavaScript's confirm(). Use this for a single yes/no question; use elicit_form to collect arbitrary fields. Returns three-state {confirmed}: true = proceed, false = a human explicitly said no, null = no answer was obtained (reason: "dismissed" \| "error") — ask again later.	not classified	labels, message, timeoutSeconds
elicit_doctor	Report the connected host's elicitation/sampling/roots support. initialize.request/response echo the handshake verbatim; support holds Elicitly's derived booleans; deprecations flags client features (sampling, roots, logging) moved to Deprecated in the MCP 2026-07-28 spec (SEP-2577); probeElicitation adds a live form-elicitation round-trip under probes.elicitationForm. Client-features background: https://modelcontextprotocol.io/docs/learn/client-concepts. Pass share: true to contribute the report to Elicitly's public Support Matrix evidence queue — stored: this report plus the optional productName / productVersion / notes (the host product's name and version, which the report cannot see from inside, and any unusual setup); the report itself contains no elicitation payloads or conversation content. The result then carries shared: true\|false.	answer inferred	notes, share, productName, productVersion, probeElicitation
elicit_form	Trigger a form elicitation with a caller-supplied JSON schema; returns the raw {action, content}. For a plain OK/Cancel question, prefer elicit_confirm. MUST NOT be used to request secrets, credentials, or other sensitive information.	act inferred	message, timeoutSeconds, requestedSchema
elicit_history	List your past elicitations, newest first, paginated with jump-to-page. `scope` 'me' = your own requests; 'org' = the whole organization (admins only). Returns `{ items, page, pageSize, asOf, total, scope }` — `total` lets you compute the last page (ceil(total/pageSize)); pass the returned `asOf` back on later pages to keep the window stable while new requests arrive.	answer inferred	asOf, page, scope, pageSize
elicit_ping	Connectivity check for the hosted Elicitly server: echoes `message` back as `pong: <message>` over the authenticated session.	answer inferred	message
elicit_proposal	Ask a human to review, edit, and selectively approve a proposed record create-or-update, shown as a diff grid: one or more read-only Source columns, a read-only Current column, and an editable Proposed column. Async like elicit_approval: returns a pending request decided on the hosted review page. Pass `requestedSchema` (a JSON Schema in the MCP elicitation requestedSchema subset — flat object of strings/numbers/booleans/enums) to define the editable Proposed fields; each property's `default` is its initial proposed value (you compute it — e.g. take Current if present else Source). Pass `columns` to name the Source column(s) and the Current column, and `fields` to supply each property's Source value(s) and Current value. The reviewer edits proposed values, chooses which fields to include, and submits; the result (via elicit_result) carries `decision` (submitted\|declined) and, on submit, `values` (included fields only). MUST NOT be used to request secrets or credentials.	not classified	fields, labels, columns, context, message, displayTemplate, requestedSchema, expiresInSeconds
elicit_result	Fetch the outcome of a decided request (poll `elicit_status` or block on `elicit_await` first — this errors while the request is still pending, after it expires undecided, or if it was canceled via `elicit_cancel`; repeatable reads are fine afterward). Returns `{ status: 'consumed', decision, context, formSubmission }` plus per-tool overlays: `elicit_selection` adds `selectedIds` (the chosen option ids); `elicit_proposal` adds, on submit, `values` (only the fields the reviewer included).	answer inferred	elicitationId
elicit_selection	Ask a human to choose one or more options from a caller-supplied list (disambiguation, record matching, picking work items). Async like elicit_approval: returns a pending request decided on the hosted review page; the chosen option ids come back via elicit_result as `selectedIds`. Options render as rows of a table the Liquid templates and `css` can customize. Defaults to single-select — raise `maxSelections` for multi-select.	not classified	css, labels, message, options, rowTemplate, hoverTemplate, maxSelections, minSelections
elicit_status	Non-blocking status check for an elicitation you created: returns `{ status }` — pending \| submitted \| declined \| canceled \| expired \| consumed. Read-only and repeatable (never consumes the result); use `elicit_await` to block on a decision and `elicit_result` to fetch the outcome.	answer inferred	elicitationId
elicit_cancel	Withdraw a pending elicitation you created — the plan changed or the request is superseded. The request resolves `canceled`: a terminal status distinct from `declined` (the reviewer's explicit no) and `expired` (nobody decided in time). The review page stops accepting decisions, pending `elicit_await` calls wake, and `elicit_result` has no outcome to fetch. Errors if the request was already decided or has expired; a cancel racing a concurrent decision loses cleanly to whichever landed first.	act inferred	elicitationId

Tool

What it does

Intent

Parameters

elicit_approval

Request human approval before proceeding. Async: returns immediately with a pending request that a human decides later on the hosted review page (block with `elicit_await`, fetch the outcome with `elicit_result`); for a synchronous in-session form answered by the connected host, use `elicit_form` instead. Two modes, at least one of `context` / `requestedSchema` is required: (1) json mode — pass `context`, a read-only payload the reviewer approves or declines as-is; optionally also pass `displayTemplate`, a LiquidJS template that customizes how `context` is rendered on the review page (instead of the default raw JSON view); (2) form mode — pass `requestedSchema`, a JSON Schema restricted to the MCP elicitation requestedSchema subset (MCP 2025-11-25): a flat object whose properties are strings, numbers/integers, booleans, or single/multi-select enums (no nested objects, arrays of objects, $ref, or allOf) — the reviewer fills in these fields on the review page and submits them back as the submitted data. Both may be passed together: `context` (optionally rendered via `displayTemplate`) is then displayed as read-only context above the form (it is NOT merged into or used to pre-fill the form fields, which are seeded only from `requestedSchema` defaults). Per the MCP elicitation spec, form mode MUST NOT be used to request secrets, credentials, or other sensitive information from the reviewer.

not classified

labels, context, message, displayTemplate, requestedSchema, expiresInSeconds

elicit_await

Long-poll for a decision on a pending elicitation: blocks until the request is submitted, declined, canceled, or expired — or until the server's polling window closes. Returns `{ status }` (pending | submitted | declined | canceled | expired | consumed); a `pending` return means the window elapsed, so call again to keep waiting. Prefer this over polling `elicit_status` in a loop.

not classified

elicitationId

elicit_confirm

Ask the user an OK/Cancel confirmation via elicitation (convenience wrapper over elicit_form), modeled on JavaScript's confirm(). Use this for a single yes/no question; use elicit_form to collect arbitrary fields. Returns three-state {confirmed}: true = proceed, false = a human explicitly said no, null = no answer was obtained (reason: "dismissed" | "error") — ask again later.

not classified

labels, message, timeoutSeconds

elicit_doctor

Report the connected host's elicitation/sampling/roots support. initialize.request/response echo the handshake verbatim; support holds Elicitly's derived booleans; deprecations flags client features (sampling, roots, logging) moved to Deprecated in the MCP 2026-07-28 spec (SEP-2577); probeElicitation adds a live form-elicitation round-trip under probes.elicitationForm. Client-features background: https://modelcontextprotocol.io/docs/learn/client-concepts. Pass share: true to contribute the report to Elicitly's public Support Matrix evidence queue — stored: this report plus the optional productName / productVersion / notes (the host product's name and version, which the report cannot see from inside, and any unusual setup); the report itself contains no elicitation payloads or conversation content. The result then carries shared: true|false.

answer inferred

notes, share, productName, productVersion, probeElicitation

elicit_form

Trigger a form elicitation with a caller-supplied JSON schema; returns the raw {action, content}. For a plain OK/Cancel question, prefer elicit_confirm. MUST NOT be used to request secrets, credentials, or other sensitive information.

act inferred

message, timeoutSeconds, requestedSchema

elicit_history

List your past elicitations, newest first, paginated with jump-to-page. `scope` 'me' = your own requests; 'org' = the whole organization (admins only). Returns `{ items, page, pageSize, asOf, total, scope }` — `total` lets you compute the last page (ceil(total/pageSize)); pass the returned `asOf` back on later pages to keep the window stable while new requests arrive.

answer inferred

asOf, page, scope, pageSize

elicit_ping

Connectivity check for the hosted Elicitly server: echoes `message` back as `pong: <message>` over the authenticated session.

answer inferred

message

elicit_proposal

Ask a human to review, edit, and selectively approve a proposed record create-or-update, shown as a diff grid: one or more read-only Source columns, a read-only Current column, and an editable Proposed column. Async like elicit_approval: returns a pending request decided on the hosted review page. Pass `requestedSchema` (a JSON Schema in the MCP elicitation requestedSchema subset — flat object of strings/numbers/booleans/enums) to define the editable Proposed fields; each property's `default` is its initial proposed value (you compute it — e.g. take Current if present else Source). Pass `columns` to name the Source column(s) and the Current column, and `fields` to supply each property's Source value(s) and Current value. The reviewer edits proposed values, chooses which fields to include, and submits; the result (via elicit_result) carries `decision` (submitted|declined) and, on submit, `values` (included fields only). MUST NOT be used to request secrets or credentials.

not classified

fields, labels, columns, context, message, displayTemplate, requestedSchema, expiresInSeconds

elicit_result

Fetch the outcome of a decided request (poll `elicit_status` or block on `elicit_await` first — this errors while the request is still pending, after it expires undecided, or if it was canceled via `elicit_cancel`; repeatable reads are fine afterward). Returns `{ status: 'consumed', decision, context, formSubmission }` plus per-tool overlays: `elicit_selection` adds `selectedIds` (the chosen option ids); `elicit_proposal` adds, on submit, `values` (only the fields the reviewer included).

answer inferred

elicitationId

elicit_selection

Ask a human to choose one or more options from a caller-supplied list (disambiguation, record matching, picking work items). Async like elicit_approval: returns a pending request decided on the hosted review page; the chosen option ids come back via elicit_result as `selectedIds`. Options render as rows of a table the Liquid templates and `css` can customize. Defaults to single-select — raise `maxSelections` for multi-select.

not classified

css, labels, message, options, rowTemplate, hoverTemplate, maxSelections, minSelections

elicit_status

Non-blocking status check for an elicitation you created: returns `{ status }` — pending | submitted | declined | canceled | expired | consumed. Read-only and repeatable (never consumes the result); use `elicit_await` to block on a decision and `elicit_result` to fetch the outcome.

answer inferred

elicitationId

elicit_cancel

Withdraw a pending elicitation you created — the plan changed or the request is superseded. The request resolves `canceled`: a terminal status distinct from `declined` (the reviewer's explicit no) and `expired` (nobody decided in time). The review page stops accepting decisions, pending `elicit_await` calls wake, and `elicit_result` has no outcome to fetch. Errors if the request was already decided or has expired; a cancel racing a concurrent decision loses cleanly to whichever landed first.

act inferred

elicitationId

Command line alternative

None found. The published package declares no executable and no matching Homebrew formula exists, so the MCP server appears to be the only route. This is a negative result from automated checks, not a statement from the publisher.

Repository signals

Not checked yet. Stars, licence, language and last commit date are read from the source host, and that pass has not run against this record.

Security, privacy and enterprise use

Read from the publisher's own website on 2026-09-09. Links only: nothing here is independently verified.

Policies

Certifications the publisher names

No certification is named on the pages that were read.

Enterprise use

The publisher does not link an enterprise or business page, so enterprise terms could not be determined. Contact them directly.

Publisher

Website: elicitly.ai
Profiles: github
Community: no subreddit linked from the publisher's site

Review platforms

CAPTERRA G2 OMR TRUSTPILOT

Ratings are not shown. G2, Trustpilot and Capterra all prohibit republishing their scores without a licence, and marking up a borrowed rating as our own would breach search engine policy. These are profile links only, and a profile may not exist for every publisher.

Frequently asked questions

What does the Elicitly MCP server do?: Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor.
Do I need to install anything to use Elicitly?: Yes. Elicitly runs as a local process, so the package has to be installed on the machine where the client runs.
How do I install Elicitly?: Install the npm package elicitly and run it with npx -y elicitly.
Does Elicitly need an API key?: No credentials are declared in the registry entry for Elicitly. Check the source repository before assuming it runs without configuration.
Which transport does Elicitly use?: Stdio. Your client has to support that transport to connect.
Where is the source code for Elicitly?: The publisher lists https://github.com/elicitly/elicitly as the source repository.
Is Elicitly an official server?: It is published under the namespace ai.elicitly, which means the publisher proved control of that domain when registering. That confirms who published it, not that it has been reviewed for quality or security.
Which version of Elicitly is listed here?: Version 0.7.2, taken from the latest registry entry.

Related servers
Server	Publisher	Category	Package	Version
NASA Mission & Space News, buy per-query in-session (nasanewswatch) VERIFIEDNASA mission & space news: launches, science, discoveries. Hourly, $0.01/query.	a2awire	Research and Reference	hosted	0.1.0
Scholar Feed Rank CS/AI/ML papers by citations, forecast impact, or code adoption; trace 23.2M citation edges.	YGao2005	Research and Reference	npm	3.20.0
Spatial India VERIFIEDDistrict-level open data for India, Census, NFHS-5, NCRB, RBI and more, joined onto one geography.	spatialindia	Research and Reference	hosted	1.0.0
Signs of AI Writing AI-writing detection (EN/ES) that shows the evidence: named tells, hidden characters, citations.	peopleworks	Research and Reference	nuget	0.7.1
BrowseAI Dev Evidence-backed web research for AI agents with citations and confidence scores.	BrowseAI-HQ	Research and Reference	npm	0.4.0
slashyear, sourced history VERIFIEDSourced history: 85,753 dated events, each quoted from a citable Wikipedia revision id.	slashyear	Research and Reference	hosted	1.0.0
Finology Verified Engine VERIFIEDKeyed federal student-loan answers, each logged and citation-stamped. Keyless tier: student-loan.	finology	Research and Reference	hosted	0.2.2
Hk Companies Hong Kong Companies Registry open data, company/BR-number search, new registrations & name changes.	pipeworx-io	Research and Reference	hosted	0.1.0

Elicitly MCP server

Details

Packages

npm elicitly

Install Elicitly

Claude Code command line

Cursor IDE

Claude Desktop desktop app

Visual Studio Code IDE

Codex CLI command line

ChatGPT web app

Cline IDE

Goose desktop app

LangChain agent framework

Make automation platform

n8n automation platform

Windsurf IDE

Zapier automation platform

Zed IDE

Tools

Command line alternative

Repository signals

Security, privacy and enterprise use

Policies

Certifications the publisher names

Enterprise use

Publisher

Review platforms

Frequently asked questions

NASA Mission & Space News, buy per-query in-session (nasanewswatch)

Scholar Feed

Spatial India

Signs of AI Writing

BrowseAI Dev

slashyear, sourced history

Finology Verified Engine

Hk Companies

Details

Packages

npm elicitly

Install Elicitly

Claude Code command line

Cursor IDE

Claude Desktop desktop app

Visual Studio Code IDE

Codex CLI command line

ChatGPT web app

Cline IDE

Goose desktop app

LangChain agent framework

Make automation platform

n8n automation platform

Windsurf IDE

Zapier automation platform

Zed IDE

Tools

Command line alternative

Repository signals

Security, privacy and enterprise use

Policies

Certifications the publisher names

Enterprise use

Publisher

Review platforms

Frequently asked questions

Other servers in Research and Reference