with one click
mcp-server-management
// Manage external MCP server connections to extend Thoth's capabilities
// Manage external MCP server connections to extend Thoth's capabilities
[HINT] Download the complete skill directory including SKILL.md and all related files
| skill_id | mcp-management |
| name | MCP Server Management |
| description | Manage external MCP server connections to extend Thoth's capabilities |
| version | 1.0.0 |
| author | Thoth Team |
| required_tools | ["list_mcp_servers","add_mcp_server","update_mcp_server","remove_mcp_server","toggle_mcp_server","test_mcp_connection"] |
| tags | ["management","mcp","configuration","tools"] |
This skill provides comprehensive management of external MCP (Model Context Protocol) servers that can extend Thoth's capabilities with additional tools and resources.
MCP (Model Context Protocol) is a standard protocol that allows AI assistants to connect to external tool servers. By adding MCP servers, you can:
View all configured external MCP servers, their connection status, and tool counts.
Example:
Can you show me what MCP servers are configured?
Add a new external MCP server with stdio, HTTP, or SSE transport.
Example for stdio transport:
Add an MCP server called "my-filesystem" with:
- transport: stdio
- command: npx
- args: ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/folder"]
- enabled: true
- auto_attach: true
Example for SSE transport:
Add an MCP server called "remote-analysis" with:
- transport: sse
- url: http://localhost:8080/mcp
- enabled: true
- auto_attach: false
Modify an existing server's configuration.
Example:
Update the "my-filesystem" server to enable auto-attach
Remove a server from the configuration (disconnects and detaches tools).
Example:
Remove the "remote-analysis" MCP server
Enable or disable a server without removing it.
Example:
Disable the "my-filesystem" server
Test connectivity to a configured MCP server.
Example:
Test the connection to the "my-filesystem" server
All MCP servers are stored in vault/thoth/_thoth/mcps.json. This file serves as the single source of truth and is monitored for changes (hot-reload enabled).
{
"version": "1.0.0",
"mcpServers": {
"server-id": {
"name": "Server Name",
"enabled": true,
"transport": "stdio|http|sse",
"command": "command-for-stdio",
"args": ["arg1", "arg2"],
"url": "http://url-for-http-or-sse",
"env": {"ENV_VAR": "value"},
"autoAttach": true,
"timeout": 30
}
}
}
Best for local command-line tools that communicate via stdin/stdout.
Required fields: command, args
Example: npx-based MCP servers
Best for HTTP-based REST APIs.
Required fields: url
Example: http://localhost:8080/mcp
Best for streaming responses and real-time updates.
Required fields: url
Example: http://localhost:8080/mcp
When autoAttach: true:
When autoAttach: false:
The system watches mcps.json for changes and automatically:
You can manually edit the file or use the provided tools.
{
"filesystem": {
"name": "Filesystem Server",
"enabled": true,
"transport": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/workspace"],
"autoAttach": true,
"timeout": 30
}
}
{
"sqlite": {
"name": "SQLite Database",
"enabled": true,
"transport": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-sqlite", "--db-path", "./data.db"],
"autoAttach": true,
"timeout": 30
}
}
{
"github": {
"name": "GitHub Server",
"enabled": true,
"transport": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {"GITHUB_TOKEN": "your-token"},
"autoAttach": false,
"timeout": 30
}
}
enabled: false and test before enablingautoAttach settingmcps.jsonvault/thoth/_thoth/settings.jsonvault/thoth/_thoth/mcps.json