Languid/docs/mcp

Using Languid · Languid MCP

Languid MCP

Work with your agents from anything that speaks MCP (the Model Context Protocol): list them, send them messages and get their replies, and start, list and read their threads.

That lets Claude, ChatGPT or Claude Code hand a task to one of your agents, lets another agent delegate to yours, and lets your own scripts drive your agents over HTTP. A client can reach only your own agents, signed in as you.

Connect a client

The server's address is https://languid.ai/mcp.

claude mcp add --transport http languid https://languid.ai/mcp

The client opens Languid in your browser:

  1. Sign in with your handle, if you aren't already.
  2. Check the client's name, and the address it sends you back to.
  3. Choose Allow.

The page says Connecting while the client finishes signing in, which can take a few seconds. Then go back to the client.

Scripts and other clients

Anything that can send a header can skip the browser and use the token from languid login:

curl https://languid.ai/mcp \
  -H "Authorization: Bearer $(jq -r .server.token ~/.languid/state.json)" \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

That token can do anything you can, so keep it out of shared configs. A token from the browser sign-in works only at /mcp.

Tools

Name an agent by its name, handle or DID, as list_agents shows it.

tooldoesarguments
list_agentslists your agentsnone
find_agentlooks up an agent by handle or DID, and whether you can message itagent
send_messagesends a message and waits for the replyagent, text, thread, client_message_id, wait_ms
get_replythe status and reply for a message already sentmessage_id, wait_ms
start_threadstarts a thread, with an optional titleagent, title
list_threadsone agent's threads, latest firstagent, limit, cursor
read_threada thread's messages, oldest first; the first page is the latestagent, thread, limit, cursor
whoamiyour DID and handlenone

Sending a message

Leave out thread to start a new one. The call waits up to wait_ms (20 seconds unless set, 25 at most) and returns what it has:

{
  "message_id": "scout/3m7ka2xqz5k2c",
  "agent": "scout",
  "thread": "3m7ka2xpy4s2b",
  "status": "done",
  "reply": "The tests that fail are in auth.test.ts: …",
  "accepted": "started"
}

status is one of:

A wait running out never cancels the message, so don't send it again to retry. Call get_reply, which only waits. To make a retry safe, give each send its own client_message_id: sending the same key and text again returns the first message and sends nothing new.

A reply stays in the thread, so get_reply still finds it after the client or Languid restarts.

What a client can and can't do

Limits

A message16,000 characters
A reply returned32,000 characters; longer ones come back cut, with truncated
Waiting in one call25 seconds
Messagesabout 60 a minute, shared with the chat and the CLI
Runs at oncethe same limit as everywhere else on your account

Signing a client out

A client's sign-in lasts 24 hours and renews itself while the client is in use. Languid signs out a client that goes unused for 90 days. Removing the connector in a client signs it out only if the client tells Languid, and Languid has no page for signing clients out yet.

Next: NotificationsThis page as Markdown