1. Conduid
  2. Developer Tools
  3. Typingmind MCP Extension
MCP server · Developer Tools

Typingmind MCP Extension

Extension to add MCP tool support to TypingMind

Unclaimed MIT last commit a year ago devtools
54Fair

Scored 4 months ago · breakdown

About Typingmind MCP Extension

Typingmind MCP Extension is an MCP server published by iamjackg in the Developer Tools category: extension to add MCP tool support to TypingMind. It has been installed 0 times through Conduid.

The repository has 15 stars and 5 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 (0) before depending on it in production.

Install

Install
npx typingmind-mcp-extension

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 Typingmind MCP Extension

Powered by Claude · Grounded in docs

I know everything about Typingmind MCP Extension. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

TypingMind MCP Extension

A TypingMind extension that integrates with MCP-Bridge to bring Model Context Protocol tools into TypingMind.

Installation

Important: It's highly recommended to download and verify this JavaScript file before using it. TypingMind only allows installation of extensions by providing a URL to a JavaScript file.

  1. Download the mcp-extension.js file
  2. Review the code to verify its safety and functionality
  3. Host the file somewhere accessible (personal web server, GitHub Pages, etc.)
  4. In TypingMind, add the extension by providing the URL to your hosted file

Configuration

The extension uses a configurable host and port for MCP-Bridge defined at the top of the file:

// MCP Bridge configuration
const MCP_BRIDGE_URL = 'http://localhost:8000';

You will need to modify this URL to match your MCP-Bridge setup before hosting the file.

How It Works

This extension:

  • Connects to your MCP-Bridge server
  • Fetches available Model Context Protocol tools
  • Registers them as TypingMind plugins
  • Tools will appear with the prefix "MCP -" in your plugins list

Visual Feedback

When the extension loads:

  • Success: A blue notification will appear at the bottom right of the screen with information about the number of tools loaded
  • Error: A red notification will appear at the bottom right if there's a connection issue or other error

Notifications automatically disappear after 5 seconds.

Debugging

If you encounter issues:

  1. Open your browser's developer console (F12 or right-click → Inspect → Console)
  2. Look for logs prefixed with "MCP Extension"
  3. Common errors:
    • Connection refused: Check if your MCP-Bridge is running
    • Invalid URL: Verify the MCP_BRIDGE_URL in the extension is correct
    • CORS errors: Your MCP-Bridge needs to allow requests from your TypingMind domain

Limitations

  • No support for resources or prompts yet
  • Requires self-hosting the JS file

References

License

MIT License - See LICENSE file for details

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Typingmind MCP Extension

How do I install Typingmind MCP Extension?

Run npx typingmind-mcp-extension, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Typingmind MCP Extension safe to use with an AI agent?

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

Is Typingmind MCP Extension still maintained?

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