Tache in your tools
Same Tache, same memory, from Claude, ChatGPT, your editor or Slack.
MCP server address
https://mcp.tache.me/mcp How it works You need an active Tache account on WhatsApp. The code works once and expires after 10 minutes.
Here is what will happen when you link your assistant, in under a minute.
- 1Paste the address In your assistant's connectors, then Add.
- 2A Tache page opens It shows a code (IA-7K2P-Q9XM): tap Open WhatsApp.
- 3Authorize in WhatsApp The code goes to Tache, which asks for your agreement: tap Authorize.
- 4You're linked Tache shows up in your assistant, with your memory.
Claude On claude.ai and in the Claude app. Custom connectors depend on your plan.
- 1 Settings › ConnectorsAdd custom connector On claude.ai or in the Claude app.
- 2 Name: TacheURL: the address above No OAuth client ID to enter: Claude registers itself.
- 3 ConnectThen confirm on WhatsApp Follow steps 2 and 3 of “How it works”.
- 4 Turn Tache onIn the tools menu Try: “Ask Tache what I have tomorrow”.
ChatGPT Developer mode and connectors depend on your ChatGPT plan.
- 1 Developer modeApps › Advanced settings Settings › Apps & Connectors › Advanced settings, then turn on developer mode.
- 2 Create: TacheAddress above, OAuth Name: Tache. URL: the server address. Authentication: OAuth.
- 3 Sign inThen confirm on WhatsApp Follow steps 2 and 3 of “How it works”.
- 4 Pick TacheIn the tools In a chat, in the developer mode tools.
Claude Code Add --scope project to the command to share the server with the repository.
$ claude mcp add --transport http tache https://mcp.tache.me/mcp > /mcp - 1 Paste the commandIn your terminal The server is added to your Claude Code configuration.
- 2 Type /mcpThen tache › Authenticate The Tache page opens: follow steps 2 and 3 of “How it works”.
Cursor, VS Code Any MCP client that supports the HTTP transport and OAuth works.
Cursor
~/.cursor/mcp.json {
"mcpServers": {
"tache": {
"url": "https://mcp.tache.me/mcp"
}
}
} VS Code
.vscode/mcp.json {
"servers": {
"tache": {
"type": "http",
"url": "https://mcp.tache.me/mcp"
}
}
} Then sign in from the MCP server list and confirm on WhatsApp.
Slack Tache only reads your direct messages, never channels. Reminders and messages from Tache stay on WhatsApp or in the app.
- 1 Write “link Slack”To Tache, on WhatsApp Or in the Tache app.
- 2 Tap Link SlackLink valid for 15 minutes The page shows your first name and the last 2 digits of your number: check them.
- 3 Allow the appIn your Slack workspace A workspace admin may need to approve it.
- 4 Write to TacheApps section of Slack Text, photos, documents, voice notes and buttons. Unlink: uninstall the Tache app.
What the assistant can do Everything Tache does on WhatsApp: emails, calendar, searches, reminders, documents, purchases.
tache_askHands a request to Tache In natural language, 4,000 characters at most. Reply within 40 seconds, otherwise a request_id. tache_get_replyReads a reply in progress By its request_id, kept for 24 hours. Security
- Confirmations on your phone Sending an email, paying or booking waits for your button on WhatsApp or in the app. A “yes” from the assistant confirms nothing.
- Links and files stay with you App connections, vault, memory space, payments and files reach your phone, never the assistant.
- No commands DELETE, STOP or turning memory off happen on WhatsApp or in the app.
- Cut everything Send DISCONNECT ASSISTANTS to Tache: every assistant loses access immediately.
Your requests go through the assistant's provider. Privacy
Technical reference
Paths relative to https://mcp.tache.me
- MCP endpoint
POST https://mcp.tache.me/mcpStateless Streamable HTTP, JSON responses (no SSE)- Protocol
2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05- Authentication
Authorization: BearerWithout a token: 401 and WWW-Authenticate with resource_metadata- Metadata
/.well-known/oauth-protected-resource/mcpRFC 9728, and /.well-known/oauth-authorization-server (RFC 8414)- Registration
POST /oauth/registerRFC 7591, redirect to https, http://localhost or an app scheme- Authorization
/oauth/authorizePKCE S256, resource = the MCP endpoint, scope tache- Tokens
POST /oauth/tokenAccess 1 h, refresh 30 days with rotation; a replay revokes the access- Revocation
POST /oauth/revokeRFC 7009- Limits
20 / min, 3 pendingPer account; your plan's limits apply
A question? Support
Tache