What is Typingmind Mcp

typingmind-mcp is a lightweight server designed to run and manage multiple Model Context Protocol (MCP) servers. It integrates seamlessly with TypingMind, allowing users to connect custom AI models or tools via a simple REST API.

Use cases

Use cases include running custom AI models locally, managing multiple MCP servers for different applications, and integrating AI tools with TypingMind for streamlined workflows.

How to use

To use typingmind-mcp, you can start it on your local device using the command npx @typingmind/mcp <auth-token>. For remote servers, ensure Node.js is installed, then run the same command or use a process manager like pm2 for persistent operation.

Key features

Key features include easy integration with TypingMind, REST API for managing MCP servers, health check endpoint, and support for running on both local and remote servers.

Where to use

typingmind-mcp can be used in various fields such as AI development, machine learning model management, and any application requiring integration with TypingMind for enhanced AI capabilities.

MCP Connector

MCP Connector is a lightweight server that can run and manage multiple Model Context Protocol (MCP) servers, specifically designed to integrate with TypingMind. It provides an easy way to run MCP servers on your local computer or a remote server, making it possible to connect your custom AI models or tools with TypingMind through a simple REST API.

---

How to Run on Your Local Device

You can quickly start the MCP Connector using npx (no install required):

npx @typingmind/mcp@latest <auth-token>

• Replace <auth-token> with your authentication token provided by TypingMind.

You can also provide the auth token via an environment variable:

MCP_AUTH_TOKEN=<auth-token> npx @typingmind/mcp@latest

Keep the process running while you use TypingMind.

HTTPS Support

To enable HTTPS, set the following environment variables:

CERTFILE=./path/to/certificate.crt KEYFILE=./path/to/privatekey.key npx @typingmind/mcp@latest <auth-token>

• CERTFILE: Path to your SSL certificate file
• KEYFILE: Path to your SSL private key file

When both variables are set, the server will use HTTPS instead of HTTP.

---

How to Run on a Server

If you prefer running the MCP Connector on a remote server:

1. Install Node.js (version 14 or later).

2. Run the server using npx:

   npx @typingmind/mcp@latest <auth-token>
   

   To run with HTTPS:

   CERTFILE=./path/to/certificate.crt KEYFILE=./path/to/privatekey.key npx @typingmind/mcp@latest <auth-token>
   

   Alternatively, for persistent running (e.g., after closing SSH), you may use a process manager like pm2 or screen/tmux:

   pm2 start npx -- @typingmind/mcp@latest <auth-token>
   

---

How to Run with Docker

You can also run the MCP Connector using Docker.

1. Build the Docker Image:
   Navigate to the project’s root directory (where the Dockerfile is located) and run:

   docker build -t mcp-connector .
   

   (You can replace mcp-connector with your preferred image tag.)

2. Run the Docker Container:

   • Basic Run (HTTP):
     Replace <auth-token> with your actual token. This command runs the container in detached mode (-d) and maps the container’s default port 50880 to the same port on your host machine.

     docker run -d -p 50880:50880 --name mcp-connector-instance mcp-connector <auth-token>
     

   • Using a Different Port:
     If you need to use a different port (e.g., 8080 on the host mapped to 12345 in the container), use the -p flag for mapping and the -e PORT environment variable:

     docker run -d -p 8080:12345 -e PORT=12345 --name mcp-connector-instance mcp-connector <auth-token>
     

   • Running with HTTPS:
     To enable HTTPS, you need to provide the certificate and key files and set the CERTFILE and KEYFILE environment variables. Mount your host’s certificate files into the container (e.g., into a /certs directory) and provide the paths via environment variables. Remember to map the appropriate port.

     docker run -d \
       -p 50880:50880 \
       -e PORT=50880 \
       -e CERTFILE=/certs/certificate.crt \
       -e KEYFILE=/certs/privatekey.key \
       -v /path/to/your/certificate.crt:/certs/certificate.crt:ro \
       -v /path/to/your/privatekey.key:/certs/privatekey.key:ro \
       --name mcp-connector-instance \
       mcp-connector <auth-token>
     

     (Replace /path/to/your/certificate.crt and /path/to/your/privatekey.key with the actual paths on your host machine. The :ro flag mounts them as read-only.)

   • Viewing Logs:
     To see the logs from the running container:

     docker logs mcp-connector-instance
     

   • Stopping the Container:

     docker stop mcp-connector-instance
     

   • Removing the Container:

     docker rm mcp-connector-instance
     

---

How to Connect to TypingMind

To connect MCP Connector to TypingMind:

1. Follow the instructions at www.typingmind.com/mcp.
2. Paste your MCP Connector server address (http://localhost:<port> or your server’s IP address and port) and your authentication token on the TypingMind MCP integration page.

---

REST API Endpoints

All API endpoints require authentication via the Bearer token you provide when starting the server.

Endpoint	Method	Description
/ping	GET	Health check; returns { status: "ok" }
/start	POST	Start one or more MCP clients; body: { mcpServers: { ... } }
/restart/:id	POST	Restart a specific client
/clients	GET	List all running MCP clients and their tools
/clients/:id	GET	Get info about a specific client
/clients/:id/tools	GET	List available tools for a client
/clients/:id/call_tools	POST	Call a tool for a client; body: { name, arguments }
/clients/:id	DELETE	Stop and delete a client

Notes:

• All requests need an Authorization: Bearer <auth-token> header.
• Available ports: The server will choose port 50880 or 50881, make sure
  these ports are available in your system. You can also use PORT environment
  variable to specify a different port.

---

License

MIT