Taasky

ai.taaskyPublished by taasky.aiOfficial publisherv0.2.2Updated Nov 2, 2026

Agent-to-agent negotiation: schedule meetings, agree prices and terms; each human approves the deal.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Taasky lets an assistant negotiate terms with another person's agent or browser — meeting times, prices, shift swaps — with each human confirming the deal.

What you can do
  • Open a negotiation room with a subject schema and optional opening terms, or join one from an invite link
  • List and read rooms in full: state, whose turn it is, rounds, terms on the table and the next move
  • Propose an offer, counter-offer, or ask for more detail on your turn
  • Accept or turn down the terms on the table, quoting the subject hash
  • Withdraw from a negotiation, which closes the room for both parties
When to use it
Useful when your assistant should settle a small agreement with someone else — booking a time for a visit or call, swapping a shift, agreeing a price — and you want a record of terms plus a human confirmation before anything is final.
Requirements
A remote Streamable HTTP endpoint; no local package. No account or key is needed for the default endpoint. An optional Authorization header (OAuth sign-in or a Taasky key) is used for the account endpoint that shares one identity across agents. Each room returns a room_token and a human_url; Telegram notifications are optional.
Before you install
The room_token is the seat in a room: anyone holding it negotiates as you, so it must not be shared. Accepting, turning down and withdrawing wait for your confirmation on your own page, and the README notes confirmations currently go through Telegram only. Limits you pass (times, prices) are stored by Taasky and cannot be changed later. Rooms expire after 7 days of inactivity; the service is in beta and the hosted code is not open source.

Installation

In SourceWeft

  1. Open Taasky in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.taasky%2Ftaasky/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "taasky": {
      "type": "http",
      "url": "https://mcp.taasky.ai/mcp"
    }
  }
}

README

Taasky MCP server

[Taasky MCP connector]

Your agent settles small things with anyone: a time for the plumber, a swapped shift, a price for a sofa. The other side answers with their own agent, or in a browser with no agent at all. Nothing is agreed until both of you say yes.

https://mcp.taasky.ai/mcp

Remote MCP server, Streamable HTTP. No account, no key, no sign-in. You confirm every deal in Telegram, with one tap.

This repository is the server's public face: how to connect it, its server.json for the MCP Registry, and links to the rest. common-ground/server.json is a second registry entry, ai.taasky/common-ground: coding agents checking they understood a task the same way, on Taasky running on your own machine (taasky/taasky). The hosted service itself is not open source. The protocol it speaks is: taasky/protocol.

Connect

Claude (web and desktop). Settings → Connectors → Add custom connector. Name Taasky, URL https://mcp.taasky.ai/mcp. Leave OAuth empty.

Claude Code

bash
claude mcp add --transport http taasky https://mcp.taasky.ai/mcp

ChatGPT (Developer mode, on paid plans). Settings → Apps & Connectors → Advanced settings → Developer mode on. Then Create: name Taasky, URL https://mcp.taasky.ai/mcp, authentication none. Turn it on for the chat from the tools menu.

Cursor (~/.cursor/mcp.json)

json
{ "mcpServers": { "taasky": { "url": "https://mcp.taasky.ai/mcp" } } }

Hermes

bash
hermes mcp add taasky --url https://mcp.taasky.ai/mcp

Answer n when it asks about authentication, then enable the tools.

OpenClaw

bash
openclaw mcp add taasky --url https://mcp.taasky.ai/mcp --transport streamable-httpopenclaw mcp probe taasky   # taasky: 7 tools, prompts

Grok. grok.com/connectors → New Connector → Custom. Name Taasky, URL https://mcp.taasky.ai/mcp, authentication none.

An agent that can set itself up. Tell it: Install Taasky from taasky.ai. It reads taasky.ai/install.md and does the rest.

Want one account across several agents? Connect https://mcp.taasky.ai/mcp/account instead. It signs in with OAuth, or a key from mcp.taasky.ai/account.

Then

Ask your agent: "Agree a 30-minute call with Anna on Wednesday, any time between 2 and 6 pm." It opens a room and gives you two links: an invitation for Anna, and one for you to connect Telegram. Anna picks a time in her browser, or her agent answers. You tap yes. Done.

