1. Conduid
  2. Developer Tools
  3. Demo MCP Server Client Implementation
MCP server · Developer Tools

Demo MCP Server Client Implementation

by · github.com/mschwarzmueller/demo-mcp-server-client-implementation

A demo implementation of a MCP server (consuming a dummy API) and basic client.

Unclaimed MIT last commit a year ago devtools
InstallView source
54Fair

Scored 5 months ago · breakdown

About Demo MCP Server Client Implementation

Demo MCP Server Client Implementation is an MCP server published by mschwarzmueller in the Developer Tools category: a demo implementation of a MCP server (consuming a dummy API) and basic client.

The repository has 29 stars and 8 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/mschwarzmueller/demo-mcp-server-client-implementation

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Demo MCP Server Client Implementation

Powered by Claude · Grounded in docs

I know everything about Demo MCP Server Client Implementation. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 6 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Example MCP Server + Client Implementation

I wrote an article and created a video about MCPs and why they're useful in my opinion.

This demo project contains a backend service / API that's consumed by a MCP server which exposes it in a standardized way to MCP clients - like the example MCP client (a very simple AI chatbot) that's also part of this project.

Important: All three parts (service, server, client) rely on Node.js being able to execute TypeScript without a compilation step. Yes, modern Node.js can do that! Make sure you have Node.js 23.x or higher installed!

Configuration

Add a .env file inside the client folder (next to the package.json file there) and add the following content to it:

OPENAI_API_KEY=<your-open-ai-key>

In each folder (service, server, client) run npm install to install required dependencies.

Running Service, MCP Server & MCP Client

For each part, navigate into the respective folder (service, server and client) and run npm run dev (with Node.js 23+). Keep each process running.

The "client" process is a simply AI chatbot using OpenAI behind the scenes. This chatbot has the custom MCP server "installed" - therefore, this AI chat application is able to store and retrieve custom information via the backend service created in the "service" folder.

Bugs are possible - it's just a basic demo implementation :-)

README fetched from the repository 6 days ago. The original is authoritative.

Questions

About Demo MCP Server Client Implementation

How do I install Demo MCP Server Client Implementation?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Demo MCP Server Client Implementation safe to use with an AI agent?

Its trust score is 54 out of 100 (fair). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Demo MCP Server Client Implementation still maintained?

The last commit was a year ago and 1 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.