Skip to main content

​
Introduction

Talqui exposes a remote MCP (Model Context Protocol) server that lets AI assistants work with your workspaces using the tools of the plugins installed in each one. You only paste the server URL into your assistant. There is no API key to create or copy: the assistant registers itself and you sign in with your Talqui account in the browser.
Only workspace owners and managers can authorize an app. Operators cannot authorize apps yet.

​
Claude Code

Add the server:
Then run /mcp inside Claude Code, select talqui and choose Authenticate. Your browser opens to finish the authorization.

​
Claude (claude.ai and desktop)

  1. Open Settings → Connectors.
  2. Click Add custom connector.
  3. Paste https://mcp.talqui.chat/mcp and confirm.
  4. Click Connect. Your browser opens to finish the authorization.

​
Cursor

Add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
Then open Cursor Settings → MCP, find talqui and click Login (or Needs login). Your browser opens to finish the authorization and returns to Cursor.

​
Other MCP clients

Any client that supports remote MCP servers with OAuth can connect: add a remote (HTTP) server with the URL https://mcp.talqui.chat/mcp with no API key. The client discovers the OAuth configuration and registers itself. Check your client’s documentation for where remote servers are configured.

​
Authorization flow

  1. Your browser opens the Talqui login (app.talqui.chat). Sign in if you are not already signed in.
  2. The consent screen shows the name of the app and the host it redirects to, with an unverified app warning. Check that they match the assistant you are connecting.
  3. Select the workspaces the app may use.
  4. Click Authorize. The assistant is now connected.
Only authorize apps you trust. The app acts with your permissions in the workspaces you select.

​
Using Talqui in the assistant

  • The list_workspaces tool lists the workspaces you authorized, with their id, name and your role.
  • Every other tool takes a workspace_id. When you have more than one workspace, tell the assistant which one to use.
  • The tools available are the ones of the plugins installed in that workspace.

​
Session and expiration

  • The access token lasts 1 hour and is refreshed automatically.
  • The connection stays valid as long as it is used at least once every 15 days. After that, the assistant asks you to sign in again.
  • Signing out of the Talqui web app, ending a session in Settings → Active sessions or changing your password does not disconnect the app. To disconnect it, revoke it.
  • Resetting a forgotten password disconnects every connected app, in case someone else had access to your account. Connect them again afterwards.

​
Revoking access

In the Talqui web app, open Settings → Connected apps (Apps conectados) and click Revoke (Revogar) next to the app. The app loses access within about a minute. Access is also removed automatically when you lose the owner or manager role in a workspace: the app stops reaching that workspace within about a minute.