Mcp SQL Server Reference Documentation

Mcp

Current Version: 11.6.0

Chilkat.Mcp

A client for the Model Context Protocol (MCP).

Chilkat.Mcp connects to an MCP server and gives an application access to the server's tools, resources, and prompts over a single, unified API. MCP is an open protocol that standardizes how applications supply context and callable tools to AI models.

Connect & handshake

Connect opens a Streamable HTTP session and performs the MCP initialize handshake, negotiating the protocol version and establishing a session id.

Tools

List the server's tools with ListTools and invoke them with CallTool.

Resources & prompts

Read resources with ListResources and ReadResource, and fetch prompts with ListPrompts and GetPrompt.

Use with Chilkat.Ai

Pass a connected Chilkat.Mcp to Chilkat.Ai.UseMcp to register the server's tools with an AI model. During a conversation the model's tool calls are routed to the MCP server automatically.

Transport: This class uses the MCP Streamable HTTP transport (protocol version 2025-06-18). A server response may arrive as a single JSON object or as a Server-Sent-Events stream; both are handled transparently. The stdio transport is not supported.
Authentication: If the MCP server requires authorization, set the AuthToken property before calling Connect. Chilkat then sends it as an Authorization: Bearer <token> header on every request. Leave it unset for servers that do not require authentication.
Pagination: When a server has more items than fit in a single response, the tools/list, resources/list, and prompts/list results include a nextCursor string. In this release the list methods return the first page only and do not accept a cursor argument, so nextCursor is informational.

Object Creation

DECLARE @hr int
DECLARE @mcp int
EXEC @hr = sp_OACreate 'Chilkat.Mcp', @mcp OUT
IF @hr <> 0
BEGIN
    PRINT 'Failed to create ActiveX component'
    RETURN
END

-- ... use @mcp ...

EXEC @hr = sp_OADestroy @mcp

T-SQL uses the Chilkat ActiveX through the OLE Automation stored procedures. They must be enabled once on the server (EXEC sp_configure 'Ole Automation Procedures', 1; RECONFIGURE;), and the Chilkat ActiveX registered must match the bitness of the SQL Server instance (64-bit for a 64-bit SQL Server). To bind to a specific major version of Chilkat, append the major version number to the ProgID, such as sp_OACreate 'Chilkat.Mcp.11' for Chilkat v11.*.*.

sp_OACreate returns an object token (an int) that is passed as the first argument of every sp_OAMethod, sp_OAGetProperty and sp_OASetProperty call, and released with sp_OADestroy. Objects returned by methods (such as an HttpResponse or JsonObject) are also tokens received through an int OUT parameter; they must likewise be destroyed, and the OUT parameter is NULL when the method fails to return an object. Objects passed as arguments are passed by their token. When an OLE Automation procedure itself fails (non-zero @hr), sp_OAGetErrorInfo describes the error.

Data types: strings are nvarchar(4000); integers, booleans (1 or 0) and object tokens are int; dates are datetime. In the signatures on this page, @success, @iResult, @sResult and the like are the OUT variables receiving a method's return value, @iValue / @sValue receive or supply a property value, and the remaining @ variables are the method's arguments in order.

A string returned through an OUT parameter is limited to 4000 characters. For longer values, retrieve the result as a result set into a table variable instead of an OUT parameter, for example DECLARE @tmp TABLE (outputLine ntext) followed by INSERT INTO @tmp EXEC sp_OAGetProperty @mcp, 'LastErrorText'. See string length limitations for strings returned by sp_OAMethod calls.

Methods that pass or return raw byte arrays are not shown on this page, because varbinary(max) values cannot be exchanged through sp_OAMethod (see varbinary(max) limitation). Use the BinData-based alternatives (methods ending in Bd) or the base64 / hex string-encoded variants instead. Binary properties (such as LastBinaryResult) can be retrieved as a result set into a table variable, as shown in their signatures. Asynchronous (*Async) methods and event callbacks are not available from SQL Server.

Properties

AuthToken
EXEC sp_OAGetProperty @mcp, 'AuthToken', @sValue OUT
EXEC sp_OASetProperty @mcp, 'AuthToken', @sValue
Introduced in version 11.6.0

An optional bearer token for authenticating to the MCP server. When set, it is sent as an Authorization: Bearer <token> header on every request. The default is the empty string.

top
Connected
EXEC sp_OAGetProperty @mcp, 'Connected', @iValue OUT
Introduced in version 11.6.0

Read-only. 1 after a successful Connect (the initialize handshake completed).

top
ConnectTimeoutMs
EXEC sp_OAGetProperty @mcp, 'ConnectTimeoutMs', @iValue OUT
EXEC sp_OASetProperty @mcp, 'ConnectTimeoutMs', @iValue
Introduced in version 11.6.0

