Commands

You can run an MCP server locally or in the cloud to connect an MCP client to a lightweight backend that calls external APIs, handles authentication, and returns structured results. This guide shows a practical demo server you can clone, configure, build, and test end-to-end.

How to use

You use the MCP server to expose API integrations to an MCP client. Start the local server, then point your MCP client at the configured runtime to perform API calls, pass parameters, and receive structured responses. You manage authentication via environment variables or built-in configuration, and you can test different API endpoints by updating the resource configuration.

How to install

Prerequisites: Node.js and npm must be installed on your machine.

1. Create a workspace folder to organize your MCP servers.

2. Install dependencies and build the demo server.

3. Start the server and verify it runs locally.

Additional configuration and usage details

The server you will run uses a local process to serve an MCP endpoint. The provided example shows how to run a Node.js-based server that loads the built demo file and optionally passes an API key for external requests.

If you need to customize, edit the demo entrypoint and the API integration in the source files under src.

The example startup configuration in use demonstrates how to launch a local node process with a specific build artifact and an environment variable for the API key.

Code sample for the local runtime you can adapt directly shows how to invoke the node command with the built demo script and an environment variable for RapidAPI access.

Sample configuration snippets

{
  "stock": {
    "command": "node",
    "args": ["users/mcp-servers/mcp-server-demo-1/build/demo.js"],
    "env": {
      "RAPIDAPI_KEY": "YOUR_API_KEY_HERE"
    },
    "disabled": false,
    "autoApprove": []
  }
}

Troubleshooting tips

If the server does not start, check that Node is installed and that the build output path exists. Ensure the environment variable is set correctly and that any required API keys are valid.

If API calls fail, confirm the target API endpoint, required headers, and authorization details are correctly configured in the resources and environment variables.

Notes on testing

Launch a chat session, then issue a call that exercises the configured API path. Verify that the response structure matches expectations and that authentication works as intended.

Available tools

clone_workspace

Create a workspace folder to organize MCP servers and clone the demo repository into that folder.

review_src_files

Inspect the source files under src, focusing on index.ts for customization and demo.ts for a functional API integration example.

select_api

Choose an API from RapidAPI, obtain access, and review headers, authorization details, and request parameters for proper integration.

configure_demo

Define the server name, tool name, required parameters, and resource configuration including authorization headers and endpoint URL.

install_build_run

Install dependencies, build the project, and start the local MCP server using the proper command and environment.

configure_chat_app

Edit the example MCP config for your chat client, update the build path, tool name, and API key, and save the configuration.

test_setup

Open a chat, trigger the server, and verify that the integration responds correctly with expected data.