Model Context FAQs

Question 1

How can I add support for new data sources or services?

Accepted Answer

Model Context is highly extensible. To add new data sources or services, developers can create a new service package, implement the `protocol.ToolCaller` interface, and register the controller. The server automatically discovers and exposes these new tools.

Question 2

Can I integrate Model Context with my development environment?

Accepted Answer

Yes, Model Context is designed for simplified integration with development environments like VSCode, providing clear configuration examples for connecting via both stdio and HTTP transports.

Question 3

How does Model Context communicate with clients?

Accepted Answer

It supports two primary communication transports: stdio (standard input/output), which is the default, and HTTP using the JSON-RPC 2.0 specification, typically accessed via a `/mcp` endpoint.

Question 4

What is Model Context (MCP Server)?

Accepted Answer

Model Context, also known as MCP Server, is an extensible server implementing the Model Context Protocol (MCP) for diverse data operations. It currently provides robust, built-in integration for MongoDB.

Question 5

What databases does Model Context support?

Accepted Answer

Model Context currently offers comprehensive support for MongoDB operations. Its extensible architecture is designed to easily integrate and manage other data sources like PostgreSQL, Redis, or custom services.

Model Context

Model Context

Características Principales

Casos de Uso

Características Principales

Casos de Uso