W
w1991e/sess-sdk
Ask a person a question from your server and continue with their verified answer.
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
w1991e/sess-sdk;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Sess SDK
Excerpted from the repository README (abridged)
Ask a person a question from your server and continue with their verified answer.
Create and run a small agent:
sh
npm create @sess.si/agent@latest my-agent
What you'll see: a Sess link. Answer two questions on your phone and your plan prints in the
terminal with a verified receipt.
Install the SDK in your own server project:
sh
npm install --save-exact @sess.si/sdk@0.4.0
## Ask a person
Use a developer API key from the Sess developer portal. Keep it on the server.
The hosted no-signup demo is a separate trial flow; a Sess link or trial credential
is not an owner API key. You need no LLM, agent framework, Docker or Sess source checkout.
ts
import { Sess } from '@sess.si/sdk';
const sess = new Sess({ apiKey: process.env.SESS_API_KEY });
const question = await sess.ask({
question: 'Approve the synthetic refund?',
fields: [
{ name: 'approved', label: 'Approve it', type: 'boolean' },
{ name: 'amount', label: 'Refund amount', type: 'number', minimum: 0 },
],
});
console.log(Send this Sess link to the person: ${question.link});
const { approved, amount } = await question.answer(); // verified; the Session is now complete
if (approved) console.log(Refund of ${amount.toFixed(2)} approved.);
sess.ask() checks the question locally, creates the Session once and returns its Sess link
before anything waits. The link is a bearer capability: deliver it only to the person, never to
logs or analytics. answer() waits for the person (ten minutes by default), verifies the signed
receipt against the exact question, checks that the answer is still the current step, completes the
Session and returns the values typed from your fields. Completion closes the Session: the link no
longer accepts answers. Field types are text, number, integer, boolean, choice,
multi_choice and rating (API reference).
If the wait times out (wait_ended, code WAIT_TIMEOUT) or you abort it, nothing changes remotely:
call answer() again on the same handle. An error with outcome: "unknown" means completion is not
confirmed; calling answer() again replays the same completion. The handle lives in memory only. To
resume after a restart, persist sessionId and revision and continue with the API below
(Integration).
If Sess refuses a call, the error says what happened and what to do. A key Sess does not accept
prints: "Sess did not accept your API key. Check SESS_API_KEY and the portal you made it on." The
message comes first; the code and request ID follow it:
js
try {
const question = await sess.ask({
question: 'Approve the synthetic refund?',
fields: [{ name: 'approved', label: 'Approve it', type: 'boolean' }],
});
console.log(Send this Sess link to the person: ${question.link});
} catch (error) {
console.error(error.message); // what happened and what to do
const request = error.requestId ? , request ${error.requestId} : '';
console.error(Details: ${error.code ?? error.kind}${request});
process.exitCode = 1;
## Keep it short
A person reads the page on a phone, so Sess keeps every piece of it short. Lengths count
characters (Unicode code points), and Sess never truncates:
| What | Style | At most |
| Title (question) | A question or a task, about 40 | 80 |
| Button (submit_label) | A verb, 1–3 words | 24 |
Create and run a small agent:
sh
npm create @sess.si/agent@latest my-agent
What you'll see: a Sess link. Answer two questions on your phone and your plan prints in the
terminal with a verified receipt.
Install the SDK in your own server project:
sh
npm install --save-exact @sess.si/sdk@0.4.0
## Ask a person
Use a developer API key from the Sess developer portal. Keep it on the server.
The hosted no-signup demo is a separate trial flow; a Sess link or trial credential
is not an owner API key. You need no LLM, agent framework, Docker or Sess source checkout.
ts
import { Sess } from '@sess.si/sdk';
const sess = new Sess({ apiKey: process.env.SESS_API_KEY });
const question = await sess.ask({
question: 'Approve the synthetic refund?',
fields: [
{ name: 'approved', label: 'Approve it', type: 'boolean' },
{ name: 'amount', label: 'Refund amount', type: 'number', minimum: 0 },
],
});
console.log(Send this Sess link to the person: ${question.link});
const { approved, amount } = await question.answer(); // verified; the Session is now complete
if (approved) console.log(Refund of ${amount.toFixed(2)} approved.);
sess.ask() checks the question locally, creates the Session once and returns its Sess link
before anything waits. The link is a bearer capability: deliver it only to the person, never to
logs or analytics. answer() waits for the person (ten minutes by default), verifies the signed
receipt against the exact question, checks that the answer is still the current step, completes the
Session and returns the values typed from your fields. Completion closes the Session: the link no
longer accepts answers. Field types are text, number, integer, boolean, choice,
multi_choice and rating (API reference).
If the wait times out (wait_ended, code WAIT_TIMEOUT) or you abort it, nothing changes remotely:
call answer() again on the same handle. An error with outcome: "unknown" means completion is not
confirmed; calling answer() again replays the same completion. The handle lives in memory only. To
resume after a restart, persist sessionId and revision and continue with the API below
(Integration).
If Sess refuses a call, the error says what happened and what to do. A key Sess does not accept
prints: "Sess did not accept your API key. Check SESS_API_KEY and the portal you made it on." The
message comes first; the code and request ID follow it:
js
try {
const question = await sess.ask({
question: 'Approve the synthetic refund?',
fields: [{ name: 'approved', label: 'Approve it', type: 'boolean' }],
});
console.log(Send this Sess link to the person: ${question.link});
} catch (error) {
console.error(error.message); // what happened and what to do
const request = error.requestId ? , request ${error.requestId} : '';
console.error(Details: ${error.code ?? error.kind}${request});
process.exitCode = 1;
## Keep it short
A person reads the page on a phone, so Sess keeps every piece of it short. Lengths count
characters (Unicode code points), and Sess never truncates:
| What | Style | At most |
| Title (question) | A question or a task, about 40 | 80 |
| Button (submit_label) | A verb, 1–3 words | 24 |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/w1991e-sess-sdk-tree-master-adapters-mcp/)
- Source
- awesome · https://github.com/w1991e/sess-sdk/tree/master/adapters/mcp
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.