📄️ Basics
Let’s use the Neva MCP client to connect to your MCP servers (and others too).
📄️ Tools
In the Basics chapter, we learned how to invoke a simple tool.
📄️ Resources
In the Basics chapter, we learned how to read a resource.
📄️ Prompts
In the Basics chapter, we learned how to get a simple prompt.
📄️ Roots
The Model Context Protocol (MCP) provides a standardized way for clients to expose filesystem “roots” to servers. Roots define the boundaries of where servers can operate within the filesystem, allowing them to understand which directories and files they have access to. Servers can request the list of roots from supporting clients and receive notifications when that list changes.
📄️ Sampling
In MCP, the client is responsible for executing LLM sampling requests initiated by servers.
📄️ Elicitation
This guide explains how a client handles elicitation requests sent by the MCP server.
📄️ HTTP Transport
In addition to stdio, Neva clients support connecting to MCP servers over Streamable HTTP — a bidirectional transport layer suitable for remote servers.
📄️ Tasks
Neva clients support long-running tasks — an extended way to call tools asynchronously with optional TTL-based cancellation and lifecycle management.
📄️ Batch Requests
Neva supports JSON-RPC 2.0 batch requests — a way to send multiple requests to the server in a single round trip and receive all responses at once.