#general
Hi everyone, I want to increase the timeout for the MCP port. Where do I need to adjust this? Thank you very much.
Hi, is there any way to add existing chats to a project?
found a tiny UX bug, a chat deleted from the left panel still shows on the project page until you refresh. raised an issue: #5910
❤️2💪1
Hey, my name is Ikshant shukla. I'd love to work on WhatsApp support for agents (issue #4145). I've read through the existing Slack and MS Teams provider(how both are intergrated) implementations and have a clear picture of what needs to be done. Is it up for grabs?
Hi team,
I am Ricardo, a professional AI / Software Engineer Engineer with over 8 years of experience. I am going to contribute to this product. Please guide me where I can start from.
Thanks.
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!Hi everyone, I want to increase the timeout for the MCP port. Where do I need to adjust this? Thank you very much.
20 replies
Hi! Could you please give more details?
When I connect the tool via the MCP port on my Archestra, the timeout expires after 60 seconds. I need to increase the timeout; how can I do that?
Just to clarify - tool call taking a long time to execute and timing out?
yes
How do I fix this problem?
I'm looking into it
is it self-hosted or remote mcp? If it's self-hosted, which transport it's using - stdio or streamable http?
It is using HTTP
I see. There is no way to set this timeout today. We will provide this setting per server in a next release early next week, does it work for u?
i think it will help me for work because i need increase time when i call tool from archestra to mcp gateway
@user Have there been any results for this yet? I'm waiting for them.
Hi! it will be included in our release 1.3 which is scheduled for next Monday, sorry for the delay
Hi @user! In a version 1.3.1 we released a env var to tweak mcp timeout via
ARCHESTRA_MCP_GATEWAY_TOOL_CALL_TIMEOUT_MS env varIs that option available on the user interface, or do I have to configure it in the terminal when installing a new version? @user
No, it's not in the UI, it's in the environment variable. How do you run archestra?
services:
archestra:
image: archestra/platform:latest
container_name: archestra
ports:
- "9000:9000"
- "3000:3000"
environment:
ARCHESTRA_QUICKSTART: "true"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- archestra-postgres-data:/var/lib/postgresql/data
- archestra-app-data:/app/data
restart: unless-stopped
volumes:
archestra-postgres-data:
archestra-app-data:
i run this
are you using docker or helm chart?
i using docker
Just add
ARCHESTRA_MCP_GATEWAY_TOOL_CALL_TIMEOUT_MS=120000 to the environment, it will increase a timeout twice. Default one is 60000Here is the doc reference - archestra.ai/docs/platform-deployment#…
Make sure you are running latest 1.3.1 version ( you can check it at the bottom of archestra UI)
Let me know if it helped!