The maximum amount of time, in milliseconds, to wait to establish the TCP/TLS connection to the MCP server. The default value is 30000 (30 seconds).

top
DebugLogFilePath
EXEC sp_OAGetProperty @mcp, 'DebugLogFilePath', @sValue OUT
EXEC sp_OASetProperty @mcp, 'DebugLogFilePath', @sValue

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
IdleTimeoutMs
EXEC sp_OAGetProperty @mcp, 'IdleTimeoutMs', @iValue OUT
EXEC sp_OASetProperty @mcp, 'IdleTimeoutMs', @iValue
Introduced in version 11.6.0

The maximum amount of time, in milliseconds, to wait for additional incoming data when receiving a response has paused. This is not a total timeout. The default value is 180000 (180 seconds).

top
LastBinaryResult
INSERT INTO @tmp EXEC sp_OAGetProperty @mcp, 'LastBinaryResult'

This property is mainly used in SQL Server stored procedures to retrieve binary data from the last method call that returned binary data. It is only accessible if Chilkat.Global.KeepBinaryResult is set to 1. This feature allows for the retrieval of large varbinary results in an SQL Server environment, which has restrictions on returning large data via method calls, though temp tables can handle binary properties.

top
LastErrorHtml
EXEC sp_OAGetProperty @mcp, 'LastErrorHtml', @sValue OUT

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
EXEC sp_OAGetProperty @mcp, 'LastErrorText', @sValue OUT

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
EXEC sp_OAGetProperty @mcp, 'LastErrorXml', @sValue OUT

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastMethodSuccess
EXEC sp_OAGetProperty @mcp, 'LastMethodSuccess', @iValue OUT
EXEC sp_OASetProperty @mcp, 'LastMethodSuccess', @iValue

Indicates the success or failure of the most recent method call: 1 means success, 0 means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
LastStringResult
EXEC sp_OAGetProperty @mcp, 'LastStringResult', @sValue OUT

In SQL Server stored procedures, this property holds the string return value of the most recent method call that returns a string. It is accessible only when Chilkat.Global.KeepStringResult is set to TRUE. SQL Server has limitations on string lengths returned from methods and properties, but temp tables can be used to access large strings.

top
LastStringResultLen
EXEC sp_OAGetProperty @mcp, 'LastStringResultLen', @iValue OUT

The length, in characters, of the string contained in the LastStringResult property.

top
ProtocolVersion
EXEC sp_OAGetProperty @mcp, 'ProtocolVersion', @sValue OUT
EXEC sp_OASetProperty @mcp, 'ProtocolVersion', @sValue
Introduced in version 11.6.0

The MCP protocol version. May be set before Connect to request a specific version; after Connect it reflects the version negotiated with the server and is sent in the MCP-Protocol-Version header of each request. The default is 2025-06-18.

top
ServerInstructions
EXEC sp_OAGetProperty @mcp, 'ServerInstructions', @sValue OUT
Introduced in version 11.6.0

Read-only. Optional usage instructions provided by the server in the initialize result (may be the empty string), available after Connect.

top
ServerName
EXEC sp_OAGetProperty @mcp, 'ServerName', @sValue OUT
Introduced in version 11.6.0

Read-only. The server name reported in the initialize result, available after Connect.

top
ServerVersion
EXEC sp_OAGetProperty @mcp, 'ServerVersion', @sValue OUT
Introduced in version 11.6.0

Read-only. The server version reported in the initialize result, available after Connect.

top
SessionId
EXEC sp_OAGetProperty @mcp, 'SessionId', @sValue OUT
Introduced in version 11.6.0

Read-only. The Mcp-Session-Id assigned by the server during the Connect handshake, or the empty string if the server is stateless. Chilkat automatically includes this session id on all subsequent requests.

top
VerboseLogging
EXEC sp_OAGetProperty @mcp, 'VerboseLogging', @iValue OUT
EXEC sp_OASetProperty @mcp, 'VerboseLogging', @iValue

If set to 1, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is 0. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
EXEC sp_OAGetProperty @mcp, 'Version', @sValue OUT

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods

CallTool
EXEC sp_OAMethod @mcp, 'CallTool', @success OUT, @name, @arguments, @result
Introduced in version 11.6.0

Calls the MCP tools/call method for the tool named name, passing the JSON arguments object in arguments. The members of arguments are the tool's input arguments and should match the tool's inputSchema as returned by ListTools. For example, a weather tool might be called with the arguments { "location": "Boston, MA", "units": "fahrenheit" }. Pass an empty JSON object (not a null) for a tool that takes no arguments.

