17402706898

Committed 02 Sep 2025 11:56AM UTC coverage: 81.132% (+0.2%) from 80.945%

Build # 17402706898

Build Type

Pull #502

github

Committed by

web-flow

Commit Message

Merge 90304fd04 into d471cdd0d

Pull Request Pull Request #502: chore: extend library interfaces to allow injecting a custom connection error handler MCP-132

Run Details

902 of 1199 branches covered (75.23%)

Branch coverage included in aggregate %.

93 of 106 new or added lines in 8 files covered. (87.74%)

2 existing lines in 2 files now uncovered.

4572 of 5548 relevant lines covered (82.41%)

44.13 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

89.29

/src/common/connectionErrorHandler.ts

import type { CallToolResult } from "@modelcontextprotocol/sdk/types.js";
import { ErrorCodes, type MongoDBError } from "./errors.js";
import type { AnyConnectionState } from "./connectionManager.js";
import type { ToolBase } from "../tools/tool.js";

export type ConnectionErrorHandler = (
    error: MongoDBError<ErrorCodes.NotConnectedToMongoDB | ErrorCodes.MisconfiguredConnectionString>,
    additionalContext: {
        availableTools: ToolBase[];
        connectionState: AnyConnectionState;
    }
) => { errorHandled: false } | { errorHandled: true; result: CallToolResult };

export const connectionErrorHandler: ConnectionErrorHandler = (error, { availableTools, connectionState }) => {
    const connectTools = availableTools
        .filter((t) => t.operationType === "connect")
        .sort((a, b) => a.category.localeCompare(b.category)); // Sort Atlas tools before MongoDB tools

    // Find the first Atlas connect tool if available and suggest to the LLM to use it.
    // Note: if we ever have multiple Atlas connect tools, we may want to refine this logic to select the most appropriate one.
    const atlasConnectTool = connectTools?.find((t) => t.category === "atlas");
    const llmConnectHint = atlasConnectTool
        ? `Note to LLM: prefer using the "${atlasConnectTool.name}" tool to connect to an Atlas cluster over using a connection string. Make sure to ask the user to specify a cluster name they want to connect to or ask them if they want to use the "list-clusters" tool to list all their clusters. Do not invent cluster names or connection strings unless the user has explicitly specified them. If they've previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same cluster/connection.`
        : "Note to LLM: do not invent connection strings and explicitly ask the user to provide one. If they have previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same connection string.";

    const connectToolsNames = connectTools?.map((t) => `"${t.name}"`).join(", ");
    const additionalPromptForConnectivity: { type: "text"; text: string }[] = [];

    if (connectionState.tag === "connecting" && connectionState.oidcConnectionType) {
        additionalPromptForConnectivity.push({
            type: "text",
            text: `The user needs to finish their OIDC connection by opening '${connectionState.oidcLoginUrl}' in the browser and use the following user code: '${connectionState.oidcUserCode}'`,
        });
    } else {
        additionalPromptForConnectivity.push({
            type: "text",
            text: connectToolsNames
                ? `Please use one of the following tools: ${connectToolsNames} to connect to a MongoDB instance or update the MCP server configuration to include a connection string. ${llmConnectHint}`
                : "There are no tools available to connect. Please update the configuration to include a connection string and restart the server.",
        });
    }

    switch (error.code) {
        case ErrorCodes.NotConnectedToMongoDB:
            return {
                errorHandled: true,
                result: {
                    content: [
                        {
                            type: "text",
                            text: "You need to connect to a MongoDB instance before you can access its data.",
                        },
                        ...additionalPromptForConnectivity,
                    ],
                    isError: true,
                },
            };
        case ErrorCodes.MisconfiguredConnectionString:
            return {
                errorHandled: true,
                result: {
                    content: [
                        {
                            type: "text",
                            text: "The configured connection string is not valid. Please check the connection string and confirm it points to a valid MongoDB instance.",
                        },
                        {
                            type: "text",
                            text: connectTools
                                ? `Alternatively, you can use one of the following tools: ${connectToolsNames} to connect to a MongoDB instance. ${llmConnectHint}`
                                : "Please update the configuration to use a valid connection string and restart the server.",
                        },
                    ],
                    isError: true,
                },
            };

        default:
            return { errorHandled: false };
    }
};

