find_agent
Search for an agent ID by name. Used to look up an agent's ID when you only know its name, so you can then call ask_agent with the correct ID.
LABSCO SUMMARY
find_agent exists because ids are the thing a model cannot guess and a human never remembers.
Every platform that addresses things by opaque id needs this tool and many skip it, leaving the caller to hard-code ids that break when something is rebuilt. Looking up by name is a small convenience that removes a whole class of brittle configuration. The scope requirement is the operational note: a general Langdock key will not work unless it carries Agent API rights.
What it is
Langdock's endpoint for calling the agents built in their platform. The surface is small because the work happens inside the agent, not in the protocol.
What you get
- find_agent — look up an agent's id by name, so the caller does not need to hold ids
- ask_agent — send a prompt to a workspace agent by id, with earlier turns passed as message history; ask_custom_agent — set up a temporary agent with its own settings for a single query
Requirements
A static API key holding the Agent API scope, in either an Authorization or x-api-key header.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Calling an agent by name
Resolve the name to an id rather than hard-coding one.
02
Reusing agents built elsewhere
Invoke a Langdock agent from whatever client you are already in.
3 tools
Listed in project docs. Your client may show a different list.
ask_agent
Send a prompt to a specific Langdock workspace agent by ID. The agent processes the request using its configured model, instructions and connected integrations. Multi-turn supported via messageHistory.
ask_custom_agent
Configure and query a custom agent on-the-fly — creates a temporary agent with custom settings for a single query, without creating a permanent agent in the workspace.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- A static API key as Authorization: Bearer or an x-api-key header; the key must hold the Agent API scope, and no OAuth is offered for this endpoint
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://api.langdock.com/mcpRequirements
- A static API key as Authorization: Bearer or an x-api-key header; the key must hold the Agent API scope, and no OAuth is offered for this endpoint
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http langdock https://api.langdock.com/mcp \
--header "Authorization: Bearer <YOUR_LANGDOCK_API_KEY>"<YOUR_LANGDOCK_API_KEY> is a Langdock API key that has the Agent API scope. The endpoint offers no OAuth sign-in, and it also accepts the key as an x-api-key header.
Other MCP Clients
OTHER MCP CLIENTS · JSON
{
"mcpServers": {
"langdock": {
"type": "http",
"url": "https://api.langdock.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_LANGDOCK_API_KEY>"
}
}
}
}<YOUR_LANGDOCK_API_KEY> is a Langdock API key that has the Agent API scope. A client that cannot send headers cannot use this endpoint, because it offers no OAuth sign-in.