On success, the tool result is placed in result. It contains a content array, an isError boolean, and optionally a structuredContent object. Each element of the content array has a type ("text", "image", "audio", or "resource"); for a "text" element the value is in its text member. A typical result looks like:

{
  "content": [ { "type": "text", "text": "The weather in Boston is 72F and sunny." } ],
  "isError": false
}
Thus the text of the first content item is at JSON path content[0].text.

Note: A tool that executes but reports a failure returns 1 here with isError set to 1 in result (the failure message is typically carried in the content array). The return value is 0 only for transport- or protocol-level failures.

Connect must be called first.

Returns 1 for success, 0 for failure.

More Information and Examples
top
Close
EXEC sp_OAMethod @mcp, 'Close', @success OUT
Introduced in version 11.6.0

Explicitly terminates the MCP session by sending an HTTP DELETE with the Mcp-Session-Id header, then releases the connection. It is safe to call this method when not connected (it simply releases any transport). A server that does not permit client-terminated sessions responds with HTTP 405, which is not treated as an error.

Returns 1 for success, 0 for failure.

More Information and Examples
top
Connect
EXEC sp_OAMethod @mcp, 'Connect', @success OUT, @url
Introduced in version 11.6.0

Connects to the MCP (Model Context Protocol) server at the Streamable HTTP endpoint URL in url (for example https://example.com/mcp) and performs the MCP initialize handshake.

On success, the SessionId, ProtocolVersion, ServerName, ServerVersion, and ServerInstructions properties are populated, and Connected becomes 1.

If an AuthToken is set, it is sent as a bearer token on the request. The URL must begin with http:// or https://; the host, port, and path are taken from it. Only the Streamable HTTP transport is supported; the stdio transport is not.

Returns 1 for success, 0 for failure.

More Information and Examples
top
GetLastJsonData
EXEC sp_OAMethod @mcp, 'GetLastJsonData', NULL, @json
Introduced in version 11.6.0

Returns, in json, the complete JSON-RPC response envelope from the most recent request (the jsonrpc, id, and result or error members), for diagnostics and logging. Note that this is the full JSON-RPC envelope, whereas ListTools, CallTool, ReadResource, and GetPrompt each return only the inner result object.

top
GetPrompt
EXEC sp_OAMethod @mcp, 'GetPrompt', @success OUT, @name, @arguments, @json
Introduced in version 11.6.0

Calls the MCP prompts/get method for the prompt named name, passing the JSON arguments object in arguments (pass an empty object for a prompt that takes no arguments). On success, the result is placed in json, consisting of an optional description and a messages array in which each message has a role and content.

Connect must be called first.

Returns 1 for success, 0 for failure.

More Information and Examples
top
ListPrompts
EXEC sp_OAMethod @mcp, 'ListPrompts', @success OUT, @json
Introduced in version 11.6.0

Calls the MCP prompts/list method. On success, the server's result object is placed in json, containing a prompts array in which each prompt has a name, optionally a description, and an arguments array, and possibly a nextCursor for pagination.

Connect must be called first.

Returns 1 for success, 0 for failure.

More Information and Examples
top
ListResources
EXEC sp_OAMethod @mcp, 'ListResources', @success OUT, @json
Introduced in version 11.6.0

Calls the MCP resources/list method. On success, the server's result object is placed in json, containing a resources array in which each resource has a uri, a name, and optionally a description and mimeType, and possibly a nextCursor for pagination.

Connect must be called first.

Returns 1 for success, 0 for failure.

More Information and Examples
top
ListTools
EXEC sp_OAMethod @mcp, 'ListTools', @success OUT, @json
Introduced in version 11.6.0

Calls the MCP tools/list method. On success, the server's result object is placed in json, containing a tools array in which each tool has a name, a description, and an inputSchema (a JSON Schema describing the tool's arguments), and possibly a nextCursor for pagination.

Connect must be called first.

Returns 1 for success, 0 for failure.

More Information and Examples
top
ReadResource
EXEC sp_OAMethod @mcp, 'ReadResource', @success OUT, @uri, @json
Introduced in version 11.6.0

Calls the MCP resources/read method for the resource identified by the URI in uri. On success, the result is placed in json, containing a contents array whose entries carry a uri, a mimeType, and either text (for text resources) or blob (base64 for binary resources).

Connect must be called first.

Returns 1 for success, 0 for failure.

More Information and Examples
top
SetConnectionSettings
EXEC sp_OAMethod @mcp, 'SetConnectionSettings', @success OUT, @sock
Introduced in version 11.6.0

Copies connection settings, including HTTP proxy, SOCKS proxy, bind (network interface) IP address, and TLS options, from sock. This is optional; if not used, default settings apply. Call this method before Connect.

Returns 1 for success, 0 for failure.

More Information and Examples
top