mistral_get_agent — Mistral MCP by usefulapi MCP Tool
mistral_get_agent
(mistral get agent) is one of 15 tools on the
Mistral MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mistral_get_agent from your client
- Claude Code Mistral MCP by usefulapi mistral_get_agent run in your project directory
- Claude Desktop Mistral MCP by usefulapi mistral_get_agent ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mistral MCP by usefulapi mistral_get_agent ~/.cursor/mcp.json
- VS Code Mistral MCP by usefulapi mistral_get_agent .vscode/mcp.json
- Zed Mistral MCP by usefulapi mistral_get_agent ~/.config/zed/settings.json
- Windsurf Mistral MCP by usefulapi mistral_get_agent ~/.codeium/windsurf/mcp_config.json
- Cline Mistral MCP by usefulapi mistral_get_agent ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mistral MCP by usefulapi mistral_get_agent ~/.gemini/settings.json
- Grok Mistral MCP by usefulapi mistral_get_agent .mcp.json (in your project root)
- ChatGPT Mistral MCP by usefulapi mistral_get_agent Settings → Connectors → Advanced → Developer mode
- Claude.ai Mistral MCP by usefulapi mistral_get_agent Settings → Connectors → Add custom connector
- LangChain Mistral MCP by usefulapi mistral_get_agent pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mistral https://mistral.usefulapi.io/mcpOther tools on this server
- mistral_list_models
- mistral_get_model
- mistral_list_files
- mistral_get_file
- mistral_get_file_url
- mistral_list_batch_jobs
- mistral_get_batch_job
- mistral_list_agents
- mistral_list_libraries
- mistral_get_library
- mistral_list_library_documents
- mistral_create_agent
- mistral_cancel_batch_job
- mistral_delete_file
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.