orquestra-mcp-connect

To configure an MCP server connection in Claude Desktop, you must edit the client-specific configuration file to point to the Streamable HTTP endpoint https://api.orquestra.dev/mcp. After updating the configuration file, restart the client to apply the changes.

MCP tools appear missing or incorrectly named when the client configuration file points to the wrong endpoint or uses an invalid naming format. You can troubleshoot this by requesting a tools listing from the server to verify tool availability and confirm correct discovery.

Yes, you can connect the Orquestra MCP endpoint to Cursor and Claude Code by updating their respective client configuration files with the URL https://api.orquestra.dev/mcp. Once configured, you should run a tool listing request to verify successful server access.

The best way to verify MCP server tool availability is to send a tools listing request to the configured endpoint. This connection verification check confirms that the server is correctly connected and that all tools are discoverable by your AI client.

You may need Node.js installed if your specific MCP client configuration relies on npx to bootstrap the server connection. Troubleshooting missing Node.js is a common step when diagnosing failed setups or empty program indexing during initial client configuration.

The Streamable HTTP endpoint https://api.orquestra.dev/mcp is used to establish a direct connection between your AI client and the Orquestra MCP server. It serves as the target URL in client configuration files for Claude Desktop, Cursor, and Claude Code.