packages/xmcp/README.md
xmcp.dev
OrganizationPopularThe TypeScript MCP framework
| Publisher | basementstudio |
| Repository | xmcp |
| Language | TypeScript |
| Forks | 92 |
| Stars | 1.3K |
| Available tools | 0 |
| Transport type | stdio |
| Categories | |
| License | MIT |
| Links |
- Connect tools to AI workflows
xmcp.dev exposes MCP capabilities that can be used by compatible AI clients and agents.
- 0 available tools
Browse the callable actions below, including names and descriptions when provided by the server.
- Ready-to-copy setup
Use the installation snippets to configure this server in your preferred MCP client.
- Open source signals
1.3K stars and 92 forks from the linked repository.
Use xmcp.dev MCP with multiple AI models
TypingMind connects MCP tools at the workspace level, so once xmcp.dev is connected, you can use it with different AI models in TypingMind instead of setting it up separately for each model. This MCP runs locally through the TypingMind MCP connector on your device.
Setup guide to use the local connector
Use this when the MCP server needs access to local files, apps, or private resources on your computer.
Open the MCP settings
In TypingMind, go to Settings, Advanced Settings, then Model Context Protocol and choose Setup Connector.
- Open TypingMind in your browser.
- Click the Settings icon.
- Go to Advanced Settings.
- Open the Model Context Protocol section.
- Click Setup Connector and choose This Device.

Run the connector command
Choose This Device, copy the command from TypingMind, and run it in Terminal. Keep the process running while you use MCP.
- Copy the setup command shown by TypingMind.
- Open Terminal on macOS or Windows Terminal on Windows.
- Paste and run the command.
- Approve the package install if Terminal asks you to proceed.
- Keep the Terminal window running while using MCP tools.
Add xmcp.dev as a server
When the connector status is Ready, click Edit Servers and paste the MCP server configuration.
- Wait until the connector status shows Ready.
- Click Edit Servers.
- Paste the xmcp.dev MCP server configuration.
- Save the server list.
- Refresh if you want to confirm the connector is still ready.

{
"mcpServers": {
"xmcp": {
"command": "npx",
"args": [
"-y",
"<mcp-server-package>"
]
}
}
}Use it across models
Save the server list, open Plugins, enable the xmcp.dev MCP tools, then select any supported AI model in TypingMind and use the tools in chat or assign them to an AI agent.
- Open the Plugins page in TypingMind.
- Enable the xmcp.dev MCP tools.
- Start a chat and choose the AI model you want to use.
- Use the MCP tools in chat or assign them to an AI agent.
- Switch to another AI model whenever needed without reconnecting MCP.

Here is what I found using xmcp.dev.
Frequently asked questions
What is the xmcp.dev MCP server used for?
xmcp.dev is an MCP server that lets compatible AI clients connect to external tools and context. In TypingMind, you can add this MCP server once and make its tools available in your AI workspace.
Can I use xmcp.dev MCP with multiple AI models in TypingMind?
Yes. TypingMind connects MCP tools at the workspace level, so you can use xmcp.dev with different AI models such as Claude, ChatGPT, Gemini, or other models you have configured in TypingMind without setting up the MCP server separately for each model.
Why use xmcp.dev MCP with TypingMind?
TypingMind is one of the best frontends for LLM chat because it brings multiple AI models, prompts, plugins, AI agents, API keys, and MCP tools into one workspace. With xmcp.dev connected, you can use its MCP tools across your preferred models while keeping your chat workflow organized in TypingMind.
How do I connect xmcp.dev MCP to TypingMind?
xmcp.dev runs through the TypingMind local MCP connector. This is best when the MCP server needs access to local files, desktop apps, command-line tools, or private resources on your computer.
What tools does xmcp.dev MCP provide in TypingMind?
xmcp.dev exposes MCP capabilities that can be enabled from the TypingMind Plugins page and used in chat or assigned to AI agents.
Do I need to share my API keys with TypingMind to use xmcp.dev MCP?
No. TypingMind is local-first and lets you keep your model providers, API keys, prompts, and MCP configuration under your control. If xmcp.dev requires authentication, add the required headers, OAuth settings, or local configuration for that MCP server when you create the connection.
Related MCP Servers
View allcodegraph
Pre-indexed code knowledge graph, auto syncs on code changes, for Claude Code, Codex, Gemini, Cursor, OpenCode, AntiGravity, Kiro, CoPilot, and Hermes Agent — fewer tokens, fewer tool calls, 100% local
goose
an open source, extensible AI agent that goes beyond code suggestions - install, execute, edit, and test with any LLM
CyberStrikeAI
The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.
Godot MCP
MCP server for interfacing with Godot game engine. Provides tools for launching the editor, running projects, and capturing debug output.
