Skip to content

Cursor mcp describe_tool_input

How to: Cursor mcp describe_tool_input

client:Cursor transport:streamable-http tool:describe_tool_input

Add mcp to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.apideck.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something describe_tool_input does. Cursor lists the server's tools on connect and calls describe_tool_input itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that mcp's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

mcp will not start until these are set, so describe_tool_input never becomes available.

  • APIDECK_API_KEY
  • APIDECK_APP_ID
  • APIDECK_CONSUMER_ID

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.