This MCP server allows for testing Model Context Protocol functionality, enabling integration with editors like VSCode. It serves as an adapter for connecting to TMS (a model service) through various code editor extensions.
To get started with the MCP testing server, follow these steps:
Build the MCP testing server with the following command:
npm run build
To test the server with the built-in inspector:
npm run inspect
The MCP server can be configured to work with different code editors. Below are configuration examples for popular editors.
Add the following configuration to your Cline extension settings in VSCode:
{
"mcpServers": {
"tms-adapter": {
"command": "/Users/$USER/.nvm/versions/node/v23.7.0/bin/node",
"args": [
"/Users/$USER/mcp-testing-tool/build/index.js"
],
"disabled": false,
"env": {
"TMS_TOKEN": ""
}
}
}
}
Note:
$USER
with your actual usernameTMS_TOKEN
environment variableFor the Continue extension (available for both VSCode and WebStorm), use this configuration:
{
"experimental": {
"modelContextProtocolServers": [
{
"transport": {
"type": "stdio",
"command": "/Users/$USER/.nvm/versions/node/v23.7.0/bin/node",
"args": [
"/Users/$USER/mcp-testing-tool/build/index.js"
]
}
}
]
}
}
Note:
$USER
with your actual usernameAfter configuration, the MCP server will run automatically when you use the configured extensions. The server handles communication between your editor and the TMS service, providing model context protocol functionality.
For the best experience, VSCode with the Cline extension is recommended as mentioned in the original documentation.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "tms-adapter" '{"command":"node","args":["/Users/$USER/mcp-testing-tool/build/index.js"],"disabled":false,"env":{"TMS_TOKEN":""}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"tms-adapter": {
"command": "node",
"args": [
"/Users/$USER/mcp-testing-tool/build/index.js"
],
"disabled": false,
"env": {
"TMS_TOKEN": ""
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"tms-adapter": {
"command": "node",
"args": [
"/Users/$USER/mcp-testing-tool/build/index.js"
],
"disabled": false,
"env": {
"TMS_TOKEN": ""
}
}
}
}
3. Restart Claude Desktop for the changes to take effect