main.js · part 240

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-agent-exec/dist/main.js, part 240. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

${n} "${e}" not found. Available ${s}: ${t.join(", ")}

${(i/1024).toFixed(1)} KB

${i} bytes

Large output has been written to: ${s.filePath} (${t}, ${e} lines)

MCP server identifier to inspect.

Dynamic namespace to inspect, e.g. an MCP server.

Tool name within the server. Requires server to be set.

Tool name within the namespace. Requires namespace to be set.

RE2 regex pattern to search server and tool names (max 256 chars). Optionally combine with server to scope the search.

RE2 regex pattern to search namespace and tool names (max 256 chars). Optionally combine with namespace to scope the search.

${t.slice(0,-1).join(", ")}, or ${t[t.length-1]}

MCP authentication: If an MCP-backed namespace has namespaceStatus "needsAuth", or its tool call fails with an authentication/authorization error, authenticate it by calling ${Ove} through ${r} with empty arguments. Then inspect that namespace again and retry if appropriate.

MCP authentication: If a relevant server has serverStatus "needsAuth", or if an MCP tool call fails with an authentication/authorization error, authenticate it by calling ${Ove} (via ${r}, with empty arguments), then inspect that server again and retry the original request if appropriate. Do not call ${Ove} just because it is listed, and do not repeatedly call it if authentication did not fix the failure.

MCP authentication: If an MCP-backed namespace has namespaceStatus "needsAuth", its tools are unavailable until that MCP integration is authenticated in the Cursor desktop IDE.

MCP authentication: If a server has serverStatus "needsAuth", its tools are not usable in this environment. Ask the user to authenticate that MCP server in the Cursor desktop IDE, then retry.

their names are listed with that namespace in <user_info>, or in the most recent <user_info_catalog_update> block on a later user turn

First-party Cursor tools: the reserved namespace "${eL.jnL}" lists built-in Cursor tools available on demand (${i}). Discover their schemas here, then invoke them via ${r}; they run natively with their own approvals and rendering.

Discover and inspect tools available through dynamic namespaces, e.g. MCP servers.

1. {"namespace":"<id>"}: returns full input schemas and full descriptions for every tool in that namespace.

2. {"namespace":"<id>","toolName":"<name>"}: returns the full schema and full description for one tool.

3. {"pattern":"<regex>"}: searches namespace and tool names across all namespaces using RE2 syntax.

4. {"namespace":"<id>","pattern":"<regex>"}: searches tool names within that namespace.

5. No arguments: returns the full catalog. Prefer a namespace or pattern when possible.

Pattern-search and catalog results shorten long descriptions to 200 characters, ending with "${YX}". Namespace and single-tool lookups always return the complete description, so fetch the tool directly when you need the full text.

The response includes namespaceStatus for MCP-backed namespaces; do not treat namespaces in ${n} states as usable.

Always call this tool to discover a tool's schema before calling it with ${r}.

Discover and inspect MCP tools. There are 5 ways to call this tool. Prefer fetching by server or pattern over listing the full catalog.

1. {"server":"<id>"}: returns full input schemas and full descriptions for every tool on that server. Preferred when you know the server.

2. {"server":"<id>","toolName":"<name>"}: returns the full schema and full description for one tool.

3. {"pattern":"<regex>"}: searches tool and server names across all servers using RE2 syntax.

4. {"server":"<id>","pattern":"<regex>"}: searches tool names on that server using RE2 syntax.

5. No arguments: returns a catalog of all servers with tool names and short descriptions. Use only as a last resort.

Pattern-search and catalog results shorten long descriptions to 200 characters, ending with "${YX}". Server and single-tool lookups always return the complete description, so fetch the tool directly when you need the full text.

The response includes each server's serverStatus; do not treat servers in ${n} states as usable.

Always call this tool to discover a tool's schema before calling it with ${r}.

toolName requires ${t?"namespace":"server"} to be set.

pattern cannot exceed 256 characters.

Invalid regex pattern: ${t}

Invalid regex pattern: ${t}

Invalid regex pattern: ${t}

${s?"Namespace":"MCP server"} "${d.server}" is ${f.serverStatus}.

MCP server

${t} Available tools: ${h.descriptor.tools.map(e=>e.toolName).join(", ")}

Tool "${d.toolName}" is already available directly and is not part of dynamic namespace "${d.server}". Invoke "${d.toolName}" directly instead of using dynamic tool discovery or invocation.

Tool "${d.toolName}" not found in namespace "${d.server}".

MCP tool "${d.toolName}" not found on server "${d.server}".

${t} Available tools: ${h.descriptor.tools.map(e=>e.toolName).join(", ")}

Invalid arguments

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

List available resources from configured MCP servers. Each returned resource will include all standard MCP resource fields plus a 'server' field indicating which server the resource belongs to. MCP resources are _not_ the same as tools, so don't call this function to discover MCP tools.

Optional server identifier to filter resources by. If not provided, resources from all servers will be returned.

Unknown error

Error listing MCP resources: ${t.result.value.error}

List MCP resources rejected: ${t.result.value.reason}

Unknown error

No MCP resources found.