1	import type { CallToolResult } from "@modelcontextprotocol/sdk/types.js";
2	import { ErrorCodes, type MongoDBError } from "./errors.js";	2✔
3	import type { AnyConnectionState } from "./connectionManager.js";
4	import type { ToolBase } from "../tools/tool.js";
5
6	export type ConnectionErrorHandler = (
7	error: MongoDBError<ErrorCodes.NotConnectedToMongoDB \| ErrorCodes.MisconfiguredConnectionString>,
8	additionalContext: {
9	availableTools: ToolBase[];
10	connectionState: AnyConnectionState;
11	}
12	) => { errorHandled: false } \| { errorHandled: true; result: CallToolResult };
13
14	export const connectionErrorHandler: ConnectionErrorHandler = (error, { availableTools, connectionState }) => {	2✔
15	const connectTools = availableTools	26✔
16	.filter((t) => t.operationType === "connect")	26✔
17	.sort((a, b) => a.category.localeCompare(b.category)); // Sort Atlas tools before MongoDB tools	26✔
18
19	// Find the first Atlas connect tool if available and suggest to the LLM to use it.
20	// Note: if we ever have multiple Atlas connect tools, we may want to refine this logic to select the most appropriate one.
21	const atlasConnectTool = connectTools?.find((t) => t.category === "atlas");	26✔
22	const llmConnectHint = atlasConnectTool	26!
23	? `Note to LLM: prefer using the "${atlasConnectTool.name}" tool to connect to an Atlas cluster over using a connection string. Make sure to ask the user to specify a cluster name they want to connect to or ask them if they want to use the "list-clusters" tool to list all their clusters. Do not invent cluster names or connection strings unless the user has explicitly specified them. If they've previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same cluster/connection.`	1!
24	: "Note to LLM: do not invent connection strings and explicitly ask the user to provide one. If they have previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same connection string.";	25✔
25
26	const connectToolsNames = connectTools?.map((t) => `"${t.name}"`).join(", ");	26✔
27	const additionalPromptForConnectivity: { type: "text"; text: string }[] = [];	26✔
28
29	if (connectionState.tag === "connecting" && connectionState.oidcConnectionType) {	26✔
30	additionalPromptForConnectivity.push({	1✔
31	type: "text",	1✔
32	text: `The user needs to finish their OIDC connection by opening '${connectionState.oidcLoginUrl}' in the browser and use the following user code: '${connectionState.oidcUserCode}'`,	1✔
33	});	1✔
34	} else {	26✔
35	additionalPromptForConnectivity.push({	25✔
36	type: "text",	25✔
37	text: connectToolsNames	25✔
38	? `Please use one of the following tools: ${connectToolsNames} to connect to a MongoDB instance or update the MCP server configuration to include a connection string. ${llmConnectHint}`	24!
39	: "There are no tools available to connect. Please update the configuration to include a connection string and restart the server.",	1✔
40	});	25✔
41	}	25✔
42
43	switch (error.code) {	26✔
44	case ErrorCodes.NotConnectedToMongoDB:	26✔
45	return {	23✔
46	errorHandled: true,	23✔
47	result: {	23✔
48	content: [	23✔
49	{	23✔
50	type: "text",	23✔
51	text: "You need to connect to a MongoDB instance before you can access its data.",	23✔
52	},	23✔
53	...additionalPromptForConnectivity,	23✔
54	],	23✔
55	isError: true,	23✔
56	},	23✔
57	};	23✔
58	case ErrorCodes.MisconfiguredConnectionString:	26!
59	return {	3✔
60	errorHandled: true,	3✔
61	result: {	3✔
62	content: [	3✔
63	{	3✔
64	type: "text",	3✔
65	text: "The configured connection string is not valid. Please check the connection string and confirm it points to a valid MongoDB instance.",	3✔
66	},	3✔
67	{	3✔
68	type: "text",	3✔
69	text: connectTools	3✔
70	? `Alternatively, you can use one of the following tools: ${connectToolsNames} to connect to a MongoDB instance. ${llmConnectHint}`	3!
NEW 71	: "Please update the configuration to use a valid connection string and restart the server.",	×
72	},	3✔
73	],	3✔
74	isError: true,	3✔
75	},	3✔
76	};	3✔
77
78	default:	26!
NEW 79	return { errorHandled: false };	×
80	}	26✔
81	};	26✔

mongodb-js / mongodb-mcp-server / 17402706898

Source File Press 'n' to go to next uncovered line, 'b' for previous

Source File
Press 'n' to go to next uncovered line, 'b' for previous