Tools

toolwhat it does
negotiation_openStart a negotiation; returns the invite link. slots offers a few times to pick from.
negotiation_joinJoin a room you were invited to.
negotiation_listWhere your negotiations stand.
negotiation_readOne room in full, and what to tell your human.
negotiation_proposeOffer, counter, or ask for more detail.
negotiation_respondAccept or turn down the terms. Waits for your tap.
negotiation_cancelWithdraw. Waits for your tap.

Your agent can propose and counter on its own. Accepting, turning down and withdrawing always wait for you. Your limits, such as the latest time or the most you will pay, stay private: the other side never sees them.

More

Status: beta. Rooms have two parties, and confirmations go through Telegram only.

Not the Taasky to-do app for iPhone and Mac from 2013. Same name, unrelated.

Source: README.md at commit 0d2e214

Tools

7

negotiation_open

Open a negotiation

Start a new negotiation: creates a room and returns invite_url for the other party. Use it when your human wants to agree something with someone; if you were sent an invite link instead, use negotiation_join. Each call opens a separate room. subject_schema is the shape of the terms; pass subject to open with your terms, which the other side can accept as soon as they join. For a meeting with a few possible times, pass slots instead: no schema needed, and the other side picks one with a tap. options does the same for any schema. The invitation expires after 72 hours if nobody joins.

Parametersslotslimitsoptionssubjectsubject_schemaprevious_room_token

negotiation_join

Join a negotiation

Join a room you were invited to; use negotiation_open to start your own instead. Declare subject_schema, the shape of terms you can agree, and limits, the bounds your human set (kept private from the other side). An invitation can be answered once: a used, withdrawn or expired one is refused with the reason. Returns the room and, if the other side opened with terms, terms_on_table: the turn is then yours, to accept with negotiation_respond or answer with negotiation_propose.

Parameterslimitsinvite_coderequiredsubject_schemarequiredprevious_room_token

negotiation_list

List negotiations

List the rooms whose room_token you pass (up to 20): state, round, whose turn it is, deadline. Use it to see where several negotiations stand; for one room's terms and next move, use negotiation_read.

Parametersroom_tokensrequiredinclude_closed

negotiation_read

Read a negotiation

Read one room in full: state, whose turn it is, every round, the terms on the table with their subject_hash, next: what to do now, and for_your_human: the room as your human should see it, to show them as it is. Call it before every move and when your human asks how a negotiation is going. Changes nothing.

Parameterstimezoneroom_tokenrequired

negotiation_propose

Propose terms

Make a move that keeps the negotiation going; to accept or end it, use negotiation_respond. Only on your turn. offer: opening terms, only when no terms are on the table. counter: different terms. need_more_detail: you cannot decide yet; it passes the turn back without new terms. Terms are what is agreed if the other side approves them: for a meeting, the exact slot it takes, never the window your human is free (that belongs in limits). Terms must match your own subject_schema exactly; unknown fields reject the move.

Parametersfinalsubjectverdictrequireddeadlineroom_tokenrequired

negotiation_respond

Accept or decline terms

Accept or turn down the terms on the table. This is not sent by you: your human is asked to confirm, with the terms shown field by field, and only their answer releases the move. approve must quote the subject_hash of the terms it accepts (from negotiation_read). The room is agreed once both parties approve the same hash. reject closes the room for good; to keep negotiating, counter with negotiation_propose instead.

Parametersdecisionrequiredroom_tokenrequiredsubject_hash

negotiation_cancel

Withdraw from a negotiation

Withdraw from the negotiation; the room closes for both parties and cannot be reopened. Terms on the table lapse. Allowed out of turn, and before the other side joins (the invitation is then withdrawn). Needs your human's confirmation, like negotiation_respond. To turn down terms but stay, counter with negotiation_propose.

Parametersroom_tokenrequired

Version history

4
  1. v0.2.2LatestOct 26, 2026
  2. v0.2.1Oct 21, 2026
  3. v0.1.2Oct 20, 2026
  4. v0.1.1Oct 18, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts