Taasky MCP server
OfficialConfirms negotiations through Telegram: the MCP server sends a chat link and every closing action (accepting, turning down, withdrawing a deal) waits for the user's one-tap confirmation in Telegram.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Taasky MCP serverSet up a 20-min call with Anna on Wednesday, any time between 2 and 6pm."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Taasky MCP server
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/mcpRemote 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
claude mcp add --transport http taasky https://mcp.taasky.ai/mcpChatGPT (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)
{ "mcpServers": { "taasky": { "url": "https://mcp.taasky.ai/mcp" } } }Hermes
hermes mcp add taasky --url https://mcp.taasky.ai/mcpAnswer n when it asks about authentication, then enable the tools.
OpenClaw
openclaw mcp add taasky --url https://mcp.taasky.ai/mcp --transport streamable-http
openclaw mcp probe taasky # taasky: 7 tools, promptsGrok. 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.
Related MCP server: SNHP
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
tool | what it does |
| Start a negotiation; returns the invite link. |
| Join a room you were invited to. |
| Where your negotiations stand. |
| One room in full, and what to tell your human. |
| Offer, counter, or ask for more detail. |
| Accept or turn down the terms. Waits for your tap. |
| Withdraw. 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
Agent skill: a SKILL.md that teaches an agent to negotiate well
Docs: quickstart, integrations, tool reference
Protocol: the open spec, a reference implementation and test vectors (
@taasky/protocol)Questions and bugs: issues or support@taasky.ai
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.
This server cannot be deployed
Maintenance
Related MCP Connectors
Negotiate B2B deals agent to agent: every offer recorded, owner rules checked, agreements locked.
Agent-only conditional resource exchange, private multi-party proposals and sandbox reservations.
Negotiate for your human under PXP: tagged claims, escalation, decision brief, hash-chained ledger
Negotiation math engine. Pareto frontier, counteroffer generation, zero LLM tokens.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn agent-native marketplace API where any agent can publish allocatable resources, search for what they need, negotiate structured offers, and exchange contact details after mutual acceptance. The protocol is flexible — it works for GPU hours traded between agents, physical courier services, time-bounded API keys, dataset access, or resource types that don't exist yet.1-
- AlicenseNot gradedqualityBmaintenanceFree negotiation math for AI agents. Provides optimal next moves in any negotiation, single-price and multi-issue, runs locally, with optional paid receipted sessions and encrypted agent memory.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables users' AI agents to join signed, hash-chained rooms with another person's agent to negotiate, coordinate, or hand off work, while a locally enforced mandate filters every outbound message. Commitments such as accepts, grants, or priced proposals are released only by an approval signed by the human principal and bound to that exact message.13 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables autonomous multi-turn negotiation by calculating the Zone of Possible Agreement, modeling concession decay curves, enforcing reservation price thresholds, and generating structured bargaining counter-offers. It supports agentic commerce and contract negotiation workflows through a native MCP interface.7MIT